Blue Eye Macro

i tried it and it works fine. Cheers!

Thank you. :mrgreen:

Pretty nice Macro
;) :)

Yep got it, Thanks.

[quote="hellomot0123"][quote="Gigus"]Did you try the new settings in version 2.1 to improve the performance of this macro?[/quote]


Unfortunately I have not, I've been really busy with coursework atm, which means no time for Blue-Eye :(.
Anyway, this would be a good time to ask how the 'send keys' or 'send mouse up' etc. functions actually work, I just can't seem to make sense of the argument descriptions that you provided. An example would be nice :).

[quote="BakT"]mouse click delay 5ms ;)

it sure is a neat macro :P i like it[/quote]

I'm Glad you like it, I made it because I wanted to draw as well as some of the other people there, but alas, even with this macro, the drawings they make are too good :P[/quote]


I just noticed i never actually gave you an answer for this question, instead I started talking about the configuration of pauses.
Sorry about that.

What Window.Send click does compared to Mouse.Click is just "tell" the window, that something occurred.

Here is one way to think of it which will make it quite clear how and when to use it.

If you Send a left click to a window, it will just "tell" the window that the left mouse button was clicked at the specified coordinates, when you do a Mouse.Click we actually simulate a click which involves moving the mouse cursor, and executing mouse clicks, which are all translated by windows, which will then tell the window below the cursor that a specific mouse button was clicked.

So what we do with Send Click is skipping one step, and telling the window directly (wrong, but a nice way to think of it) that this click was performed.

So, the good part about this, is that the window doesn't have to have focus, it could even be minimized, and you are still able to send clicks / keystrokes to it.

This can come very handy for e.g. game bots, imagine a bot playing a game, and you just minimize your game, and Blue Eye will keep playing.
And in the meantime, you can still use your mouse and keyboard for other things, since we never actually move the mouse or press any keys, we just "tell" the specified window something has occurred.

I'm going to share a bot for Perfect World soon (which has 3 times as many players as WoW I believe ;) ), this bot does exactly this, and reads everything from memory instead of color/pixel recognition, it is capable of playing the game all by itself, and automatically move from spot to spot as it levels up, and the best part is, the game can be minimized, and you can use your computer for other things in the meantime.

Ill also create a YouTube tutorial video of the making of it, to show how I located the base pointers in memory, and used them to know when to send what keys etc.


But to check out the Send keys/clicks you could just do a test with notepad, try the following code:
[code]
begin
// First we send some text
Window.Send keys("Notepad", "no", "Edit", "First some text")
// And then right click inside the text area
Window.Send mouse click("Notepad", "no", "Edit", "50", "50", "Right")
end
[/code]

I hope this answers your question :)

I don't see any problems with that, that should work just fine.

What if I had a virtual desktop open or something of the sort, with blue-eye open on one, and me just using my computer normally on the other, would that work?

I wish I had, however the case is, it is simply not possible due to the windows architecture.

The closest you can get, is a still image for a window, at the time it is minimized.

Thats what windows does in windows vista & windows 7.
When you hover programs in the task bar, it will show what the app looks like, however the case is actually, that it is just showing what it looked like the second before it was minimized.

The reason its not updated real-time, is obviously for performance reasons, as if windows had to continue to render in memory what a screen looks like even when its minimized, it would drain quite some resources.

So unfortunately this will never be implemented, simply because it cant be (to my knowledge).

However good alternatives is to get the data you need straight from memory, or using the Window.Get text feature.
Thats really the only two ways you can get information about what is going on in a minimized window.

[quote="Syrifina"]Warp speed achieved! See it in action (real time) here: http://www.youtube.com/watch?v=Lp6rJQV9xsg

I figured out that you don't need an additional program to make the window transparent. After
[code] Color.Freeze screen dump cache()
Color.Limit area of interest to coordinates("{x1}", "{y1}", "{TotalPixels1}", "{TotalPixels2}")[/code]
add
[code] Window.Restore("Untitled - Paint", "yes")[/code]

Then minimize Paint/Sketch Star; run macro. Also, if your trace is catching the last user input window, add a pause before the color.freeze.[/quote]


Good job Syrifina!

Trust me, if anything, im happy that you decided to improve my macro, and take it to a level where it functions so well, so don't worry about offending me haha!

Anyway Gigus, thx for the example, I got it perfectly, I was just confused as to what it actually did, but I was just being stupid - overcomplicating things. Just a small query though, I know you have implemented features to allow you to send keys and or mouse clicked to any window, but I was wondering if you would ever implement something that would allow you to find pixels patterns or images or anyhting of the sort of a minimised window? And if I'm just being silly again, and you have implemented it ...how do you do it!?! :P

god damit i just had same idea, to freeze, then change window :lol:
good job ;)

Well done!

Cant believe I didn't think of that :p

Really nice work :)