Details
-
User Story
-
Resolution: Unresolved
-
P3: Somewhat important
-
6.8
Description
Why?
Cause
- Number of the items (if hundreds) to be viewed has a performance impact
- As a developer I want best performance. There are many cases that the user deals only with an invalid QModelIndex and represents the root index. Extra jni calls can be avoided by adding reusable Q(t)ModelIndex instance.
Customer
- TODO
Cruft
- TODO
What?
Definition
- Share a reference to a static invalid QtModelIndex to avoid extra JNI calls between jvm & native. To eliminate an invalid QtModelndex going back and forth between JVM & native, because an invalid QtModelIndex does not deliver any information other than being an invalid index (mostly when an item does not have parent aka. invalid parent).
Demarcation
Dependencies
Attachments
Issue Links
- is cloned by
-
QTBUG-133444 QtModelIndex performance measurements
-
- In Progress
-
1.
|
Implement re-usable QtModelIndex |
![]() |
Reported | Qt Android Team |
2.
|
Measure performance after changes |
![]() |
Reported | Qt Android Team |
3.
|
Document API changes |
![]() |
Reported | Qt Android Team |
4.
|
Update CI tests |
![]() |
Reported | Qt Android Team |