Page 1 of 1

Debugging improvements

Posted: Thu Jul 19, 2018 11:17 am
by soa
When debugging RDMLX function I am almost always interested in the contents of #IO$STS. At the moment it is listed alphabetically with the other fields but since it is a 'special' value that is always present it would be convenient if it were permanently pinned in one location. This way I wouldn't always have to go and look for it amongst, sometimes, hundreds of variables. It would also be wonderful to be able to pin the variables I'm interested in to the top or bottom (or another tab) and have them remembered between debugging sessions. ("I've mentioned this before!)

Also on debugging. The list of variables seems to be split based on the length of the name. Old school 9 character RDML names are sorted together but add a single letter and they are sorted together with the other long names at the top. I can't see any logical reason why #curselstd + #curselstd2 would not be displayed adjacent in the variable list.

And, it would be really nice if, when debugging, I could see a variables value by hovering my cursor over it - again like Visual Studio. The information to do this is all there as a right click on a variable allows the variable to be displayed in a list.

Its about time that the debugger got a bit of love.

Re: Debugging improvements

Posted: Fri Jul 20, 2018 11:07 pm
by jyoung
+1 for variable inspection on mouse over!

Re: Debugging improvements

Posted: Tue Jul 24, 2018 4:30 am
by atostaine
I thought variables that weren't listed alphabetically were ones that I created with a define_com, never thought it was the length of name.

All of these suggestions are voted +1 again.