Antonio,
thank you for the fast response and the perspective to have an excellent FiveWin debugging function in the near future
As stated above, the most important issues is the difference between the shown and the actual executed row and the time-consuming preparation of the xBrowse.
Understanding that it’s an array-xBrowse and it takes some time to prepare it, particularly if the source files have thousands (more than 10000) of rows. I suppose thats also the reason for the row-differences!?
So, perhaps you can change the concept from file- to function-/procedure-/method- oriented preparation!
At least, it would be possible/thinkable to have separate dialogs for each function/procedure/method, analog to the call structure. The focus then changes automatically between them with the execution progress. For navigation, you can offer a jump-list of all modules in the actual file, etc.
Here my actual feature list:
- Possibility to set breakpoints with 'AltD()'
- Additional monitoring of PUBLIC's, PRIVATE's and STATIC's
- New folder for a ‘Watch function’, to see only a few variables or the value of an expression (script function)
- Copy & paste function: Edit a row in the source browse; copy a part of the line in the clipboard; past it in the watch edit field.
- New folder for Set() values -
done
- Monitor the values of (multidimensional) arrays
- Syntax highlighting
- Options: Chose font, encoding and size. I’m still using OEM-font ‘Terminal’
- Make much as possible settings persistent, e.g.:
- xBrowse state, e.g. column width
- Breakpoints
- List of watched variables and expressions
- Partitioning between upper and lower dialog