Pixel Events - Open Beta

[Gen. Hothauser]

How's it coming?

[Ad Bot]

[DrenDran]

I tried the mod and it didn't work.

[Plexious]

I tried the mod and it didn't work.

Elaborate.

[the_stitch]

this mod makes my brain hurt. i can't use it.

[Gen. Hothauser]

So, how's it coming?

[Plexious]

So, how's it coming?

I've extended the string length for the fields so you can use VCE. You'll have to disable PixelDebug to use this though.
As for the horizontal pixels it will take a bit of doing. Basically I just need to make the code more flexible.

[Gen. Hothauser]

I've extended the string length for the fields so you can use VCE. You'll have to disable PixelDebug to use this though.
As for the horizontal pixels it will take a bit of doing. Basically I just need to make the code more flexible.

Would you be able to update the mod with the extended fields for now?

[Plexious]

Would you be able to update the mod with the extended fields for now?

Updated

[DrenDran]

Elaborate.

It just didn't.
The pixels didn't even show up when I tried to create them.

[Gen. Hothauser]

It just didn't.
The pixels didn't even show up when I tried to create them.

Did you use the Pixel_Create output first, then use the Pixel_Color output?  Did you de-render the brick you did this on?

[Gen. Hothauser]

So I tried the pixel events with the elongated fields and VCE, and it didn't seem to work.  I am currently trying to make a mouse move one pixel across the screen.  I'd accomplish this by checking the screen's <var:br:X> and <var:br:Y> mouse position variables.

The following is for the left arrow key that is used in my mouse.

Code: [Select]

[0] [OnActivate] [NamedBrick > TV_Screen] [VCE_IfVariable] [X] [>] [1] [1 4]
[1] [OnVariableFalse] [NamedBrick > TV_Screen] [Pixel_Hide] [Rectangle] [<var:br:X> <var:br:Y>] [1 1]
[2] [OnVariableFalse] [NamedBrick > TV_Screen] [VCE_ModVariable] [Brick] [X] [Subtract] [1]
[3] [OnVariableFalse] [NamedBrick > TV_Screen] [Pixel_Color] [Rectangle] [<var:br:X> <var:br:Y>] [1 1] [37]
[4] [OnVariableFalse] [NamedBrick > TV_Screen] [Pixel_UnHide] [Rectangle] [<var:br:X> <var:br:Y>] [1 1]

This should, in theory, check if the mouse pixel is not on the last column of pixels (edge of screen).  If it isn't, the mouse pixel is hidden, a pixel to the left of the previous mouse pixel is recolored and unhidden, thus making it look like the mouse is moving.

I did the /disablepixeldebug command, and that let me type variables into the fields, but I don't think VCE works in the fields.

[Plexious]

I honestly have no idea how VCE functions. I'll have to look into the VCE code. I guess it wasn't as simple as just lengthening the fields.

EDIT: Fixed, tested, and updated.

[Gen. Hothauser]

I still can't seem to make it work.  I've tried every combination of IfValue, IfVariable, <var:nb_brick:variable>, etc. and still nothing seems to work.  What are you doing to test?

[Plexious]

I still can't seem to make it work.  I've tried every combination of IfValue, IfVariable, <var:nb_brick:variable>, etc. and still nothing seems to work.  What are you doing to test?

Make sure you're using the right events on the right bricks. If you save variable1 to brick1 any events on brick2 won't be able to access it, only brick1 will be able to. I suggest using global variables instead of brick variables.

[Gen. Hothauser]

Make sure you're using the right events on the right bricks. If you save variable1 to brick1 any events on brick2 won't be able to access it, only brick1 will be able to. I suggest using global variables instead of brick variables.

Your statement is false.  You can use [Self] [Ifvalue] [<var:nb_brick:variable>] or [NamedBrick-brickname] [Ifvalue] [<var:br:variable>] or [NamedBrick-brickname] [IfVariable] [variable] to check a variable on another brick.  Also, last time I checked (which was a few hours ago because, again, I went over every VCE aspect I could think of), you can't directly modify a global variable, those aren't even variables, they are values and can only be displayed (such as simtime, playercount, and pi).  And by "What are you doing to test?", I meant "What is the exact method with which you are testing whether VCE can affect pixels on the screen?".  I am trying to make a pixel appear to move from one location to an immediate other pixel, and my method should work if VCE would work with this.  I have reviewed every character I have entered into every field, making sure to use the correct combination of output to variable/value and self/namedbrick to nb_variable/variable.  In the code box I provided a bit ago, that string of events was on the screen itself, to make my life easier with movement and rechecking.  I used NamedBrick to indicated the name of the brick, despite doing so being useless had these events actually been made for the screen itself.  I mistakenly not used nb_X and nb_Y in those rectangle size indication fields because I made those events on the screen, and thus nb_variable was useless.  I'm sorry I didn't catch that mistake.