Sign in to follow this  
Followers 0
PartyPooper

@TRAY_ID [SOLVED]

5 posts in this topic

#1 ·  Posted (edited)

It's 4:20 in the morning so I'm probably missing something very simple. For some reason I can't work out why I keep getting the following Unknown macro error in the SciTE Console:

: ==> Unknown macro.:

MsgBox(0,'',@TRAY_ID)

MsgBox(0,'',^ ERROR

Syntax check passes it no probs, but it errors out on running. I get the same error with both the Production and Beta versions of AutoIt.

Edited by PartyPooper

Share this post


Link to post
Share on other sites



Hi,

Are your running your script as Opt("TrayOnEventMode",1) ?

Share this post


Link to post
Share on other sites

Hi,

Are your running your script as Opt("TrayOnEventMode",1) ?

Yes which is why I'm scratching my head over this one. Maybe just too :D

Share this post


Link to post
Share on other sites

This is working for me, even in Scite.

Opt ("TrayOnEventMode", 1)
Opt("TrayAutoPause", 0)

TrayCreateItem("Test")
TrayItemSetOnEvent(-1, "Mb")
TraySetState()

While 1
WEnd

Func Mb()
    MsgBox(0, "", @Tray_ID)
    Exit
EndFunc

George

Question about decompiling code? Read the decompiling FAQ and don't bother posting the question in the forums.

Be sure to read and follow the forum rules. -AKA the AutoIt Reading and Comprehension Skills test.***

The PCRE (Regular Expression) ToolKit for AutoIT - (Updated Oct 20, 2011 ver:3.0.1.13) - Please update your current version before filing any bug reports. The installer now includes both 32 and 64 bit versions. No change in version number.

Visit my Blog .. currently not active but it will soon be resplendent with news and views. Also please remove any links you may have to my website. it is soon to be closed and replaced with something else.

"Old age and treachery will always overcome youth and skill!"

Share this post


Link to post
Share on other sites

Yeah thanks guys - it was a stupid mistake on my part that was the ultimate cause. I'd forgotten to declare a passed parameter variable and the script just did weird things like dumping that error message. Of course it didn't help that I'd been hard at it for the last 36 hours. Ahh, the joys of programming :D:-)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0