several other of my menu files. But with this one, it insists on showing a "QWK: " prompt in yellow at the lower left of the display.
Hi all,
Trying to customize a few more of my menu display files. Having an issue with the QWK one (qwk.asc). I make my new screen in TheDraw and save in ANS format, then use 'ans2asc qwk.ans qwk.asc -clear' command to convert it to an ASC file. This all works fine and the new file displays as expected except for the bottom/end... At the bottom of the file, I have "Which or Quit: " prompt, with an '@eof@' after that, as I have done with several other of my menu files. But with this one, it insists on showing a "QWK: " prompt in yellow at the lower left of the display.
Any ideas why, and how to prevent that prompt from showing? Thanks!
Will Milberger wrote to Gamgee <=-
several other of my menu files. But with this one, it insists on showing a "QWK: " prompt in yellow at the lower left of the display.
I hope someone else is able to chime in. The QWK: in yellow, is
in one of the .DAT files. Maybe MENU.DAT? Wish I could be more
help. I know it is in one of the files you can mod to change
menus.
Digital Man wrote to Gamgee <=-
Re: Customizing menu files
By: Gamgee to All on Sun Jan 05 2020 11:28 am
Trying to customize a few more of my menu display files. Having an issue with the QWK one (qwk.asc). I make my new screen in TheDraw and save in ANS format, then use 'ans2asc qwk.ans qwk.asc -clear' command to convert it to an ASC file. This all works fine and the new file displays as expected except for the bottom/end... At the bottom of the file, I have "Which or Quit: " prompt, with an '@eof@' after that, as I have done with several other of my menu files. But with this one, it insists on showing a "QWK: " prompt in yellow at the lower left of the display.
Most menu files don't include a prompt. Most prompts are defined
in the ctrl/text.dat file.
Any ideas why, and how to prevent that prompt from showing? Thanks!
Remove the prompt from your menu file. Remember: in expert menu
mode (assuming your command shell supports that), menu files
aren't displayed to users - only prompts are. So if you had a
vague prompt such as "which or quit", it might not make any sense
in expert menu mode. Be sure to test in expert menu mode too.
Digital Man wrote to Gamgee <=-
Re: Customizing menu files
By: Gamgee to All on Sun Jan 05 2020 11:28 am
Trying to customize a few more of my menu display files. Having an issue with the QWK one (qwk.asc). I make my new screen in TheDraw and save in ANS format, then use 'ans2asc qwk.ans qwk.asc -clear' command to convert it to an ASC file. This all works fine and the new file displays as expected except for the bottom/end... At the bottom of the file, I have "Which or Quit: " prompt, with an '@eof@' after that, as I have done with several other of my menu files. But with this one, it insists on showing a "QWK: " prompt in yellow at the lower left of the display.
Most menu files don't include a prompt. Most prompts are defined
in the ctrl/text.dat file.
Yes, thanks. Since my first post I've found the "QWK: " prompt in
text.dat, and set it to a null value (""). Line 570. That stops
the display of the yellow "QWK: " prompt in the lower left, and
leaves my cursor after the "Which or Quit: " prompt which is part
of my menu display file. All good there.
However... With the same idea in mind, for the CHAT menu, I
created another display file (chat.msg), also with a "Which or
Quit: " prompt as part of the menu/display file. I was still
getting a yellow "Chat: " prompt below my custom menu though. I
found the same type of prompt as discussed above in the text.dat
file for the "Chat: " prompt (Line 506) and set that to a null
value as I did for the QWK prompt... but... The yellow "Chat: "
still shows up on the screen below my display file.
As another experiment, I restored the original Chat prompt at line
506 of text.dat, but intentionally misspelled it. It still shows
as "Chat: " though. So, something other than Line 506 is driving
the display of the yellow prompt for Chat. I searched the rest of
text.dat and found no other line that seemed to affect the prompt
display. Any advice on what the secret to that one is?
Digital Man wrote to Gamgee <=-
Re: Re: Customizing menu files
By: Gamgee to Digital Man on Sun Jan 05 2020 04:21 pm
Trying to customize a few more of my menu display files. Having an issue with the QWK one (qwk.asc). I make my new screen in TheDraw and save in ANS format, then use 'ans2asc qwk.ans qwk.asc -clear' command to convert it to an ASC file. This all works fine and the new file displays as expected except for the bottom/end... At the bottom of the file, I have "Which or Quit: " prompt, with an '@eof@' after that, as I have done with several other of my menu files. But with this one, it insists on showing a "QWK: " prompt in yellow at the lower left of the display.
Most menu files don't include a prompt. Most prompts are defined
in the ctrl/text.dat file.
Yes, thanks. Since my first post I've found the "QWK: " prompt in
text.dat, and set it to a null value (""). Line 570. That stops
the display of the yellow "QWK: " prompt in the lower left, and
leaves my cursor after the "Which or Quit: " prompt which is part
of my menu display file. All good there.
No, as I explained in my message, that is not a good idea. The
prompt is a separate string for good reason: it is displayed at
times when the menu file is not. If you tested your modifications
while in expert menu mode ('X' from the user defaults settings)
you'd see what I mean.
However... With the same idea in mind, for the CHAT menu, I
created another display file (chat.msg), also with a "Which or
Quit: " prompt as part of the menu/display file. I was still
getting a yellow "Chat: " prompt below my custom menu though. I
found the same type of prompt as discussed above in the text.dat
file for the "Chat: " prompt (Line 506) and set that to a null
value as I did for the QWK prompt... but... The yellow "Chat: "
still shows up on the screen below my display file.
Again, not a good idea to embed the prompt in the menu file.
As another experiment, I restored the original Chat prompt at line
506 of text.dat, but intentionally misspelled it. It still shows
as "Chat: " though. So, something other than Line 506 is driving
the display of the yellow prompt for Chat. I searched the rest of
text.dat and found no other line that seemed to affect the prompt
display. Any advice on what the secret to that one is?
It's exec/chat_sec.js - but I'm going to fix that to use the
text.dat line right now. Still, setting any prompt to an empty
string is a bad idea. I suggest you don't do that.
[...]Most menu files don't include a prompt. Most prompts are defined
in the ctrl/text.dat file.
Yes, thanks. Since my first post I've found the "QWK: " prompt in text.dat, and set it to a null value (""). Line 570. That stops
the display of the yellow "QWK: " prompt in the lower left, and
However... With the same idea in mind, for the CHAT menu, I
created another display file (chat.msg), also with a "Which or
Quit: " prompt as part of the menu/display file. I was still
getting a yellow "Chat: " prompt below my custom menu though. I
Rampage wrote to Gamgee <=-text.dat
Most menu files don't include a prompt. Most prompts are defined
in the ctrl/text.dat file.
Yes, thanks. Since my first post I've found the "QWK: " prompt in
, and set it to a null value (""). Line 570. That stops
the display of the yellow "QWK: " prompt in the lower left, and
[...]
However... With the same idea in mind, for the CHAT menu, I
created another display file (chat.msg), also with a "Which or
Quit: " prompt as part of the menu/display file. I was still
getting a yellow "Chat: " prompt below my custom menu though. I
how about leaving your prompt out of your screens and setting the
prompt in text.dat to your desired "Which or Quit"? just make
sure your screen places the cursor where you want the prompt to
appear?
and, as DM mentioned, make sure you test in expert mode, too... i
think you'll find some things to be confusing since expert mode
skips displaying the menu files you create...
[edit]
NVM... i see you've taken DM's advice and reverted your changes
in favor of a different course of action :)
It's exec/chat_sec.js - but I'm going to fix that to use the
text.dat line right now. Still, setting any prompt to an empty
string is a bad idea. I suggest you don't do that.
OK thank you, and thanks for the suggestions. I've changed back
to not embedding the prompt in the menu file, and restored the
text.dat strings. Really appreciate the prompt and on-point help.
Digital Man wrote to Gamgee <=-
It's exec/chat_sec.js - but I'm going to fix that to use the
text.dat line right now. Still, setting any prompt to an empty
string is a bad idea. I suggest you don't do that.
OK thank you, and thanks for the suggestions. I've changed back
to not embedding the prompt in the menu file, and restored the
text.dat strings. Really appreciate the prompt and on-point help.
You're welcome. Did you get the updated chat_sec.js with that fix
as well?
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 557 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 09:05:56 |
| Calls: | 10,406 |
| Files: | 5 |
| Messages: | 364,995 |