I've never tried, but cant you call the base class behaviour with the scope resolution operator?
e.g.
CommandButton::Click()
Cheers,
Andrew
>>>Yeah, I think I've got it under control now ("sure", he says, "until next time"). David F. gave a pretty clear explanation in another thread, too.
>>
>>Good, though this should read:
>>
>>>>But in a VFP Base class method like Show(), if you put code in there without a DoDefault(), its going to execute that code, and only that code, it probably won't make the form visible. Thats why, if you use Show() like
event, you need to include
DoDefault() in order to actually do the Show(), it could conditionally leave it out too. It depends on what you want>
>"It depends", now there's a phrase I've never used before. < LOL > I agree with David F., that there should be away to execute just the VFPBaseClass behaviour, not just the DoDefault() that does ALL parent class code and levels.
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
