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

Some changes in v1.3 OS X app seem like a regression to me! #343

Open
oderwat opened this issue Apr 10, 2018 · 0 comments
Open

Some changes in v1.3 OS X app seem like a regression to me! #343

oderwat opened this issue Apr 10, 2018 · 0 comments
Labels
big Needs to be divided to subtasks os:macOS
Milestone

Comments

@oderwat
Copy link

oderwat commented Apr 10, 2018

  1. The v1.2 app did run in the menubar without also having it in the dock. The v1.3 seems to be always visible in the dock. This is quite annoying for a run and forget application as this because it will "eat up" dock space for "nothing". There should be an option to either have the menu-bar icon, dock icon or both.
  2. V1.3 always opens up the main window on start, which is most annoying when the app is set to autostart. The autostart selection also is not part of the configuration which is uncommon on OS X and would be needed if the app is run as menu-bar only. There should be a preferences setting to "start minimised" which does not show the main windows on start.
  3. The "quit" (Beenden) in the right button menu of the dock does not quit the application if "don't close the app if the main windows gets close" is ticked. The behaviour is also the other way around as it usually works. You would have an option to "quit the app if the main windows is closed". The current app behaviour is what "naturally" should happen if you click the yellow (minimize) button in the window frame. This current behaviour also is quite unusual and hinders for example to quit the application using apple script like so:
tell application "Nitrokey App V1.3"
quit
end
  1. The German translation uses "freischalten", "entsperren" and "aktivieren" for "unlock". It even differs for the three menu entries related to unlocking. At the same time the requesters ask one to "aktivieren" (activate) a volume. "Freischalten" has a meaning of "give access" while "entsperren" means "remove the lock" and "aktivieren" well just means "activate". I think "entsperren" should be used everywhere while activate ("aktivieren") probably is the technical term which describes what happens.
  2. Having to "Save" changes to the preferences is very unusual on OS X. Getting a requester that tells me that the changes where saved does not make that better. Preferences should just directly update the configuration. I am quite happy that there is no "are you sure you want to change the preferences" requester :-)
  3. The first tab in the main window looks quite strange to me but well.. tastes differ. I would make those "buttons" bigger (using all of the window space) and add some illustrations to them. Well thats not so important.

Sorry to be that negative but I will even stay with the old v1.2 app for now as this new version is really annoying to use regularly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big Needs to be divided to subtasks os:macOS
Projects
None yet
Development

No branches or pull requests

2 participants