https://bugs.kde.org/show_bug.cgi?id=468902
Noah Davis <noaha...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INTENTIONAL
Status|REPORTED |RESOLVED
--- Comment #1 from Noah Davis <noaha...@gmail.com> ---
> 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.
--
You are receiving this mail because:
You are watching all bug changes.
