Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Using Hotkeys
Message
De
20/10/2010 14:08:34
Kevin Hickman
The Cadle Company
Ohio, États-Unis
 
 
À
11/10/2010 15:59:44
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Network:
Novell 6.x
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01484785
Message ID:
01486359
Vues:
52
Craig,

Thanks for the idea, but it didn't quite give the desired result, but it doing so, it appears as when you run something from either the Hotkeys or the menu that it takes off like a seperate thread abd when the code on FormA takes longer then the few lines that tell it to load Form B on the Hotkey or Menu item, I get that effect. I thought about it and found a solution. I use a certain "safe zone" type field on the form and setfocus on it before I load any "FormB" from the menu items or hotkeys. The key is that the "safe field" has little code on the lostfocus or none that sets focus on any other object in FormA. When I do that,, the code runs on FormA completely, then when it hits the safe object it continues which then calls the code to load FormB and all is well.

Ahh.. I see what's happening. You should provide a flag. Before the call to FormB, set a flag that says, "Another form is opening". In the LostFocus, if the flag is set, don't go to the other object on FormA. When FormB closes, clear the flag.


>FormB is modal
>
>>Make FormB Modal.
>
>>Is there any way to load up a form over another form using the onkey (hotkeys) and put it on the bottom of the stack?
>>
>>Basically, I have my cursor on an object and push say F7 which calls up the onkey to load in say FormB. The problem is FormB loads in at the same time the lost focus of the object I was last on is working. In this case, the lost focus code directs the cursor to another object on FormA when it is done, but the onkey has already pulled up FormB and FormB must be on top, so what I get is FormB on top with a grey title bar (because it is not currently active) and a lockedup situation because FormB is in front but the cursor is somewhere on FormA.
>>
>>Is there any way to call up FormB from onkey, but make it wait until it is done with the lostfocus of the object on FormA?
>Craig Berntson
>Software craftsman
>MCSD, Microsoft Visual C# MVP, INETA Community Speaker
>Twitter: @craigber
>Read my blog
Craig Berntson
Software craftsman
MCSD, Microsoft Visual C# MVP, INETA Community Speaker
Twitter: @craigber
Read my blog
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform