Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Form controls sometimes invisible
Message
De
30/06/2009 14:43:17
Gary Foster
Pointsource Consulting LLC
Chanhassen, Minnesota, États-Unis
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Database:
MS SQL Server
Application:
Desktop
Divers
Thread ID:
01409187
Message ID:
01409427
Vues:
53
Hi Christof,
Wow, thanks for the suggestions. I'll try them all out and get back to you with the results by topic.

Gary


>Hi Gary,
>
>>? datetime() && Outputs to form as expected, but no controls show up
>
>So something is displayed? This excludes the likes of LockWindowUpdate() which would work on the API level. A few things to check:
>
>a) Does VFP think there's an object where you think it is: Point the mouse to one of the controls. Then enter:
>
>Set Memowidth To 300
>? Replicate("x",10000)
>
>If you get an error message, VFP might somehow display the controls on an invisible part of the form. That is, the form might internally be a scrollable form and moved to a position where there are no controls.
>
>b) Does VFP attempt to draw? With the form being the active window enter this in the command window:
>
>Set Memowidth To 300
>? Replicate("x",10000)
>
>The form should be filled with "x"'es. Click into an invisible textbox. Does anything happen, at all?
>
>c) Does this only affect VFP controls? Add a pageframe somewhere on the form and on the first page put any ActiveX control. Put another control directly on the form into the upper left corner. if the control is visible, does it participate in the tab cycle?
>
>d) Has the Window procedure changed? If you have Visual Studio installed on your computer, there's a tool called Spy++ in the Common7\bin folder. Run this tool. Bring the blank form and another form onto the screen. Search for both windows and look at the value for the window procedure. They two windows should have the same values except for the window handle and size
>
>e) Is there a BindEvents interfering? Search the entire code base for BINDEVENTS(). The effect could have been caused by code intercepting the WM:PAINT or WM_ERASEBKGROUND messages. These are, for instance, intercepted with GDI+ code to prevent flickering.
>
>f) Probably something you tried, but does anything happen when you resize the form?
>
>g) Does
>
>oForm.SetAll("Visible",.T.)
>
>have any effect?
>
>h) Does VFP thing you are in READ compatibility mode? When you issue READ in the command window, does the blinking cursor appear somewhere?
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform