 |
Toxic
Adept
Joined: 27 May 2008
Posts: 299
|
 Posted: Thu Jun 12, 2008 1:04 am
[2.26] Using #CLASS to disable/enable
|
when I type
#class "Class|subclass|subsubclass" 1
into command line or fire from a script even when its already there (just disabled) its creating a new class tree under my default session window instead of enabling the one thats already there...
I know I could use #T+ but the above should work... or at least I thought it would. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jun 12, 2008 5:52 am
|
No, that's the difference between the #CLASS command and the #T+ command. If the #CLASS command doesn't find an existing class, then it will create it. The #T+/- commands will not create it if it doesn't exist.
If the class isn't in the default session window, then you need to make sure it is in a Global module. If it's in some other window, then it's private to that other window, and then you need to use the full syntax of
#class "||WindowName|Class|Subclass" 1
So give us more detail on where the class already exists so that we can understand why CMUD isn't finding it. |
|
|
|
|
Toxic
Adept
Joined: 27 May 2008
Posts: 299
|
Posted: Thu Jun 12, 2008 12:51 pm
|
Paste the following xml into a blank session and fire the alias changeclass... By your own words it should find the class and disable it, instead it recreates the class tree under the default window for the session.
| Code: |
<module name="test" id="4">
<uid>{DB64B9DE-96AC-40C0-80F3-2142A7EF8E86}</uid>
<class name="class" id="5">
<class name="subclass" id="6"/>
<alias name="changeclass" id="7">
<value>#CLASS "class|subclass" 0</value>
</alias>
</class>
</module>
|
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jun 12, 2008 5:19 pm
|
Hmm, you are correct. That's definitely not working correctly. Thanks for the good test case...I'll add this to the bug list and try to fix it for v2.27.
|
|
|
|
|
|
|
|
