Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Form(s) within another
Message
 
To
13/10/2005 01:43:59
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9
Miscellaneous
Thread ID:
01058371
Message ID:
01058699
Views:
9
>>>>
ACTIVATE WINDOW (frmGuest.Name) IN WINDOW (frmHost.Name)
>>>>Are we asking for trouble handling forms through ACTIVATE WINDOW?
>>>>
>>>
>>>1. forms name must to be unique
>>>a my big wish is for ( emulate SetParent() API):
>>>
>>>ACTIVATE WINDOW (frmGuest.hwnd) IN WINDOW (frmHost.hwnd)
>>>
>>>
>>>2. ACTIVATE WINDOW it is equal to .Visible = .T.,
>>>but it is not equal to .Show
>>
>>Hi Fabio,
>>
>>1. I agree that forms name conflict may be an issue, thus something like ACTIVATE WINDOW (frmGuest.hwnd) IN WINDOW (frmHost.hwnd)would be better than ACTIVATE WINDOW childname IN WINDOW parentname, though SetParent API is easily accesible. Thanks for the SetParent suggestion.
>>
>>2. I disagree. ACTIVATE WINDOW seems to be equivalent to form.Show (with no arguments); the form.Activate event is raised.
>>
>
>If I write it, then it means that it is this way.
>
>.Show performs a .Refresh, ACTIVATE WINDOW doesn't do it.

However, ACTIVATE WINDOW is certainly more than Visible = .T.
Previous
Reply
Map
View

Click here to load this message in the networking platform