Details
-
Task
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
Description
A few things could be improved in the QML profiler UI:
1. allow restricting ranges by selected event
2. allow searching for events by more criteria than just note text (filename, function name ...)
3. Make the model parsing asynchronous. This is already done in some places, but the UI repsonsiveness when loading large traces is still not great. Restricting to ranges is completely synchronous so far.