Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Can't get VFP-Form active in W2K
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Titre:
Can't get VFP-Form active in W2K
Divers
Thread ID:
00546080
Message ID:
00546080
Vues:
27
Hi all !

I use a prooven VFP5 app which behaves annoying in W2K (SP1) :
Once the app has started, and the inlog-form is there, it won't get active by itself; a click on the form or alt-tab will. This happens even when no other tasks are there. I think I saw a similar problem described at UT (even answered to it myself) but can't find it anymore (and I don't have the membership (: ).

Some characteristics which may influence the problem :

  • During startup _SCREEN is made visible and invisible;

  • During startup another task is created (all in same datasession);

  • The whole app is running in a TopLevel Form, and the inlog-form is InTopLevelForm.

  • When de app is about waiting for input, the Activate of the inlog-form runs (prooven);

  • Both Toplevel Form and InTopLevelForm show inactive (grey TitleBar);

  • When alt-tab is performed, de TopLevel Form shows Active, de InTopLevelForm does not, but IS active now (i.e. input is possible). When another (Clear Events and) Read Events is performed, the form shows Active.

  • A click on the InTopLevelForm shows both TopLevel and InTopLevel forms active (and input is allowed);

  • A Click on the TopLevelForm shows both active (and input is allowed). The getting active of the InTopLevelForm will be caused by the logic in the Click, which makes the InTopLevel Form explicitly active.

  • Knowing of all the above, whatever code in the Activate of the InTopLevelForm won't help a bit. So, no Click() anywhere, no Show() of anything, etc. etc,;

  • The other task created during startup, already shows inactive (and shows normally active in NT4 etc.);

  • If another task is running, and is active during startup, the minimizing of this task makes my app active in the proper way;

  • During startup a few Dos-calls are performed which may have to do with it (of course they become active for their short while of being there);

  • The properties "start maximized" etc. on the desktop-icon don't influence.

  • The fact that the being inactive also happens with no other tasks being there (apart from the one the app creates itself of course) puzzles me the most;

  • All of this is running fine in all other versions of Windows.


    Any ideas ?
    TIA !
  • Suivant
    Répondre
    Fil
    Voir

    Click here to load this message in the networking platform