 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sun Oct 28, 2007 12:08 am
[2.09] Context issues
|
I think some discussion of this has been brought up before, maybe as early as the 1.2x version. However it is definitely an issue for me now, with the way the alarms behave it basically breaks all scoping. I believe the most recent discussion was with the PE right-click Execute Script, where it was decided to leave the contexting broken because it could be impossible to determine what window should have the context. Alarms like in this example don't have such an unclear situation though.
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter at the command line
| Code: |
| abc=def;#WINDOW test;:test:#EXEC "var=-1000;#ALIAS wtf {#SAY Found you};#ALARM *1 {#ADD var 1;#SHOW @var @abc;#IF (@var\10=0) {#VAR;#ALIAS;wtf}}" |
You will see this results in a variable 'var' being created in the untitled window, when the alarm is in another window. Of course the alarms of the test window should act on and use the variables of the test window. The #SHOW appears in the test window, but the variables accessed and changed are in the untitled window. The alias that is called every tenth time belongs to the test window, and doesn't exist according to the alarm, but guess what it does exist! |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Oct 29, 2007 9:21 pm
|
Confirmed. That's a good test to track down the problem and I honestly have no idea how that's happening. But I'll get it fixed.
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
