Feature suggestion: Graphical debugger remembers split point

Help!
1

I’m using: SWI-Prolog version 8.1.9 on Windows 8.1.

I’d like to see the next version of the graphical debugger remember the vertical split point between the variable pane and the source code pane. As it is now, every time you end a trace session, the next time you trigger a trace the old split point is back. If you have a lot of variables, enough so that they overflow the variable window vertically, then this means that you have to reset the split point every time you trace just to see all the variables (either that or constantly scrolling the variable pane up and down).

If the debugger remembered the split point, you’d only have to do it the first time you trace something after loading SWIPL.

2

Somehow that should work, but apparently it doesn’t :frowning: I did push a fix such that you can scroll the binding window and select a binding without the window scrolling back. This bug made scrolling the binding window nearly impossible. Related to this there is a rather long standing issue to see whether there is a smarter ordering or scrolling of the binding window such that you need less scrolling. It is not entirely clear how though.

I guess we could keep track of the bindings in a specific clause and figure out which variables have changed. Might not be trivial though as this required copying the binding or something similar, but the value of a variable can be a huge term (sometimes giga bytes).

1 Like
3

Is this a possible short-term fix? It would effectively solve the problem for folks like me with a lot of variables in some predicates.

Create a variant of the gtrace/0 called gtrace/1 where you can specify the default number of rows for both the Variable and Call Stack window panes? For example:

gtrace(25).
4

The source code is all yours :slight_smile: I never felt the need … If I would, I’d figure out why the layout is not preserved.

2 Likes