User | Kudos |
---|---|
8 | |
2 | |
2 | |
2 | |
1 |
Currently, the only object that we have access to in an Event Structure it the control itself:
This is not what I am interested in, most of the case, when I am working on the BD.
Rather, I'd like to either find the terminal, or local variables, references, etc.
Moreover, going to the control using the above shortcut may result in a messed up FP, not mentioning cases like this:
where the control may be hidden or invisible because it is in another tab than the one currently selected.
Now, I know that some will argue that the control terminal is most of the time in the event structure (see for instance this thread)...
But read the thread's comments for counter arguments: we would be talking about the Value Change event, but this is not what I am talking aboutin general: any event for that control should give access to the control's terminal (and BTW, it could very well be an indicator) and, as for a terminal, to this list of related objects:
(The last one courtesy of this shortcut plugin)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.