General information
Title:
Need help understanding cmdAdd's personality
Once again I need some advice about how to proceed as I introduce myself to VFP6. Specifically I'm trying to dig down through the OOP levels to view the underlying procedural code - I'm committed to understanding OOP but my background is in procedural Fox so I'm trying to use that as a bridge. I want to put that effort in now rather than later - I could just jump in using the wizards but them I'm going to be lost when I have to subclass something to do modify it - I won't have a clue where to start.
So I started by:
Create a new form - run it - open debugger and use watch window to study what's been created.
Add a textbox and do same
Open Data Env and add a table and then look thru watch window to understand what's being wrought.
So now I drop a VCR data nav group on - BINGO - lots of detail to work my way thru - so much in fact that's it's really hard to guess which hole to jump down first.
So - thought I'd follow the cmdAdd button downward - trying to find the procedural code that makes it do its thing. But I'm getting lost in the tangle - not finding where cmdAdd becomes an individual - either ending up too far down where commandbuttons are born or too far up where cmdAdd already knows how to do its thing.
I need a benchmark - a specific explanation of where the cmdAdd button picks up it's individuality will open the door for me - I'll then be able to jump in at that level with other buttons or procedures.
I'll really appreciate any comments.
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only