Quote:
Originally Posted by BetterRed
IMO you have made something that exemplified elegant simplicity into something unnecessarily complex.
With this:
Attachment 221216
I only need be aware of two UI elements: the palette list and the button stack: I can switch between them with the Tab key, I can traverse both with the ↓ and ↑ keys, and I can 'press' a button with the Enter key.
With this:
Attachment 221217
I have to be aware of five UI elements, the palette list and the button stack on the Palettes tab panel, the button stack on the Settings tab panel, the Toggle Dark/Light button, and the row of buttons at the bottom. I have to use the Tab key to move between them
However, it is very hard to see which of the five UI elements has focus. If you look at the screenshot on the left you might be able to discern it's the Toggle Light/Dark button, and in the screenshot on the right its the Restore Calibre Defaults button.
You can't solve the visibility issue, that's baked into the Qt/calibre pie 
And when I 'pressed' the Export Selected File button, I got an error:
Code:
calibre, version 9.3.0
ERROR: Unhandled exception: <b>UnboundLocalError</b>:cannot access local variable '_' where it is not associated with a value
calibre 9.3 Portable embedded-python: True
Windows-10-10.0.19045-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19045')
Python 3.14.2
Windows: ('10', '10.0.19045', 'SP0', 'Multiprocessor Free')
Interface language: None
EXE path: D:\Calibre\Portables\Version 9 current\Calibre\calibre.exe
Successfully initialized third party plugins: Current Paths (3, 0, 0) && Palette Switcher (1, 0, 900)
Traceback (most recent call last):
File "calibre_plugins.palette_switcher.main", line 284, in export_palette
UnboundLocalError: cannot access local variable '_' where it is not associated with a value
BR |
Thank you for your analysis. I fully understand that the elegance of the previous version lay in its minimalism, and I regret that the new layout affects your keyboard workflow. Let me explain the reason for these changes and how I plan to address them:
1. The Value of the Light/Dark Control
One of the implementations I consider fundamental in this version is the ability to test and validate palettes in both modes (Light and Dark) in real time. Since Calibre manages these profiles differently, integrating this switch allows the user to ensure their palette is functional under any lighting conditions without having to leave the plugin. It's a necessary layer of control for professional color management.
2. Respect for the Original Workflow
My intention with this architecture was to expand management capabilities (import/export and security). By separating the functions into tabs, I aimed to keep each tool in its place, although I recognize that this has fragmented keyboard navigation (Tab).
3. Immediate Solutions
UnboundLocalError: Fixed. It was a naming conflict in the translation system, which has now been resolved. I'll upload it shortly. That error was also preventing translations from being accepted.
Accessibility: I'm going to review the tab order. My goal is that, even with more buttons, the focus will logically jump between the list and the main action buttons (Apply/Exit), restoring the responsiveness you mentioned.
I really appreciate experienced users like you focusing on usability. I'll work to ensure that the power of these new features doesn't compromise the simplicity that made the plugin so special.