 |
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
 Posted: Sat May 29, 2010 5:29 am
[3.18a]BUG?: Installation resets custom options
|
I've had to install 3.18 a couple of times (due to computer problems) and each time, it's reset all my custom settings (ansi colors, special characters, etc) back to default. Not sure if this has happened to anyone else, but it's annoying having to reset each setting (including fonts!) :P
Charneus |
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Sun May 30, 2010 5:52 am
|
I don't even see a 3.18 release?
|
|
|
|
|
GeneralStonewall
Magician
Joined: 02 Feb 2004
Posts: 364
Location: USA
|
|
|
|
|
Fizban1216
Apprentice
Joined: 03 Feb 2007
Posts: 170
|
Posted: Sun May 30, 2010 2:24 pm
|
Happens to me. Had it turn the numlock setting back on when I installed it despite having turned it off when 3.17 was installed beforehand.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon May 31, 2010 12:25 am
|
Some settings are session-specific and stored in the *.pkg file and some are global stored in the CMUD.INI file. Can you try to pin down which specific settings are getting reset? There *were* some changes to handling the global options from the CMUD.INI file since that involved some internal string list usage, but I don't see any changes that would have effected session-specific stuff like ansi colors and special characters.
|
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Mon May 31, 2010 1:19 am
|
I'll try to pin them down, but for me, it was everything. Checkboxes I had unticked were ticked again (Echo message, update window, spelling, etc). My ansi colors were changed back to default (I change them because the dark colors are too dark for me to see sometimes), and my fonts were reset back to Courier. My color syntax settings were also reset back to nothing. The only things that didn't change was my layout and toolbar settings.
Charneus |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jun 03, 2010 4:36 pm
|
I am not able to reproduce this at all. Is it still happening with 3.18b? If so, can you create a simple procedure for creating a session, changing a setting, then reinstalling CMUD that will show the problem?
Here is what I did that worked just fine:
1) Installed v3.18b using the default installation options.
2) Created new session called Test
3) Opened Test offline and changed the ansi colors. Also turned off the Auto Numlock option
4) Exited CMUD
5) Re-ran the CMUD setup installer and used the default installation options again
6) Ran CMUD and opened Test offline
7) Colors were still set properly and the Auto Numlock option was still off.
So it seems to work for me.
For the Auto Numlock option, the value is saved to your CMUD.INI file, which is in \My Documents\My Games\CMUD by default. When I looked at this file, the first few lines say:
| Code: |
[Settings]
NumLock2=0 |
so if this option isn't getting saved, you should check to be sure your CMUD.INI file is getting updated. The CMUD installer doesn't touch this file at all.
For your ANSI colors, those are saved in your *.PKG file, so you should check to see if the timestamp on your *.PKG file is getting updated after you change the colors and exit CMUD. Again, the installer doesn't touch your package files, so it sounds to me more like a problem with your changes getting saved to your package properly. |
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Thu Jun 03, 2010 7:42 pm
|
Didn't happen for me in 3.18b, so not sure what the problem was with 3.18a. I'll keep a lookout for it, though.
Charneus |
|
|
|
|
|
|
|
