Created attachment 170786 [details] Screenshot with square brackets and an arrow indicating the region where a potential mis-click can trigger unintended behavior. SUMMARY While navigating frame by frame in the Project Control area using the mouse, it feels far too easy to accidentally double-click on the tiny space immediately above the Time Control buttons and unintentionally trigger "Play" in Project Control, with full-screen mode active, the main consequence of which being to lose one's place in the Timeline. (This is beginning to sound like a Doctor Who episode.) As far as I know, there is no mitigation for it one's only choices are to either be more careful in where one clicks (and ideally adapt one's muscle memory) or to just advance frames using the keyboard instead. STEPS TO REPRODUCE 1. Open a project and drop a clip into the Timeline 2. Using the mouse, advance forward and backwards a single frame at a time using the Time Control up- and down-arrow buttons. 3. Increase the rate of clicks while clicking on the up-arrow button to advance forward more quickly and allow the mouse cursor to drift upwards and into the space just above the button (while still clicking). OBSERVED RESULT These steps should result in triggering "Play" on the project monitor and opening full-screen mode. EXPECTED RESULT My suggestion would be to designate the 10-15 pixels or so just above the Time Control up-arrow button as “neutral territory” where clicks on that space have no effect at all. This, I think, would serve to minimize the possibility of mis-clicking there and triggering full screen and play by mistake. SOFTWARE/OS VERSIONS Windows: 10 (available in About System) KDE Plasma Version: KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2
That missing "and" word in the summary paragraph will probably haunt me forever.
Created attachment 170830 [details] Second screenshot to clarify that the triggering region is broader than I originally indicated This second screenshot should help clarify that the region in which double-clicking has this effect is actually much larger than what my first screenshot indicated. Although the region shown in screenshot #1 identifies what might be the highest priority area to consider, l think it would also make sense to consider everything inside this box that is not a clickable element (e.g. button or drop-down), rather than just the small area immediately around the time control forward/back buttons).