well, ok, it's also a question of being lazy. i know what i have in my rightclick() in base classes and end objects. in the mouseup i would have to go through all my base classes objects, move the call from the righclick to the mouseup, double check everything, because everything has been based on the call beeing in the righclick. now, with round about a total of 1700 classes i don't really wanna do this if i don't have to. of course, i try always to program in a way that changes later are easy, or maybe aren't even necessary, but that's not always possible.

so, changing the call from 1 event to another in , ah , maybe 21 +- 10 base classes is not so much the problem, but now where do i have some code in some subclasses or end-objects and had a reason not to call DoDefault() in there?

so maybe my programming structure could use some more modern approach - i don't know. or maybe that’s just the way it is, but i think in this case i'd rather stay with the RightClick().

although i agree with you in the subject of having control (i am so crazy, i rewrite a lot of functions which are already out there, just so that i know exactly what’s going on), but and the same token i am also a friend of using api and activeX. i think they open the already wide open doors of Vfp even more, and they are easy to use, etc, etc.

the bottom line of the whole story: i enjoy talking with fellow Fox Programmers


>OK, you're nuts. < bg >
>
>If you're more comfortable with that route, go for it. Personally, I don't like involving the Win API unless there's no other way to do something, or it's proven to be faster. I'd much rather have all my code in a place where I can tweak it if need be. Once you've gone to the API, you've given up all control (usually). Sometimes, that's a necessary evil.