Quit When Closing Main Window

thiswillkillthat

[quote name='khad' timestamp='1296791992' post='20028']

Welcome to the forums, gooddy. While this is being debated, consider simply not quitting 1Password. Is there functionality that running 1Password "windowless" would grant you? You do need to have the main window open in order to copy passwords. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/mellow.gif' class='bbc_emoticon' alt=':mellow:' />



thiswillkillthat, is there a reason that simply unchecking "Disable automatic unlock for 1Password" will not work in your situation? Please do let me know. I am genuinely curious. There is still much internal debate about this and the more data points we have, the better!



SJK FTW! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/laugh.gif' class='bbc_emoticon' alt=':lol:' />

[/quote]



I'm sorry it's taken me so long to get back to you.



Running 1Password windowless doesn't have any additional functionality aside from clearing up screen space, which is often at a premium for me because I'm often working on a smaller laptop. The 1Password window is pretty large when your display is only 1280 by 800, and the fewer windows are open, in my case, generally the better. Things get cluttered, the expose tiles are smaller the more windows are open, and things eventually become difficult to tell apart. This is especially the case when I have a few finder windows, the console, an ftp program, a text editor, and remote desktop already going, and I'm having to constantly switch between them. A bigger laptop would take care of the issue, but that's just not a possibility for me right now.



I suppose the biggest reason why it bothers me is just that it feels inconsistent. In my mind, and I'm sure those of many mac users, Cmd-W closes a window, Cmd-Q quits the application. Even if it's not in the Apple guidelines, it's what nearly all applications do. In fact, of all the ~150 applications on my computer, only Aperture behaves differently (it just blocks Cmd-W). The two are discrete functions, and I'm choosing one or the other because I know what I want my computer to do. There's a very clear division between the two. The fact that Cmd-W closes, quits, and locks 1Password, in one shot, means that I have to make a conscious adjustment to my behaviour for the 1Password application in particular. People moving over from Windows will probably appreciate it, because it is more the windows way of doing things than the mac way of doing things, but to longtime mac users who know (or at least think they know) that Cmd-W closes an window but keeps the application running in the background, it's not an easy adjustment, especially because nothing else really behaves that way. For those of us that use our computers as near as makes no difference all day, every day, and who perform window operations almost subconsciously, it's forcing additional mental load to keep track of the specific behaviour of what application we're in.

[Deleted User]

[quote name='thiswillkillthat' timestamp='1297542278' post='20502']

Things get cluttered. […] A bigger laptop would take care of the issue.[/quote]

As might [url=http://forum.agile.ws/index.php?/topic/3318-quit-when-closing-main-window/page__st__20__p__19732#entry19732]effective usage of Spaces[/url]. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

khad

Or ⌘H (which I actually use all the time even apart from 1Password on my tiny little 13" screen). <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Then again, now you can keep on pressing ⌘W (in the latest beta). <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />

Oxon

Not sure I like the change to 1P no longer quitting when main window closed. It seems to me that there's more chance of leaving it unlocked without realising it (I quite often close windows I don't mean to).





Oxon

khad

Oxon, this change is reverting to the behavior that 1Password has had since it was first released. It was only changed temporarily for a short time. Have you had trouble with your lock state previously?

Oxon

I've been using 1P only since last November. I'm not sure when the lock-when-exit change was made but if it was after I started using 1P then I couldn't have noticed how it had behaved previously! Not a big issue with me and I hadn't seen the discussions about it as I'd started a new topic which you moved to here. Nice to hear the opposite view though. It just goes to show that you can't please everyone.



Regards



Oxon

khad

...though we try. *sighs*



The change was only made recently, so it sounds like you went at least a number of months using 1Password as it is now (with the option to run "windowless" like Finder, Safari, Address Book, iCal, etc.). I never take advantage of it myself — I use ⌘Q when I am not using 1Password — but, well, there it is.



I think I am going to lock this topic now. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_tongueout.png' class='bbc_emoticon' alt=':-P' />