Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP 9.0, SP2 now available
Message
From
16/10/2007 12:35:15
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
16/10/2007 11:41:31
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01260474
Message ID:
01261289
Views:
20
Greg,

I have no problem to wait.

It's just a Vista problem. Me and my customers switched to XP early this year. (I from W2K and the customer from NT) So there is no hurry. ::)
I just like to keep the problems solved when they are new.

Agnes
>Hold off check until at least this week end. I very busy at work trying to get a release out, and probably have little time for play.
>
>>Thank you Alan,
>>
>>I will check Greg's page in a while.
>>
>>Agnes
>>
>>>When I get in tomorrow, I'm going to send the three pieces of code to Greg, and he'll put it with his projecthooks list on his web site.
>>>
>>>I'll see what he does, then if necessary, I'll post it here in the downloads.
>>>
>>>Hope that's ok.
>>>
>>>>Hi Alan,
>>>>
>>>>can you post the hook it in downloads?
>>>>
>>>>Agnes
>>>>>What I finally did (about 5 minutes ago) was to mess a little with Calvin's code to handle scx and vcx files and then messed with it a bit more so I could embed it into a projecthook in the beforebuild event. Now I don't need to worry about it when I save files. When I build, everything gets fixed before the compile.
>>>>>
>>>>>>I have look at Calvin's solution, but have tried it yet. Thanks for the heads-up about forms inside VCXs.
>>>>>>
>>>>>>>Yes. I did some checking and you're right. This fix is not about the border repaint issue. I assume Calvin's code does that, but again, you need to remember to fix the order of items in the property field whenever you save a form - new or existing.
>>>>>>>
>>>>>>>I notice also that Calvin's code (I'd only use it as a one time run) only fixes the properties in an scx file, and doesn't do anything to the forms within a vcx file. I don't know whether it's necessary or not. I assume it isn't a problem with inherited forms, but I'm not sure about instances of those form class objects using createobject() and form.show()
>>>>>>>
>>>>>>>>I beleive this fixes the highlighting issue in the listbox. Without it, this listbox behaves like you are multiselecting items as you move through the list.
>>>>>>>>
>>>>>>>>>I use this code in the startup program (I can't remember where it came from, but seems to fix border issues):
>>>>>>>>>
>>>>>>>>>IF VAL(OS(3)) > 5
>>>>>>>>> DECLARE INTEGER GdiSetBatchLimit IN WIN32API INTEGER
>>>>>>>>> GdiSetBatchLimit(1)
>>>>>>>>>ENDIF
>>>>>>>>>
>>>>>>>>>>>Agreed, I thought SP2 was mostly about Vista compatibility. I've tried it on a laptop and desktop, and the bad behavior happens on both unless I turn off Aero. I'm astounded that they didn't fix this. What were they doing all this time? So now the best case is that I have to remember to run Calvin's utility every time I create a new form (thanks to him for the utility, though!)
>>>>>>>>>>
>>>>>>>>>>Also, any time you change a form. Saving an existing form will re-order the information in the properties field of the scx file.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Reply
Map
View

Click here to load this message in the networking platform