Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Class-based form
Message
From
29/10/2010 19:54:23
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01487548
Message ID:
01487557
Views:
68
Sergey --

I was afraid of that. I'll have to use SYS(2015) for the property name, because there can be multiple instances of this. Just clutters up _Screen, I guess.

Thanks.

>You have to keep form reference around. Something like
>
>_Screen.AddProperty("oPemeBrowser" , Newobject ('PEME_FRMBROWSER', 'PEME_mxBrowser.VCX'))
>_Screen.oPemeBrowser.WriteHTML(lcResult)
>...
>
>
>>No, that's the opposite of what I want.
>>
>>The form is not modal, and I don't want it to be.
>>
>>What I want is that the form is still around after the Return statement. (It goes POOF and disappears because of loForm going out of scope).
>>
>>
>>>>I have just begin using class-based forms, and have come upon the following.
loForm = Newobject ('PEME_FRMBROWSER', 'PEME_mxBrowser.VCX')
>>>>loForm.WriteHTML (lcResult)
>>>>loForm.Show()
>>>>
>>>>Return lcResult
>>>>The form that is created here is not modal, and I want it to hang around once it is created by the code above. Of course, loForm goes out of scope and POOF!
>>>>
>>>>Suggestions?
>>>>
>>>>TIA
>>>
>>>Does
>>>loForm.Show(1)
>>>get you what you need?
Jim Nelson
Newbury Park, CA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform