Zugg Software :: View topic

Posted: Mon Dec 04, 2006 1:07 am

I set the word wrap length to 5 to test a trigger for another thread, and when I #echoed a string more than 5 characters long, it didn't wrap. I checked the preferences to see if the wrap column really was set to 5, and it was, but nothing was getting wrapped. Thinking it might be pecular to #echo, I connected to a random MUD from the CMUD menu to see if it'd work there. Still no wrapping.

Anyone else having this problem? Auto-wrapping at the screen width works, but even with that option turned off, the Wrap Column never overrides that setting.

Apprentice Joined: 12 Jun 2006 Posts: 106

Was checking this out. I set my column to 80, and unselected autowrap. Still wrapped at screen width like you. I deselected word wrap and that worked so I enabled it(which takes a little while with a long scrollback). It then wrapped at 80 characters. I had to deselect and select the word wrap option again to get back to autowrap at screen width.

Posted: Mon Dec 04, 2006 9:59 am

So to get it to wrap, you have to uncheck the Word Wrap option and then recheck it? Least I know how to work around for now :)

Thanks saet.

EDIT: You know, it seems like lots of people are having trouble with preferences in general not saving - see here too. Is there a more general bug with preference updating?

Posted: Mon Dec 04, 2006 11:14 pm

In this case it was just a problem with the word wrap settings. CMUD has a routine to perform actions when a preference value is changed. For example, when clicking the WordWrap option, it needs to tell the current MUD window to rewrap the text. Otherwise the Preferences editor just changes the value stored in the database without doing anything else.

In this case, the WordWrap checkbox was causing the window to update it's wordwrap settings, but neither the AutoWrap nor the Wrap Column preferences were set to call this routine.

So it has nothing to do with preferences saving or not...it's just a matter of whether the effect of the settings was getting executed right away. If you see other preferences with this problem, report it separately. I have not found any general bug with preference updating yet. The Special Characters issue that Fang linked to is a totally different issue and is related to how the parser handles special character changes.