 |
DanteX
Apprentice
Joined: 13 Aug 2007
Posts: 166
|
 Posted: Thu Nov 12, 2009 9:00 am
[3.12] #ALARM stops working
|
This is a problem that constantly occurs to me...
My #ALARMs simply stop. I can see them in my settings editor, but they aren't executing... if I then just restart CMUD, it works again.
I don't understand how it can just stop...
Is this occuring to anyone else too? |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Nov 12, 2009 5:17 pm
|
There isn't any known bug on my list about alarms that stop. As always, you'll need to give me an exact procedure to reproduce the problem before I can fix it. We need to see the exact XML code for the alarm having problems.
|
|
|
|
|
DanteX
Apprentice
Joined: 13 Aug 2007
Posts: 166
|
Posted: Thu Nov 12, 2009 7:20 pm
|
This is very wierd... Many of my scripts are running simultaneously, and work fine most of the time, but screw up SOMETIMES. So I haven't been able to isolate it yet... would it help you if I sent you my entier settings file?
|
|
|
|
|
Yodous
Apprentice
Joined: 23 Jun 2004
Posts: 105
Location: Poland
|
Posted: Sun Nov 15, 2009 5:56 pm
|
Dantex i found out, that in beta versions sometimes my Alarm stoped working.
It was realy weird, becouse #ALARM +5 {} was working, and #ALARM +3 {} (with the same body) - doesn't.
I found out that the problem is in aliases, that was calling themselfs like:
Alias test:
| Code: |
#UNTRIGGER alarmTest
#ALRM alarmTest +3 {
//some operations
test
}
|
And as I already wrote - if there was for example +5 - it was working, but if there was +3, only the first time was fired and then it wasn't working.
I simply remove the body to another alias and leave it with:
Alias test:
| Code: |
#UNTRIGGER alarmTest
#ALRM alarmTest +3 {
anotherAlias
}
|
Alias anotherAlias:
| Code: |
//some operations
test
|
And that fiexd my problem.
PS. It all worked in the stable version, but I had to do this modification in the beta versions. |
|
|
|
|
DanteX
Apprentice
Joined: 13 Aug 2007
Posts: 166
|
Posted: Wed Nov 25, 2009 2:29 pm
|
After creating a completely new session, transfering scripts, using the new session, multiple modules, having a number of wierd crashes that almost all were reported using the built-in function... I'm back to a point where this a problem again. In that new session. And it's not only this... cmud freezes when I try to delete settings, I have more, random crashes, scoping problems with variables being written to windows that are marked...
I'm getting to the point where I don't know what to do. Atm I feel it's hopeless to continue trying to fix this stuff and simply return to zmud. |
|
|
|
|
DanteX
Apprentice
Joined: 13 Aug 2007
Posts: 166
|
Posted: Wed Nov 25, 2009 2:34 pm
|
I don't know if this also is in the bottom caused by a scoping problem...
I have this in a separate module:
[code]
#ALARM {+@temp4} {code}
[\code]
where temp4 is stored at the bottom of my main window, and not in the module containing the code.
But it is important to mention that it does work mostly, and that ALL my settings initially were in one module (the main window) that was imported from zmud. |
|
|
|
|
DanteX
Apprentice
Joined: 13 Aug 2007
Posts: 166
|
Posted: Thu Nov 26, 2009 11:39 am
|
I've noticed that after restarting CMUD due to this error, the mapper does not open automatically.
|
|
|
|
|
|
|
|
