 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sat Mar 15, 2008 2:24 pm
[2.20] Default package corruption
|
There are actually 2 bugs here. Procedure
1. Launch CMud
2. Close Sessions Window
3. Enter at the command line
| Code: |
| #WIN a;#MODULE b;#MODULE 0 |
4. Open Package Editor (CTRL-G)
5. Select New Package from the PE File menu
6. Name your new package 'a'
7. Click the 'a' tab in the PE
At this point you will see that package 'a' was created without its basic module. I am guessing this is because of the naming conflict with the existing window. It would seem this lack of a module is the cause of the further problems.
8. Click the untitled tab in the PE
9. Drag the 'a' window from the treeview to the 'a' tab
10. Drag the 'b' module from the treeview to the 'a' tab
If you check in the 'a' tab it will still be empty. The window and module both went into the default.pkg. Until they are removed an 'a' window will appear next to the untitled window with every launch.
When I found this I also had an empty trigger in my default package, which might have been caused during testing of the issue with creating trigger states. Should that be the case it is likely that anyone encountering either bug will have numerous problems. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Sat Mar 15, 2008 7:46 pm
|
Confirmed.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Mar 17, 2008 5:31 pm
|
Added to bug list.
|
|
|
|
|
|
|
|
