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
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Wed Apr 09, 2008 6:33 am   

[2.22] BUG - toggle type buttons - 'new button state' creates a window
 
This bug seems so big, I assume someone has already bugged it.. but I have not been able to find a thread of it anywhere.


1. Package Editor.
2. Create new button.
3. Set a name, nothing else.
4. Set button type to toggle.
5. Save the setting.
6. Go to New>Button State
7. A new window is created where the button state should be.


I went straight from 2.18 to 2.22, and just now noticed that the 40 or so toggle buttons I have were turned into push buttons in the change, hehe.

I'll look into this more.
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Wed Apr 09, 2008 6:41 am   
 
I think it may be a problem with the package. The problem happened twice in two different backages, but not in a brand new one. I feel a bit silly for not testing that first, however..

Anyone have any suggestions on how to 'fix' my package? I do have a backup from 3 days ago but I've just done about 12 solid hours of work on it :s
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
Vijilante
SubAdmin


Joined: 18 Nov 2001
Posts: 5187

PostPosted: Wed Apr 09, 2008 10:49 am   
 
If you have a copy of the package from 2.18 that exhibits this problem then you should send it to Zugg with instructions to receate the problem. I find it best to send such things to support@zuggsoft.com, and directly attach the package do not zip it. You should also reference this topic, so Zugg has a better idea what it is related to.

Zugg is currently getting Lasik, which means you might not get much of a response for a while. You probably already have a new package mostly built that is correct, but since Zugg is talking about making 2.23 a public version it would be good to have CMud automatically fix such a problem in the packages of anyone upgrading from 2.18.
_________________
The only good questions are the ones we have never answered before.
Search the Forums
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Wed Apr 09, 2008 2:22 pm   
 
Fair point :)

I'll check it out and get it to him.

Turns out I've been able to fix it by turning the buttons back to push type, saving, then back to toggle and saving.. though I have to rewrite all the second buttons states, which is a pain due to there being almost 40 of them Confused

I still have the original package though. I'll test it to see if it happens a second time when I load it into 2.22, then send to Zugg.
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Wed Apr 09, 2008 2:31 pm   
 
This sounds related to a previously reported bug where any time you created a trigger state it would create a random setting like a button, window, whatever. Does it only happen for you on the toggle buttons? I'm not having any problems like this since the bug fix.
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Wed Apr 09, 2008 2:34 pm   
 
Its only on existing buttons. And I have not been able to reproduce it with new buttons since the first time I managed to create a new button correctly. I'll look at it closer tomorrow. Its late here.
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Wed Apr 09, 2008 4:42 pm   
 
That is what was happening before. Every time you went to add a new trigger state to an existing trigger it would create a random setting.

http://forums.zuggsoft.com/forums/viewtopic.php?t=30033&highlight=
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Wed Apr 23, 2008 11:56 am   
 
oldguy2 wrote:
That is what was happening before. Every time you went to add a new trigger state to an existing trigger it would create a random setting.

http://forums.zuggsoft.com/forums/viewtopic.php?t=30033&highlight=


Its been happening to me on trigger states now as well.

I have not sent the file to zugg yet because.. its intermittent. I'll send it now, but er..

The bug with the trig states was already fixed wasn't it?
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
Zugg
MASTER


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

PostPosted: Wed Apr 23, 2008 8:32 pm   
 
The bug that OldGuy2 is talking about was already fixed in v2.22. The problem Caled is having is something different related to something specific in his files that I am trying to track down.
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Wed Apr 23, 2008 11:03 pm   
 
By the way, I don't understand why you are going to New> button state.

Every time I have created a toggle button it automatically creates the new state.
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Sat Apr 26, 2008 9:10 pm   
 
Thats the thing. If I go to one of those buttons, change it to push type. Save. Change it back to toggle, it creates the button state properly.

For some reason they are existing as toggle types with only one state.
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sun Apr 27, 2008 10:56 am   
 
Well guess what...I just exported my settings to XML. Deleted my old package, created a new one, reimported my settings and now all my toggle buttons are broken. It changed the second state to transparent color and they won't frickin work period. Even after changing the color of all the second states, when I push them nothing happens. If I change the variable, they don't change either.
Reply with quote
Zugg
MASTER


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

PostPosted: Mon Apr 28, 2008 5:12 pm   
 
Toggle buttons normally only have one extra state. The main button entry is used for the "off" state, and state #1 is used for the "on" state.

I received Caled's files and will try to test it there and see what might be corrupted. But I can't get this to fail in any new packages, so I think it's something that was fixed and that Caled has something corrupted from a previous beta version.
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