Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Ignore mouse click
Message
From
27/09/1997 01:13:14
 
 
To
27/09/1997 00:18:57
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00051797
Message ID:
00051936
Views:
36
>>Since it seems that whatever you do, you still have to modify in all places from where you make this call (unless you have a special class to deal with this), I think the easiest solution is to send the THIS object as a parameter to the second form. In this way, you have just one line (the one where you call the second form) to modify in more places and you can do all the rest (enable, disable the calling button) in the called form.
>
>Another good idea, I'll have to try them all.

Even better: you can put in your framework in all base classes, in the click event:

oApp.LastClicked = This

This way you know all the time which object was clicked last time. Probably it will take you the same work as any other previous solution (obvious, in the current problem, you will enable/disable oApp.LastClicked object in your second form), but you can use this in much many cases. Please note that beeing an object reference you can access any method/property of the LastClicked object, including it's PARENT. Etc, etc.

Vlad
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform