[GH-ISSUE #197] Client-builder not saving settings #79

New issue

Closed

opened 2026-02-27 15:48:39 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:48:39 +03:00

Owner

Originally created by @ghost on GitHub (May 25, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/197

not sure why this happened, but I noticed it after trying to build a client with new settings (it didn't prompt me to save my settings)

Originally created by @ghost on GitHub (May 25, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/197 not sure why this happened, but I noticed it after trying to build a client with new settings (it didn't prompt me to save my settings)

kerem

2026-02-27 15:48:39 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 15:48:40 +03:00

Author

Owner

@ghost commented on GitHub (May 25, 2015):

to reproduce:
delete Bin/Release/Profiles/Default.xml
delete Bin/Release/settings.xml

Start server listen
Build client with new settings
(No prompt to save settings?)

@ghost commented on GitHub (May 25, 2015): to reproduce: delete Bin/Release/Profiles/Default.xml delete Bin/Release/settings.xml Start server listen Build client with new settings (No prompt to save settings?)

kerem commented

2026-02-27 15:48:40 +03:00

Author

Owner

@yankejustin commented on GitHub (May 25, 2015):

I will deal with this. The settings manager should implement INotifyPropertyChanged eventually. :)

@yankejustin commented on GitHub (May 25, 2015): I will deal with this. The settings manager should implement <code>INotifyPropertyChanged</code> eventually. :)

kerem commented

2026-02-27 15:48:40 +03:00

Author

Owner

@ghost commented on GitHub (May 26, 2015):

@yankejustin, 👍 sounds good.

Just a little note: changed a setting 'disabled keylogger' and saved the settings, then it prompted me to save settings.. I'm going to assume its a check for a/some setting(s) that doesn't trigger saving the file unless the settings are different than the ones read from the file

@ghost commented on GitHub (May 26, 2015): @yankejustin, :+1: sounds good. Just a little note: changed a setting 'disabled keylogger' and saved the settings, then it prompted me to save settings.. I'm going to assume its a check for a/some setting(s) that doesn't trigger saving the file unless the settings are different than the ones read from the file