Blue Eye Macro

yes, glad you found it...just add curly brackets.

Define variables = no curly braces
Call variables = curly braces

P.S. Your next question (which you haven't posted yet) will probably be answered by my response on this page: viewtopic.php?f=122&t=20881

Resurrecting old thread.. I am wondering is it possible to pass variables as parameters into predefined BE functions? Such as:

Variable.Set("x_pat_pos", "0")
Variable.Set("y_pat_pos", "0")
Variable.Set("flag", "0")
Color.Find pixel pattern("", "20", "yes", "x_pat_pos", "y_pat_pos")
if Color.Pixel pattern can be located on screen("","")
begin
Mouse.Move to coordinate("Variable.x_pat_pos", "Variable.y_pat_pos")
Variable.Set("flag", "1")
end


Obviously this doesn't work (when pixel pattern is filled) or I wouldn't be asking! Lol. But is there a way of doing this in BE?

EDIT: Nevermind, found out I just needed curly braces around the variable names.

omar_a,

I can understand where you're coming from and I partially agree on that. However, the main goal for Blue Eye Macro is to cater the general audience, essentially those without programming skills. Sure it's wordy but there's a lot of non-programmers that understand this syntax and Blue Eye Macro has been released for about two years. To change the syntax so suddenly would more than likely backfire for the non-programmers as they would have to 're-learn' the syntax over again.

There has been a discussion on syntax changes before in the Ideas section of our board, however you are free to actually make plugins for this program as well, where you are free to write it in any code you want it in.

Would love to see a more programming-style implementation of variables.

Like...

Var myVariable = 9
Var myVariable2 = "a"

Or even adopt a sign/symbol to stand for variables (PHP uses $ quite nicely)
{myVariable} = 9
$myVariable = 9

However its done, with a nice standard and syntax, the un-needed variable "functions" can be removed as they would be done in-line like normal programming / scripting.
Im sure Gigus knows what I mean, but just to elaborate...

if myVariable = 9 then
if $myVariable = 9 then
if {myVariable} = 9 then
^-- all are nicer/ cleaner than if Variable.Is equal to("number", "1") (9)*
Variable being set or being evaluated via = based on whether the operation is unary or binary. That or just do like C++ and use == XD

Additionally, it would allow the `evaluate` function to be performed without needing to be called
myVariable = (2 * 3 + 7) + " units available to deploy"


All in all, I think it'd be a very nice addition / change.

Expansion Pack: Expanded on a FAQ concerning if variables work through functions and how it works.

Oh yes, there's also Pre-Defined Variables so I linked that on the guide at the bottom of my first post. If additional explanation is needed, I will write that down.

Hahaha, oh you.

I just make tutorials and such to my own accord and by request (when presented and asked formally).

Wow, that was a good post / tutorial. Well done!

And I guess it's also worth a thanks to @TLBunny for making you unlazy :p

When is your next holiday - so I can prepare some requests ^^ (joking). But I really enjoy those kind of posts!

You have my permission when they release and when you think they are deemable and corrected for technicalities.

That would be pretty cool, perhaps I could link to those articles from within the documentation pages - That also makes it easier to use them as future references for answering questions.