Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Big problem with the F10 key in modeless forms
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01297399
Message ID:
01297444
Views:
22
>>If I hit F9 then the save works.
>>If I hit F10 then the current object loses all text that has been entered.
>>If I do not map F10 to F9 then nothing happens and the text is unchanged.
>>
>>We use command buttons on all our forms. The keypreview is turned on in the forms and there is a case statement in the form keypress that looks for any hot keys used in the command buttons and if one is hit then a procedure or whatever is run from the case statement. This has worked really well for us for a number of years.
>>
>>As I said, the Only change that caused this problem is changing the form from Modal to Modeless. If I change the form back to Modal it works ok.
>>John.
>
>What do you have in the routine you use to handle F9?

The case statement simply does thisform.cntmenu.cmdWhaterver.Click() (The cmdButton with the hot key gets fired.)
However, the text is gone before the .cmdWhaterver.Click() even happens. (I put a wait window just before it to check it.)
Beer is proof that God loves man, and wants him to be happy. - Benjamin Franklin
John J. Henn
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform