 |
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
 Posted: Sat Mar 15, 2008 8:13 am
[2.20] Compatibility Report Crash
|
When I run the compatibility report CMUD crashes on me. I narrowed it down to my prompt trigger because I have a #PCOL in the value. I created a test trigger in a new session with #PCOL and it works fine with no crash when running a compatibility check.
I think this is related to my other posts too and has something to do with when I import my XML files something is getting corrupted somewhere behind the scenes. |
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Sat Mar 15, 2008 2:42 pm
|
Meh sorry I can't come up with a procedure to reproduce this, but it is impossible to use the compatibility report. It just crashes on random crap.
For instance, it shows it was compiling this alias when it crashed Cmud.
Alias: aliasname
Value: #variable %1 0 |
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sat Mar 15, 2008 3:27 pm
|
Doing a little bit of import testing from my full original zMud settings I was able to find something that demonstrates a problem with the compatibility report cosnsitently. For the most part the report seems to be right, but there are some odd errors occuring with it.
Procedure
1. Launch CMud
2. Close Sessions Window (ESC)
3. Open Package Editor (CTRL-G)
4. Right click in the tree panel and paste
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger type="Alarm" priority="10" copy="yes">
<pattern>*.501</pattern>
<value>#WINDOW Channels
#WINDOW Room
</value>
<trigger type="Manual"/>
</trigger>
</cmud> |
5. Bring PE to front (CTRL-G)
6. Select Compatibility Report from the PE File menu |
|
_________________
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:28 pm
|
I didn't get any errors associated with this. But I was using the Pro version (although that shouldn't make a difference).
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Mar 17, 2008 5:26 pm
|
I was able to reproduce this. Even after the compatibility report, if you click on the Alarm trigger and then click on the Compiled Code tab, it will say that it has an error. The same script in a normal trigger compiles fine. So it's something wrong with the alarm code somehow. Anyway, I've added this to the bug list.
|
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Fri Apr 04, 2008 11:26 pm
|
Still broken in 2.21.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Apr 04, 2008 11:59 pm
|
Yep, sorry about that. I fixed it in the Settings Editor, but not in the Compatibility report. I put it back onto the bug list, but I didn't see this in time to fix it in v2.22, so it will have to wait until the next version (which unfortunately won't be for another month or so).
|
|
|
|
|
|
|
|
