Many bugs in Watch window

[rogeriodec_games]

Reproduction Steps
In addition to this bug report ("My Watches" showing the expand icon when table is empty), there are several other issues with the Watch window:

A) The first click to sort a column won’t work:

1. Create this on a script:

local a01 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a02 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a03 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a04 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a05 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a06 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a07 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a08 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a09 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a10 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a11 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a12 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a13 = {	aa = { 	aaa = 1 }, 	bb = {} }
local a14 = {	aa = { 	aaa = 1 }, 	bb = {} }

while true do
	print()
end

1. Set a breakpoint on line 17 (print)
2. Open the Watch window
3. Run:
   
4. When debugging pauses on the breakpoint, click on the “Name” column to put all variables descending. The first time you click, it changes the sorting icon, but do not sort anything:
   
5. Only a second click will reorder:
   

B) Losing column sort at each step:

1. Keeping the same script as before, press F10 to trigger the debug Step and the previous sort will be lost:
   

C: Closing a previous expanded table each step:

1. Expand a table:
   
2. Press F10 and the table will be collapsed:
   

This forces me to keep reopening all levels of a table at every step, making it very difficult to keep track of an internal variable in the table.

D: Losing the scrolling position each step:

1. Scroll down to view a variable that still does not appear because it is further down:
   
2. Press F10 and the scrolling will be lost:
   

In the same case as the previous one, this forces me to keep scrolling again at each step, making it very difficult to follow a variable.

E: Inexistent variadic being shown:

Expected Behavior
All the bugs reported above shouldn’t happen.

Actual Behavior
All bugs are reported above.

---

Issue Area: Studio
Issue Type: Display
Impact: Moderate
Frequency: Constantly

[gigagiele]

Thanks for the report. We are looking into this and we’ll keep you updated!

[rogeriodec_games]

After more than 1 year, after the imposition of the Intuitive Debugger, items A, B and C were resolved.
Items D and E were not.
However, I will close this topic to open another one about these two items.