Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat May 23, 2009 12:38 am   

[3.08] Still a bit of lingering xml loading differences in 3.08
 
I'm still noticing a few differences in my xml when I use the new version. I noticed that in the new version it had changed my text color from white to black. When I pulled up a side by side look at the before and after it looks like the xml has been modified a bit from what it was.

Version 3.06
Code:
<button name="alertness_ind" type="Toggle" autosize="false" width="8" height="16" toolbar="2" mousebtn="Left" toolstyle="true" transparent="false" color="darkred" textcolor="white" priority="135">
  <caption>-</caption>
  <expr>%iskey(@Defenses, alertness)</expr>
  <tooltip>alertness</tooltip>
    <state caption="-" mousebtn="Left" color="green"></state>
</button>


Version 3.08
Code:
<button name="alertness_ind" type="Toggle" autosize="false" width="8" height="16" toolbar="2" toolstyle="true" color="darkred" textcolor="white" priority="135" id="1970">
  <caption>-</caption>
  <expr>%iskey(@Defenses, alertness)</expr>
  <tooltip>alertness</tooltip>
  <button color="green" id="1971">
    <caption>-</caption>
  </button>
</button>


In all other respects 3.08 feels really solid. The flicker is gone for me and apart from the morphed xml it seems pretty solid and speedy.

If it would be helpful I can e-mail you my xml file and you can load it up and check for other xml loading differences. This seems like a another case similar to what I posted about and you fixed for 3.08. Perhaps with my file you could root out some of the corner cases.


Last edited by ReedN on Sat May 23, 2009 2:00 am; edited 1 time in total
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Sat May 23, 2009 1:52 am   
 
Something isn't quite right with your examples. In 3.08, the button states should be output with a nested <button> tag and *not* any <state> tag. So I don't see how 3.08 could possibly be generating your example shown above. Did you get your examples backwards? Your first example looks more like 3.08 output, but the XML looks fine to me.

Also, I see textcolor="white" in both examples, so no difference there. So I wasn't able to reproduce any problem with that.

However, keep in mind that the Options database field in 3.06 and earlier could be severely corrupted. That was one of the main problems fixed in 3.07/3.08. So problems in old settings files might be causing some issues too.

Feel free to send me your 3.06 (or earlier) package and just make a note of what settings I should pay attention to that have a problem.


Last edited by Zugg on Sat May 23, 2009 4:54 am; edited 1 time in total
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat May 23, 2009 1:59 am   
 
You are correct, I accidentally reversed the labels. I'll correct the original post.

The xml from 3.06 has been sent, let me know if you have issues receiving it.

Regarding what to look at in particular, the only thing I've noticed so far (and it was relatively minor) is that the "-" from the button above is showing up with a foreground color of black despite what the xml says.

I guess originally I was envisioning that you could run something like tkdiff against the two, but that was before your comments made clear that you expect various differences between the two.
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat May 23, 2009 2:13 am   
 
Here's another button I happened across that showed some difference in background color:

3.06
Code:

<button name="btn_TargetShort1" autosize="false" width="100" height="20" autopos="false" left="451" mousebtn="Left" priority="252">
          <caption>1) %item(@shortTargets, 1)</caption>
</button>


3.08
Code:

<button name="btn_TargetShort1" autosize="false" width="100" height="20" autopos="false" left="451" color="#ECE9D8" priority="253" id="3378">
  <caption>1) %item(@shortTargets, 1)</caption>
</button>


In the new version the color field "#ECE9D8" was applied whereas the original was default.

This new version has been stable enough I'm using it as my regular version. Great work!
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Sat May 23, 2009 4:57 am   
 
You probably had the Transparent flag enabled in the 3.06 version. The Transparent flag no longer exists in 3.08. The color value of "None" is used to set the transparency. But in 3.06 you could enable the Transparent checkbox without effecting the text color box, which causes the button to be imported into 3.08 with the indicated color.

So this isn't a bug, but is just a side-effect of the color change. Some things like this will require you to manually edit your button colors.
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat May 23, 2009 3:11 pm   
 
I did a little more poking around on the original item I posted about. I believe the issue is that before the 'white' textcolor applied to both the button states, but when you made it so that each was separate the extra state reverted to default. If I set it manually to how it looked before then I get this xml, which shows the extra button state with another 'white'

Code:

<button name="alertness_ind" type="Toggle" autosize="false" width="8" height="16" toolbar="2" toolstyle="true" color="darkred" textcolor="white" priority="135" id="1970">
  <caption>-</caption>
  <expr>%iskey(@Defenses, alertness)</expr>
  <tooltip>alertness</tooltip>
  <button color="green" textcolor="white" id="1971">
    <caption>-</caption>
  </button>
</button>


So this seems like more of a conversion oversight. I don't think this will affect people once they convert.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Sat May 23, 2009 5:28 pm   
 
Yep, you are correct. The default text color is Black. I should probably make the default color for a child button state "None" so that it will inherit the color from the main parent button. I'll add that to the list.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net