You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the performance problems and maintainability issues with the current UI code, it might be worth at least exploring if an alternative version could work without having to rely on LibQTip. When using something like ScrollFrame, the performance should be much higher, although I don't know if it could be made to look appealing. However, at first a prototype should be built to evaluate the performance.
AFAIK this is similar to what AllTheThings uses and I've never heard anyone complain about the performance. But it's just an idea.
Due to the performance problems and maintainability issues with the current UI code, it might be worth at least exploring if an alternative version could work without having to rely on LibQTip. When using something like ScrollFrame, the performance should be much higher, although I don't know if it could be made to look appealing. However, at first a prototype should be built to evaluate the performance.
AFAIK this is similar to what AllTheThings uses and I've never heard anyone complain about the performance. But it's just an idea.
Design wise, something basic like the AnglerAtlas UI or SimpleArmory would likely be sufficient.
Details TBD, just putting it here as a "brain dump". It's unlikely to be implemented due to time constraints.
Alternatives: Refactor the existing UI code (oof), and try to cache updates/implement reactive updates instead of full rebuilds.
The text was updated successfully, but these errors were encountered: