-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add Settings Menu #31
Conversation
Thanks for another PR, for the settings i would like to keep things such as the states, image keys, and image text to be on the main form instead of settings for faster switching and perhaps even move IP and client ID to settings |
Two thoughts: We might be able to keep the large key/text in settings since the app sets the that ID automatically and potentially convert those text boxes to house the Home Menu key/text values. Or, we could bring those boxes back to main view and have them be populated automatically with the Name/ID from the Switch. As for the Client ID, I can see that moving to settings but then first-time use flow would be kinda wonky which was holding me back from sending it over in the first place. Maybe just have another Message box pop up on first run that opens settings? |
The text boxes act more as an override that is meant to be more easily accessible and it seems right to keep it in the main view at all times for quick customization. As for the Client ID and IP a prompt on first opening the app to ask for an IP and Client ID would work well. |
Gotcha. I'll poke around later tonight after New Year's festivities die down on my end. |
Alright sounds good. I was also thinking about making the switch over to the built in settings from JSON but I think i will do that once this PR is all set so i can also improve CLI settings aswell. |
So here's what I came up with:
|
Most of the code looks good but I'm not sure if I like how override has to enabled (I did enabled by default) I would rather keep that out. |
I added the override option because the majority of the users most likely wouldn't end up using the override, but those who want it and know what they're doing would still have the option. I figured making the text read-only by default could prevent an accidental character deletion and potentially a future issue submission because of it. Just makes it more user-proof, I guess? |
Hm, I think more people would use it but either way i think it's a little unnecessary. |
Alright, I'll remove it when I get home then.
- Andrew
…________________________________
From: Sun <[email protected]>
Sent: Wednesday, January 1, 2020 7:19:36 PM
To: SunTheCourier/SwitchPresence-Rewritten <[email protected]>
Cc: Andrew Augustine <[email protected]>; Author <[email protected]>
Subject: Re: [SunTheCourier/SwitchPresence-Rewritten] Add Settings Menu (#31)
Hm, I think more people would use it but either way i think it's a little unnecessary.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#31>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACQQTAQEJKXFPPVV7C7GNT3Q3UXJRANCNFSM4KBX557A>.
|
Closing this due to inactivity. |
This PR adds a separate settings menu as requested in #30 alongside a few other tweaks here and there.