Glad to see it's working. I'm not the best eventer but I'll have a tutorial out by the official release.
Would it at all be possible to make output pixel checking events (I think doing this with VCE variables would be too disorganized). For my computer, to move things like the mouse, or check if the mouse is over an icon when the mouse button is clicked, I have to keep track of the pixel location of the mouse pixel on the screen. I do this by adding/subtracting from variables 'Moulove" and "MouseY", but doing it this way can have issues if any lag ensues. I like to refer to this system as a weak system, where the display and recording systems are separated - for all of my projects, I like to have strong systems, where the display system is based on the recording system, instead of separate from it.
This would be like having a daycycle, then using relays to keep track of time and have lights turn on when the relays make them turn on. This is a bad system, and so I made my own daycycle with events and the Environmental Control events.
That was an example that was easier for me to explain than for the computer, but the output check events would be like the following:
[input] [Self] [Pixel_IfPixel] [4 7] [Has Color] [23] [4-6]
and
[Input] [Self] [Pixel_IfPixel] [4 7] [Is Visible] [1] [4-6]
etc...
The output is called "Pixel_IfPixel". The first field is the coordinates of the pixel. The second field is a drop-down menu containing certain commands, such as "Has Color" or "Is Visible". The third field is the special params, where 1 is yes, 0 is no, and for color, the number is the colorid of the pixel. The last box is the range of events that this specific output triggers. This means there would also need to be an input that gets triggered by the "Pixel_IfPixel" output, so maybe something like "Pixel_OnTrue" and
"Pixel_OnFalse". Basically, the point in this is to make more sturdy system, with each part of the system more dependent on the system as a whole.
