@wally
Sorry for the delay I was working on building the manual (chm) and thanks for using the new debugger.
wallyg wrote: ↑Jul 31, 2022 21:24
At startup, I tried to get to the routine that is causing a problem and place a breakpoint at the beginning. The right arrow at the top of the left side gives a warning message about it not working. So I tried to go to the Procs tab on the right side, After finding it, clicking on it did nothing, I then right-clicked and picked the options to show proc, and sometimes instead a random location in the main program (default view when starting up) is displayed then the rest of the lines are highlighted. I cannot get to the routine I want. Other times it seems to work fine. Cannot duplicate it reliably.
You can't put a breakpoint on sub/function lines but only on the (first) executable lines
There is a problem with locate proc in source. For now I don't know what is happening.
wallyg wrote: ↑Jul 31, 2022 21:24
When I do try to start the program I enter "r" and I get "not an executable line" I do not say "run to", it should just start from the initial starting location.
'r' is for running to the line where the cursor is. Instead use 'x'.
wallyg wrote: ↑Jul 31, 2022 21:24
Sometimes the sub dialog window asking a question that I have to answer does not display on top of the main window. I only notice it by looking at the bottom line of the window where it displays active windows so I click on it and then it displays and I can proceed.
Know issue, the GUI library doesn't work in a same way on Windows/Linux and I keep the same behaviour for both OS. However I could force a modal window on Windows.
wallyg wrote: ↑Aug 01, 2022 21:05
When you start a new debugging run, you used to ask if I wanted to keep the previous invocation's breakpoints. You no longer do, Please put that back. I do not remember all the locations I previously set breakpoints and I want to start clean.
The function managing the breakpoints when staring/restarting is disabled. I'll see to enable it again.
wallyg wrote: ↑Aug 01, 2022 21:05
When debugging a program with hundreds/thousand routines, the tab list across the top of the left side is sort of useless. Could it be maybe only routines I have touched in this debugging run?
I guess routines are bas files. I understand when there are too many files it's a bit hard. For this reason there is a combobox on the right side listing the files.
I could add an option to display only the file where the next debugged line is and a second one selected by the combobox or via proc list. Your opinion ?
wallyg wrote: ↑Aug 01, 2022 21:05
Same for the Procs list, Could it be in proc name order (perhaps like procname(type) or procname(file) )? And then could I have a drop-down Combobox of sorted names so that I could type in the name and the list gets reduced (maybe only after 3 characters are typed) for every character I enter and when the list is small enough, I can select which one I want to be displayed in the left pane?
For the previous version of fbdebugger Windows's API allowed the sort now I have to do it myself (again Windows/linux). in my todo list.
About the combobox, also in my todo list.