Feature - Enhancement #1560
Enhancements to UI Datatypes
0%
Description
Add new member location and visible to UI Datatypes eq2uipage and eq2uielement. You would ultimately only need to add these members to UI objects that the end user could actually see.
Location would allow use a way to read objects in the UI, so we can know where to place the mouse to click. Visible would give a way to check to see what configuration a window is in by checking to see what objects are visible. This is a trick us UI modders use through the DB's UIscripting.
Updated by Amadeus over 8 years ago
- Status changed from New to Accepted
- Assignee set to Amadeus
I can look into these; however, you do know that the eq2uielement datatype does have methods called RightClick, LeftClick, and DoubleLeftClick ...correct? (In other words, you can already mouse-click all eq2uielements and eq2uipages.)
"Visible" is not as easy as you'd think. I've tried doing it a couple of times and, if I remember correctly, the data was inconsistent across different ui elements/windows.
Updated by lazycrafter over 8 years ago
I do know of the click methods and they work for 99% of what I try to do. One example is in the Guild window. If I know the location of membersRows I can calculate the location of the first MemeberRow. If I know the size of MemberRow I can calculate the location of Nth MemberRow.
I kind of figured visible had issues else you would have already had that coded.
Updated by lazycrafter about 8 years ago
I see lstype is reporting an IsVisible Member now but when I try to use it I get the error no such member. Nevermind... Grr that was EQ2UIPage that has IsVisible not EQ2IUElement. Sorry my bad.
Updated by Amadeus almost 8 years ago
- Status changed from Accepted to Resolved
I've made the "IsVisible" MEMBER of the eq2window datatype more reliable/accurate, and for eq2widget (formerally known as eq2uielement), you can use .GetProperty[Visible].
For other requests, let's make seperate issues rather than combining them together.