With looking glass, Screen.isInViewport takes 200-400ms on resizable with transparent chatbox enabled but ~20ms with transparent chatbox disabled
Description of the bug (be specific): Calling Screen.isInViewport (used by most isClickable and isOnScreen implementations) runs very slowly when transparent chatbox is enabled on resizable mode.
Few things could be addressed I believe.
- Could try to only check if the chatbox is open if the point is actually in the chatbox area.
- NPCChat.getClickContinueInterface() and NPCChat.getSelectOptionInterface() run very slowly (about 100 ms each, probably the bottleneck here). I'm personally able to check if the chat box is open on looking glass in an average of 1ms. (does it really matter if you can find the exact interface if you're really just checking to see if its open at all? could just check the master interfaces)
How often the bug occurs: 100% of the time
Triggers of the bug (if known): Described above
Java version: 1.8.211
Max Heap Size: 512
TRiBot client version: TRiBot Version: TRiBot 10.24.0
Looking Glass (yes/no): Yes
Operating System: Windows 7
Script Name: N/A
TRiBot Old-School or RS3: OSRS
Client Debug: N/A
Bot Debug: N/A
Screenshots (if any): N/A