 |
enema
Beginner
Joined: 06 Aug 2009
Posts: 11
|
 Posted: Mon Sep 14, 2009 5:27 am
Access violation error when using #cond
|
sorry for all the questions.
Why do i always get an access violation error when i'm using #cond?
Code:
#COND {*here*} {#ECHO next line}
EDIT:
and when it doesn't give me some sort of error the #COND part of the trigger doesn't work. Any previous code fires, but the condition doesn't seem to do anything at all. |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4715
Location: Pensacola, FL, USA
|
Posted: Mon Sep 14, 2009 1:11 pm
|
Are you using it when you have not already defined a trigger during the current session?
Otherwise it might not know what its a condition of.
| good wrote: |
#TR {this text} {do this}
#COND {that text} {do that} |
| bad wrote: |
| #TR {this text} {#COND {that text} {do this and that}} |
|
|
_________________
Discord: Shalimarwildcat |
 |
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Mon Sep 14, 2009 1:23 pm
|
This is likely specific to your session. I just tried it and got no errors at all.
It may actually be a sign that you settings are partially corrupt. I would recommend you make a back up your session, export your scripts, then reimport them into a new session.
[Edit] Shalimar's suggestion may be more your likely problem. |
|
_________________
Asati di tempari! |
|
|
|
|
|
|
