Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Page deactivate/destroy
Message
From
28/10/1999 14:43:54
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00283256
Message ID:
00283297
Views:
17
Thanks, Kile!


>I already had two EditMode procedures, one for entering EditMode and one for leaving EditMode. So I added your suggestions to them:
>
>Upon entering EditMode, I added .Page1.Enabled = .F. and THISFORM.Closable = .F.
>Upon leaving Edit mode, I added .Page1.Enabled = .T. and THISFORM.Closable = .T.
>
>I already had the equivelant of your SETALL suggestion set up in these procedures, but only for the controls on the active page.
>
>I was under the impression that Enabling a Page would trigger the Activate() method, but I guess that's not the case. Turns out to work exactly as I need it to.
>
>Thanks for the help! Yet another problem solved!
>
>(...and Microsoft wanted to get rid of this kind of support?!?!)
>
>
>
>>Too late at that time. Maybe what you want to do, when you go to EditMode, is use SETALL() to disable everything on the form, use it again for the specific controls on the page, enabled the page only, enabled whatever OK and Cancel buttons you have, and set Form.Closable to .F.
>>
>>>I need to prevent a Page in a PageFrame from getting deactivated or destroyed if that page is in "EditMode". I found a small thread on this topic back in July, but the solution provided there does not work in my case.
>>>
>>>Is there a way to check for this in the deactivate (or destroy) and prevent the page from getting deactivated (or destroyed)? Or is it too late by this time?
>>>
>>>Can anyone help with suggestions?
>>>
>>>Thanks!
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Reply
Map
View

Click here to load this message in the networking platform