mwieder wrote: ↑Fri Jun 21, 2024 8:57 pm
I'd still rather do things the other way around (if the uAllowThemeSwitching or whatever is true then...) because it makes it easier to bring things over from the LC ecosystem, especially stacks I didn't create myself.
With that situation, here's some more random logic of mine - please don't take offence, this isn't meant to come across as abrupt, ascerbic or terse:
How many other stacks do you think users will potentially bring over from Livecode? - (A genuine question) especially with it already being potentially incompatible in lots of ways. (They will likely have to make changes to their stacks anyway) - especially as the gap between LC and OXT widens.
Within that number of stacks being brought over, how many of those that rely on being in dark mode do not have these set in script or via the inspector? Additionally, how many stacks with a custom theme are just relying on it looking that way by a happy accident? - probably none I'd guess as they would have been designed to look a certain way.
It wouldn't seem unreasonable for a user to have to choose to opt-out of the defaults, rather than opt-in to the defaults. To me, opting out of the defaults (the system theme and the rest of the IDE) makes more sense. No different than when you choose to override the default stack colour, at that point the user has consciously made a decision to go for a non-standard interface.
Edit: Perhaps you can give it a go and see what you think.
(I'm hoping at the very least, it gives you a way to feel reassured that your stack will look how you set the colours in future).
As I'd particularly like to incorporate your work on the script editor, and probably other things in future.
If you run the updates, it'll take you to build 202406212252 of OXT Lite 1.05 (please quit and relaunch if it doesn't do this for you -
but it should).
Afterwards you'll have this new option:
- a.png (49.08 KiB) Viewed 4997 times
If you have the stack open that you have set specific colours on, then choose this option - you'll get:
- b.png (18.92 KiB) Viewed 4997 times
If you say "Proceed", then the custom property is set on that stack:
- c.png (14.38 KiB) Viewed 4997 times
You can then add custom colours to your stack - designing your own interface, without OXT Lite attempting to match the IDE / or system theme for it in future.
Edit: just spotted I've mixed my American and UK English spellings of colours in the alert. I wish OXT was localised. I'll go set them both to 'colors' in those dialogs now.