>Here's the code:
>
Michelle, please add a space between a < and the next character to make UT's HTML parser happy next time - I've added it here:
>
>DEFINE POPUP _mfile MARGIN RELATIVE SHADOW COLOR SCHEME 4
>DEFINE BAR _mfi_close OF _mfile PROMPT "\< Close" ;
> MESSAGE "Closes the current file"
>DEFINE BAR _mfi_quit OF _mfile PROMPT "E\< xit" ;
> MESSAGE "Quits Visual FoxPro"
>
>
>The "close" works; the "exit" doesn't. I don't see anything that does anything different on the "exit" one.
>
OK, now there's something to give us a clue. Could be that _mfi_quit is bypassing the shutdown, and _mfi_close is not; the obvious fix here is to change what the menu bar does when called! And even easier would've been to try simply changing the _mfi_quit, which didn't work, to _mfi_close, that did. Whne that worked, then try to track down what the difference in behaviors was from a pragmatic perspective.
In the docs, look under Menu Items/Activating System in the Index tab, SYS(2013), and Chapter 11, Designing Menus and Toolbars, in the Programmer's Guide.
I'll leave off the obvious Four-Letter Acronym that starts with "R". If I respond again, I'll probably be just as sarcastic about looking things up and trying practical exercises to see what is different between things.
I'd be totally ignorant about how things worked if I didn't bother to look. If computers could think and generate complete, consistent beautiful apps without having to look at what they do, I would be out of work. In fact, so would you - app programmers would be completely useless lazy people instead of lazy people who can apply neurochemical energy to solving problems when pressed.
IOW, the answer
was right there in code. And in the docs.
>Thanks,
>
>Michelle
>
>
>
>
>
>
>
>
>
>
>>>I don't just jump on the UT every time I hit a snag. I spend a lot of time trying to find the answer on my own first. When I run out of ideas, I post. Having you tell me to RTFM or look at code is just plain rude in my book.
>>>
>>
>>A few more questions:
>>
>>Is there anyplace that you can issue the command DO
filename.ext where there is no code behind it? Not
DO FORM. Just DO
filename.ext The answer to this might help you know when you need to examine code, as opposed to examine something other than code.
>>
>>If the code is identical in two places in the same menu, what distinguishes between them?
>>
>>IOW, what is the code fragment that works, in context, vs the code fragment that doesn't work, in context?
>>
>>Is there anything that relates to the context of the two menus that might help establish why one would be greyed out? Have you looked in the debugger to see what was happening when you tried to select the two menu pads?
>>
>>Now, do you get the idea of the process behind how to find the answer? I'm not trying to "piss you off" here - I'm trying to get you to think about the process of solving the problem.
>>
>>...and we still have not seen the relevant pieces of the .MPR that work and don't work...
>>
>>>I provided all the information I had in my question. I didn't even know there was code in an MPR. Now that I've looked at it, nothing has changed. The code for the option that doesn't work is the same as for the option that works, which is what I said in the first place.
>>>
>>>I appreciate the knowledge that there is code in a menu you can look at, but when the rest of your post is so nasty, it's just going to piss me off.
>>
>>Glad you found it useful. Good luck with solving things in the future.
