Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
File:exit
Message
From
27/01/2000 16:08:45
 
 
General information
Forum:
Visual FoxPro
Category:
Menus & Menu designer
Title:
Miscellaneous
Thread ID:
00323620
Message ID:
00323792
Views:
23
Here's the code:
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.

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.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform