Zugg Software :: View topic

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I have also seen this happen with buttons, however buttons require some sort of screen update to occur before they suddenly show up.

Procedure A (alarm starts firing)
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#CLASS test1;#ALARM *2 {bad alarm};#class 0;#T- test1" at the command line with out the quotes
4. Open Package Editor (CTRL-G)
5. Select File|New Package
6. Provide a name for the package
7. Switch to the untitled tab in the Package Editor
8. Drag the test1 class to the new package

Procedure B (hard AV crash)
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#CLASS test1;#ALARM *2 {bad alarm};#class 0;#T- test1" at the command line with out the quotes
4. Open Package Editor (CTRL-G)
5. Select File|New Package
6. Provide a name for the package
7. Switch to the untitled tab in the Package Editor
8. Right-click the test1 class and select Copy To
9. Select the new package from the list

Procedure C (alarm never works)
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#CLASS test1;#ALARM *2 {bad alarm};#class 0;#T- test1" at the command line with out the quotes
4. Open Package Editor (CTRL-G)
5. Select File|New Package
6. Provide a name for the package
7. Switch to the untitled tab in the Package Editor
8. Right-click the test1 class and select Move To
9. Select the new package from the list
10. Enable the test1 class in your new package

Posted: Wed Oct 17, 2007 9:18 pm

A) This was hard to reproduce, but I think I found a related bug. Will need to have you test this again when 2.07 is released.

B) Confirmed and fixed for 2.07. Nasty little bugger. When draging or using the copyto/moveto to another package, it would reset the default properties of the setting. That was causing settings to get enabled, triggers to be reset to default settings, etc. Very bad.

C) Confirmed. Another pretty bad problem. Using the Enable/Disable in the Settings Editor was not properly handling classes, nor was it handling alarms. The code was different from the #T+ and #T- commands and it was just changing the database record Enabled field and not running the associated code that handles classes and alarms. Fixed in 2.07.

Wizard Joined: 14 Aug 2004 Posts: 1269

I thought there was some issue with the Enable/Disable on classes in the Package Editor, but I can't find a reliable way of reproducing it! (And it appeared to only be a display issue. So maybe this is separate. Will have to see in 2.07.)

SubAdmin Joined: 18 Nov 2001 Posts: 5182

These are all fixed in 2.07. There is still a bug with disabled classes not being respected in 2.07 though.

Procedure (alarm starts firing)
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#CLASS test1;#ALARM *2 {bad alarm};#class 0;#T- test1" at the command line with out the quotes
4. Open Package Editor (CTRL-G)
5. Select File|New Package
6. Provide a name for the package
7. Switch to the untitled tab in the Package Editor
8. Drag the test1 class to the new package
9. Close untitled window by clicking X

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I had a further problem with an alarm in disabled class becoming active when working with my imported settings. I used a right-click MoveTo on a class and immediately there after the alarm started firing. I can't seem to replicate that particular occurence outside of my files though.

Posted: Mon Oct 22, 2007 7:37 pm

Well, I think the problem is in step (9). When you delete the untitled window, then where is the session window? The new package that you created doesn't have any window object, and when you have removed the untitled window, I'm not sure what window will get your alarm output.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

To make this clear I mean the X button for the untitled window. This closes the session, after a short pause brings up the Sessions Window, and a new untitled session behind it. The "bad alarm" shows up quite nicely in this 'new' untitled session.

Also if the screen shot doesn't cover it, it still occurs with 2.08

Posted: Tue Oct 23, 2007 5:58 am

OK, I'll take a look into that. Closing the Untitled window using the X deletes it and then recreates a new, blank untitled window. Not sure how this is causing the class in the other package to get enabled.