>>>>>As a followup on the situation. FYI:
>>>>>If the "faulty" task is left open for some considerable time it starts to recognize new dimensions !!!
>>>>>Cetin
>>>>
>>>>Does this mean that the change takes place via some kind of "windows message"? When you say "faulty" task, do you mean just VFP or do other apps see the change come later, too?
>>>>
>>>>The reason I ask this, is that VFP doesn't receive windows messages the same way that other windows apps do. I was just wondering if that's how the change is "broadcast" to the other apps, through a standard windows messaging mechanism that VFP doesn't "see", at least not immediately.
>>>
>>>
Fred,
>>>I seem to remember another app to behave like that but wasn't one that I'd care much. IOW I don't remember what was that app.
>>>I just tried with word and excel, they both behave normally. Since there besides printer, video card driver problems are reported for fox maybe it's just my video driver (S3 trio323d/2x - 8Mb AGP, driver LC2X).
>>>Cetin
>>
>>Cetin,
>>
>>It may just be your video driver. I just tried changing the resolution with a VFP6/SP3 app running. It handled the resolution changes immediately with no problems (W95a). So it must be either a video driver or maybe it is the OS in your case.
>>
>>Ed, I didn't have to use DOEVENTS. The App I tried it with was just sitting at it's main screen (standard READ EVENTS).
>
>
Fred,
>Have you tried it with the order I said or just one VFP. If you kindly confirm you did it with that order, I'll be glad and blame just to w2000 and/or my video driver (I prefer to blame video card:)
>Cetin
Cetin,
I just tried it with 2 different VFP Apps running. No difference. They both recognized the resolution change immediately for me. I was going from 1024x768 16 bit color to 800x600 16 bit color and back and forth between these two resolutions. The Apps both resized and maximized to the correct resolution every time. So, the ball is still in your court.
