Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Listbox Ghosting
Message
 
To
28/09/2013 03:46:04
Al Doman (Online)
M3 Enterprises Inc.
North Vancouver, British Columbia, Canada
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01584331
Message ID:
01584453
Views:
45
>>>>I've got a pageframe with a listbox on it that ghosts onto the part of the form that doesn't have a pageframe like the attached graphic.
>>>>
>>>>I've tried turning themes off. The listbox ghosts onto the form without deactiving the page it's on so making it invisible won't work. What other tricks are there to get past this bug.
>>>>
>>>>This is with VFP9 SP2 running on Win8 and Win7.
>>>
>>>I've seen that on some of my forms that have multiple layers e.g. pageframes within pageframes, when the object "ghosting" is not in the correct container. Either I put it in the wrong container when initially building it, or during an edit I inadvertently dragged it from one container to (typically) its parent.
>>>
>>>Another cause I've seen is getting too tricky with .LockScreen when trying to make screen updates look snappier and avoid temporary artifacts. If you're using it you could test with a version where you've removed or commented out all instances of it.
>>>
>>>You might also check that the video driver is exactly correct for the hardware, and that the most recent WHQL-certified driver is being used.
>>
>>Thanks for the input Al.
>>
>>I'm not using LOCKSCREEN. The control is definitely in the correct container and this happens on every PC I've tried ti on so the video driver wouldn't make a difference.
>
>How about any custom code in .Activate/.Deactivate/.GotFocus/.LostFocus/.Show/.SetFocus for any object or container? I seem to recall seeing weird effects when DODEFAULT( ) is not called or is called in the wrong place.

I couldn't find any custom code without a dodefault().

I did just put a THISFORM.DRAW() at the end of my Activate code for the offending page and that seems to have fixed it.
Phil Sherwood
SherWare, Inc.
Previous
Reply
Map
View

Click here to load this message in the networking platform