Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the difference between _Apply_ and _Save_ implicit #824

Closed
losandes opened this issue Feb 1, 2016 · 0 comments
Closed

Make the difference between _Apply_ and _Save_ implicit #824

losandes opened this issue Feb 1, 2016 · 0 comments
Labels
👆 ConEmu Upstream issue in ConEmu.

Comments

@losandes
Copy link

losandes commented Feb 1, 2016

Some settings support an Apply feature so changes are not persisted beyond the current session (i.e. changes to Siz & Pos can be applied without saving). As a non-power user of cmder, because this button is a fair distance from the Save Settings button, it's not implicit that the changes are not going to persist beyond the current session. Following are a few ways you could make this more obvious:

  1. Indicate that the changes are for this session only (i.e. Apply for this session instead of Apply)
  2. Make Apply a universal feature, and put it next to the Save Settings button. This might make the difference between Apply and Save more implicit.
  3. When user exits the Settings dialog without saving their settings, confirm that they don't wish to persist the settings beyond this session
@Jackbennett Jackbennett added the 👆 ConEmu Upstream issue in ConEmu. label Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👆 ConEmu Upstream issue in ConEmu.
Projects
None yet
Development

No branches or pull requests

3 participants