02-08-2022, 05:50 PM
Hi there. I seem to have found a bug, but I can't point to the line of code yet. I'm going to try to build Au from source so I can step through the internal functions in my debugger. This seems to only happen when there's DPI scaling... if my monitor is set 1:1 it works fine.
The is being run against a listview with many items. I select an item then run the script above to "start" at the selected item. The debug output prints the proper signal name..... but if DPI scaling is enabled (I usually run my monitors 4k with 150% scaling), the Invoke() method opens the properties window for an element about 5-6 items higher in the listView.
It's not so high priority because I can just run my monitors without scaling in 1080p mode...
C# code:
var w = wnd.find(1, "Signal Paths", "Afx:*");
var c = w.Child(1, id: 59648); // SysListView32
c.Activate();
var activeSignal = elm.focused();
print.it(activeSignal.Name);
activeSignal.Invoke();
The is being run against a listview with many items. I select an item then run the script above to "start" at the selected item. The debug output prints the proper signal name..... but if DPI scaling is enabled (I usually run my monitors 4k with 150% scaling), the Invoke() method opens the properties window for an element about 5-6 items higher in the listView.
It's not so high priority because I can just run my monitors without scaling in 1080p mode...