(adsbygoogle = window.adsbygoogle || []).push({}); I was making a menu and got annoyed by the fact I had to keep making the patch over and over trying to guess good X and Y values, So I made this function to move elements around the screen.

    

PosTest(D) {

switch(D) {

case "U":

self moveOverTime( .1 );

self.Moving[self.TestNum].y -= 5;

break;

case "D":

self moveOverTime( .1 );

self.Moving[self.TestNum].y += 5;

break;

case "L":

self moveOverTime( .1 );

self.Moving[self.TestNum].x -= 5;

break;

case "R":

self moveOverTime( .1 );

self.Moving[self.TestNum].x += 5;

break;

case "Re":

self iPrintln("x: " + self.Moving[self.TestNum].x);

self iPrintln("y: " + self.Moving[self.TestNum].y);

break;

case "Sw":

self.TestNum++; if(self.TestNum > self.Moving.size) { self.TestNum =0; }

self iPrintln("Editing " + self.TestNum);

break;

} }



LoopRun( function, event, input) {  

for(; {

self waittill( event );

self thread [[function]]( input );

} }

Make a function like this and add all the items you want to be able to move(shaders and text both work) to self.Moving. Don't forget to change "dpad_XXXX" to whatever controls your menu uses.

    

MenuDebug() {

self.Moving=[]; self.TestNum=0;

self.Moving[0]=self.scrollbar1;

self.Moving[1]=self.BackGroundHud;



self thread LoopRun( :osTest, "dpad_right", "R"); //Move Right

self thread LoopRun( :osTest, "dpad_left", "L"); //Move left

self thread LoopRun( :osTest, "dpad_up", "U" ); //Move Up

self thread LoopRun( :osTest, "dpad_down", "D"); //Move Down

self thread LoopRun( :osTest, "button_cross", "Re"); //Print X and Y values of current element

self thread LoopRun( :osTest, "button_square", "Sw"); //Switch to next element in self.Moving

}

Once you fine a good spot, print the X and Y then put the values as the X and Y for your element.
I might also add a way to scale the item up/down later...

Nice work man, if you want to make it even more in depth, make an options menu to go with it so you can do more things like change the relatives and what not.

do the 'self waittill( "DPAD_UP" );' ect.. work?, and after so long you just know where to posision then :p

I meant change them to the notify's that your menu uses. Obviously there is a way to get dpad buttons working, IW uses it for the game menu.

    

Shader( element )

{

	p = self createFontString( undefined, 2 );

	p setPoint( "TOPRIGHT" );

	for(;

	{

		element.y += attackButtonPressed();

		element.x += adsButtonPressed();

		p setText( element + " Y: " + element.y + "   " + element + " X:" + element.x );

		wait .3;

	}

}

Serious?

Super lag because no wait in function, probly will crash the game. setText would crash the game before you got anything useful done if the lag didn't.

it wont lag bad, its only setting a value.. but it does need a wait :p
i had a , in the setText because it was an iPrintln and forgot to change it ha.

It would do the loop a few thousand times per second. Each loop would set 2 variables, check if a 2 buttons are pressed or not and call the setText function. No lag at all.

but, it still works..

Hitting a door with a sledge hammer also works for getting through it, Doesn't mean you should do it.