move [variable v] to x:() y:() :: variables
([var v] x position :: variables reporter)
([var v] y position :: variables reporter)

set location of [var v] to x:(0)y:(0)::variables//default values are sprite's current position

Sheep_maker wrote:

I think only this block

set location of [var v] to x:(0)y:(0)::variables//default values are sprite's current position

is necessary, assuming that the center of a variable reader is the top-left corner.

define set position to x(a) y(b)
set [position v] to ((((a)+[240])mod[480])+((((b)+[160])mod[360])*[480])

go to x: (((position) mod [480])-(240)) y: (([floor v] of ((position)/[480]))-[180])

A-KouZ1 wrote:

Did you mean…? uses single variable for positioning?
woh that's easy workaround,

define set position to x(a) y(b)
set [position v] to ((((a)+[240])mod[480])+((((b)+[160])mod[360])*[480])

Well, if you want to read it, just do…

go to x: (((position) mod [480])-(240)) y: (([floor v] of ((position)/[480]))-[180])

Badly, forY Position, is does not support decimals

move [variable v] to x:() y:() :: variables
([var v] x position :: variables reporter)
([var v] y position :: variables reporter)

Breck- wrote:

Support for these:

move [variable v] to x:() y:() :: variables
([var v] x position :: variables reporter)
([var v] y position :: variables reporter)

Breck- wrote:

Support for these:

move [variable v] to x:() y:() :: variables
([var v] x position :: variables reporter)
([var v] y position :: variables reporter)

ivancr72 wrote:

No, it's “moving the variable”, not “storing a position on a variable”.

define glide variable to x:(x) y:(y) by(n) secs
set [temp x v] to (var x)
set [temp y v] to (var y)
set [timecyc v] to (timer)
repeat until <(timer)>((timecyc)+(n))>
    set [var x v] to ((temp x)+(((x)-(temp x))*(((timer)-(timecyc))/(n))))
set [var y v] to ((temp y)+(((y)-(temp y))*(((timer)-(timecyc))/(n))))
go to x: (var x) y: (var y)
end
    set [var x v] to (x)
set [var y v] to (y)

A-KouZ1 wrote:

ivancr72 wrote:

No, it's “moving the variable”, not “storing a position on a variable”.

Oh, I understand, somewhat like gliding variable thing, right?

define glide variable to x:(x) y:(y) by(n) secs
set [temp x v] to (var x)
set [temp y v] to (var y)
set [timecyc v] to (timer)
repeat until <(timer)>((timecyc)+(n))>
    set [var x v] to ((temp x)+(((x)-(temp x))*(((timer)-(timecyc))/(n))))
set [var y v] to ((temp y)+(((y)-(temp y))*(((timer)-(timecyc))/(n))))
go to x: (var x) y: (var y)
end
    set [var x v] to (x)
set [var y v] to (y)

Could try it?

maxhup010 wrote:

In scratch you can show a variable, but you have to drag it to where you want the information to be displayed… This is a massive limitation if you have multiple different screen layouts as you would have to base your layout around where the variable is… So if you could get a variable to go to a place on the screen (X & Y Coordinates) then you can have a User Interface that can adapt to the situation!

Hope that helps

show variable [ v] as [slider v]::variables

set position of list [ v] to x:() y:()::list

set size of list to width() height()::list

change [variable v] x by []::variables

change [variable v] y by []::variables

maxhup010 wrote:

Hey!

I have been working on a couple of projects that use movable window designs for a UI and have ran into some problems with the large variable showing where a couple of simple blocks could help! (These blocks would act similar to SOME motion blocks)

(These blocks could be under a little dropdown in variables to prevent scaring new scratchers away from variables… or not, whatever)

move [variable v] to x:() y:() :: variables
([var v] x position :: variables reporter)
([var v] y position :: variables reporter)

move [my variable v] to X: () Y: () ::variables