SUMMARY Hello all. Today I updated my system and got a new version of Spectacle. And it's not what I was expecting. There's too much information, and the move of the buttons to the toolbar completely broke the way that I'm used to working with Spectacle. So far, I never felt the need for a makeover in spectacle ux, and I would like to know the motivations for this to happen like it did. I'm used to using the 'Rectangular Region' type with delay sometimes, and previously I only needed to click on a combobox to select this type and right below I could get the delay. Now I need to set the delay first(there is the last option on the screen) and then go back to click on the button of the type of the screenshot. Also, the shadow of the annotation tools while I'm going to take the screenshot confuses me, and I never felt the need to have it during screenshot time. Would be possible to give an option to use the previous GUI? Without the need to compile the app. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.11-arch1-1 (64-bit)
> Would be possible to give an option to use the previous GUI? Without the need to compile the app. While it's not completely impossible to bring back the old UI, it would be difficult to maintain, wouldn't get all the new features and would likely become buggier and buggier over time from lack of testing and maintenance. Adding an option to use the old UI wouldn't be a good idea in the long term and I don't have the time to re-add it in the short term. > So far, I never felt the need for a makeover in spectacle ux, and I would like to know the motivations for this to happen like it did. - Annotations in rectangular region mode, much like Flameshot. You can even undo/redo annotations in the viewer window that were made in the rectangle capture window. - Screen recording, which required a Qt Quick UI in order to use the KPipeWire library. - General Qt Quick/QML port for future maintainability and longevity. It's hard to find people who can maintain a Qt Widgets app and it's much faster to make changes to a QML UI than a Qt Widgets C++ UI. - Better Wayland support. There are fewer X11-isms in the new UI. - Better multi-monitor/UI scaling support. Some major usability bugs related to the way the old UI worked with fractional scaling were fixed. The old UI used one window for all screens and the new UI uses a window for each screen when doing a rectangle capture. Multiple refresh rates are likely supported now, but I haven't tested it. - Faster UI in rectangular region mode. Previously, if you had two 4k screens rendering at 2x scale, the rectangle selection UI would have painfully low FPS.