Repository navigation
Replies: 1 comment 7 replies
|
I personally like option 2 the best. Having a Lock for every thing you can customize could look ugly though, but having it globally on a label by label action would make it so you only have "Use Action Settings" and "Only Use Custom Settings" |
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Hey there,
You might have noticed that while you can customize icons for actions using the asset manager, the label editor currently prevents modifications to labels set by actions, including font size and color. Similarly, the layout editor controls aspects like icon size and alignments, which you might also want to customize.
I've been trying to find ways to allow users to change default actions while retaining the ability to revert to them. The challenge arises when distinguishing between user preferences and default settings, especially when reverting changes. For instance, if an action initially used the Roboto font, you changed it to Arial, and then reverted to Roboto, the app can't determine if you're enforcing that option or restoring the action's defaults (the action might use different fonts, font sizes, font colors and so on).
To address this, StreamController needs a mechanism to differentiate between user overrides and default settings. Here are three approaches I've considered:
Checkbox Indicators: Display checkboxes for properties modified by actions.
Pros:
Cons:
Lock Icons: Introduce lock icons next to affected properties. Clicking the lock unlocks the property for modification and locks it again to adhere to action settings. Below is a conceptual representation (lock icon only added to the font chooser button):

Pros:
Cons:
Reset Buttons: Incorporate reset buttons for properties altered by the user. This way, StreamController can discern whether you intend to revert to action settings.
Pros:
Cons:
Each approach has its trade-offs, and we need to carefully consider usability alongside functionality. Let me know your thoughts or if you have any other suggestions.
Let me know what you like the best and if you have any other ideas to solve this problem.
All reactions