S
slacroixak
Guest
This feature is pretty needed when you deal with old legacy code that uses numerous variables. I would propose a few other ideas for the Variable View: It would be a good idea to provide a clue on the current sorting, that is a bit odd. AFAIU, the list seems to begin with local variables (in current ABL method), followed by some Next-Sibling and Prev-Sibling OO ABL object, then followed by global variable/properties, then global buffers, then 'IMPLICIT' buffers (perhaps when using ref only temp-tables), then at last, and very controversial : local parameters of a method (these should appear at first). I would suggest the following: a) review the current unsorted order to make it more consistent on : -local parameters INCLUDING parameter buffer and temp-table buffers -local variables -local temp-table buffers -local DB buffers -global parameters if any (for external procedures) -global variable & properties -global temp-table buffer (could be those implicit that shoud be renamed 'DEFAULT' to be consistent with the documentation) -global Database buffers -Next-Sibling and Prev-Sibling OO ABL facility b) you may actually provide a 3rd column, beside name and value to handle the resource type ("local variable", "local parameter" etc...). This is probably the only to distinguish two variable of same name with one local that somehow overrides a global. c) provide the ability to sort the grid on the 'Name' column when we click on its label (and toggle back to 'natural' sorting when we click again). This might be a native functionality to achieve that in the Eclipse grid you are using.
Continue reading...
Continue reading...