Closed wsanchez closed 9 years ago
This bugs me too.
The reason I haven’t done a fix like this is that the login window is application modal, so even after you bring up the preferences panel, you can’t do basic things like click in the fields in the panel, and it’s all pretty janky. I figure this only pissed off those of us that work on the server, so I haven’t figured out how to make the dialog not modal and disable enough other parts of the app.
Stonebeard sez:
With the change I did, I was able to edit the host field in preferences, though modality stopped me from closing the preference window.
I suppose another option would be a host name field in the login screen, though that might be confusing.
What's the plan for setting the default value for deployment?
@flwyd: Yeah, I tried out your change, and had tried a similar thing before. I just don't think it's a fully baked solution, and I don't think the problem is big enough to add a half-baked solution into the code for.
If you can't connect to the server (which will be the case with the default setting of localhost unless you are running a server), the login screen will not come up, and you can edit the preferences.
We have five Macs to deploy onto, plus perhaps a few personal machines to deal with on playa. I plan set up the five and no users to date have complained about being unable to set the app up on personal machines.
There's no longer a login screen; it's an on-demand dialog now.
Please verify with Incidents 3.0a1.
Stonebeard sez:
In v0.9, The Preferences menu item is disabled when the program first opens and the login screen is present. This prevents the user from switching servers so they can actually log in.