>I've got a custom menu in a VFP5 app that we're supporting, and one of the UI issues we have with it is that the client wants the last menu item selected to be popped up again after the screen that it runs compeletes running.
>
>For example, if we use File->New to create a new file, do a bunch of stuff in the file, and then close it, the client wants the 'File' menu to be popped back up, and the 'New' menu item highlit, ready to be selected by a simple ENTER.
>
>An additional wrinkle is that the system does regular housekeeping which results in any menus that are currently popped up being closed.
>
>The problem comes in trying to determine what is the currently-open (i.e., popped-up) menu, and ideally, the currently selected menu item of that popup.
>
>I've tried reading POPUP() and BAR() and the like, but they only seem to be populated AFTER an item in the popup has been selected.
>
>I need to know that "right now, the user has the Edit menu open, and the Copy menu item is selected". That way, I can preserve that information and restore the menu state when the time is right.
>
>Any leads on calls or even internal VFP stuff I can use to determine this?
>
>-- jas

You can't get at that. We don't have access to the menu events. BTW, what your client wants runs against Windows standards and should be discouraged from doing things that way.