11-15-2021, 12:32 AM
In QM2 I could navigate a sysTree32 using "up and down" to avoid traversing any previously expanded "trees". It seems that even if I collapse all the elements, navigating "next" ends up opening any expanded folders unless I close the window and re-open it. I'm not sure if this is more of a software factor in the program I'm trying to automate or if it's more of a windows / AU thing.
The TREEITEMs seem to stay in the "find UI element" browser as well, even after they're closed. In the interim I'm just closing that window and re-launching it after collecting the X,Y, width and height so I can resize it back to the original place.
I could work around it with the "up / down" arrows then set the elm to the elm.focused() but that doesn't seem as clean. Any thoughts?
The TREEITEMs seem to stay in the "find UI element" browser as well, even after they're closed. In the interim I'm just closing that window and re-launching it after collecting the X,Y, width and height so I can resize it back to the original place.
I could work around it with the "up / down" arrows then set the elm to the elm.focused() but that doesn't seem as clean. Any thoughts?