Debugging improvements

Please log all suggestions for improvements and enhancements to Visual LANSA here. Entries may be acknowledged and may be added to the list for possible inclusion in later releases of Visual LANSA.
Post Reply
soa
Posts: 339
Joined: Mon Dec 07, 2015 3:15 pm

Debugging improvements

Post by soa » Thu Jul 19, 2018 11:17 am

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.

jyoung
Posts: 690
Joined: Thu Jan 21, 2016 6:43 am
Location: Oklahoma City, OK USA

Re: Debugging improvements

Post by jyoung » Fri Jul 20, 2018 11:07 pm

+1 for variable inspection on mouse over!

atostaine
Posts: 565
Joined: Wed Jan 20, 2016 7:38 am

Re: Debugging improvements

Post by atostaine » Tue Jul 24, 2018 4:30 am

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.
Art Tostaine

adale
Posts: 12
Joined: Wed Apr 08, 2020 9:18 pm
Location: Poplarville, MS

Re: Debugging improvements

Post by adale » Fri Jul 09, 2021 12:35 am

+1 for some debug attention.

Debug can be painfully slow at time, and having some better attention help would be greatly appreciated.
I have heard said from the new tech support staff that they don't use or don't like Debug for VL Web applications, but for me this is the only and best tool I have to track and follow what is happening in the flow of the code.

Post Reply