>Actually, VFP has a number of Window handles associated with it. As Vlad mentioned the _VFP.hWnd refers to the frame and _SCREEN.hWnd refers to the desktop (the area the command window generally lives in). Similarly the .Top, .Left, etc. properties of these refer to these individual windows.
>
>One thing of note, however. As with 6.0, SDI forms are different from other VFP windows. With a non-SDI form the hWnd property refers to both the frame and client area. In an SDI form, it refers to the frame. The client area is a separate window.
Yes. Using SPY++, I have noticed that VFP has "many (levels of) windows"; I needed a recursive VFP "child" window tree navigator in order to find the handle of a given child window in 6.0.
The main point, I guess, was that code that worked in VFP6 can break in VFP7. First case I'm aware of; sort of like _CUROBJ and FPW.
But performing real-time 3D graphics on a VFP Form or in _SCREEN using a 3rd-party graphics engine isn't typical either :)
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only