SUMMARY Noticeable delay before FormLayout relayouting. STEPS TO REPRODUCE 1. Build ktimetracker from this Git commit: https://cgit.kde.org/ktimetracker.git/commit/?id=2b535e8c1ec36ff968df1de5d9cbfdda4a35221d 2. Run ktimetracker 3. Create a task with a long description in ktimetracker. 4. Select the task in task list and press E (or select "Edit Time..." from context menu). OBSERVED RESULT "Edit Time" dialog opens in desktop layout, then it changes to mobile layout by itself after about 1 second. EXPECTED RESULT The appropriate layout of "Edit Time" dialog should be applied immediately, without changing it over time. SOFTWARE/OS VERSIONS Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.1.17-300.fc30.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15,4 ГиБ ADDITIONAL INFORMATION If I close the dialog and open it again without restarting ktimetracker, the layout won't jitter anymore, because the appropriate layout has already been calculated and applied on the previous appearance of the dialog.
Created attachment 121811 [details] screenshot during the first second after dialog shows up
Created attachment 121812 [details] screenshot when the dialog had already been on screen for more than one second
do you know if is due to that task name being so long? (should be elided btw) i would see that window to have always the desktop layou (and perhaps the title/name part being outside the formlayout) with that code in particular with the super long label, the "correct" behavior should be going to single column layout immediately and that should be adressed, tough that issue of long label should be adressed on ktimetracker part
(In reply to Marco Martin from comment #3) > do you know if is due to that task name being so long? (should be elided btw) Yes, relayouting happens only if task description is long. If it's short, then layout is always mobile (side-by-side).
*** Bug 476816 has been marked as a duplicate of this bug. ***
*** Bug 502100 has been marked as a duplicate of this bug. ***
*** Bug 500572 has been marked as a duplicate of this bug. ***