LiveCode Forums.

hi!
i have an app in which the user can move object around. what will be the most efficient way of preventing them from dragging the object out of the screen?

tnx
tomer

Hi.

How are you moving the objects around?

In any case, the "mouseMove" message is sent whether in edit or run mode, so you could (pseudo): Silly, eh? But can you take it from there? To check either the mouseLoc in relation to the edges of the card, or, if you want to get fancy (and I always recommend fancifulness) check the edges of the object in relation to the edges of the card. The "target" is your friend here.

Write back with your fancies.

Craig Newman

Hi,
You may define a rect and test if all points of your control is within this rect at mousemove
Best regards
Jean-Marc

Learning to do this yourself is the best idea, but Animation Engine includes some very nice features including constraints to location.

i am moving the object with: where should i put this code that u wrote? in the card script?

Try something like this in the script of the object you’re moving:

local tStartLoc

on mouseDown
put the loc of target into tStartLoc
grab me
end mouseDown

on mouseUp
if the loc of target is not within the rect of this card then
move target to tStartLoc
end if
end mouseUp

Hi Tomerp,

what Randy wrote!

Important hint:

.. so you could (pseudo):

PSEUDO in this case means, this is what it should do, but is really NOT the actual script!


Best

Klaus

I did it DIFFERENTLY . . . . Stack removed as updated, improved version uploaded.

You ALWAYS do it differently!

This version allows one to resize the stack . . . .

...and if you want it to work for any size card, you can generalize the tests for right and bottom. (other than an 800x600 sized card in Richmond's example)

give the card a name (e.g. "main") and modify the code to check for instead of just .

and the instead of 600.

RATS,

I tried to get there with a more universal solution before you did (Richmond). But I went back to edit it and while I was editing it, you uploaded your new stack. So your time stamp was earlier than mine.

I like your idea of using variables for the right and bottom locations. It makes the code simpler reading.

Good job, nice example

It makes the code simpler reading.

That's because I really don't understand complex code.

Yes, I do too but sometimes when teaching newbies, you have to step through the process in logical steps (as you help them think thru it) Some people can not make the jump to the better code in one step.

To understand what happens when the stack is resized, and so that
the TROLL doesn't "get lost" when it is resized, you need to look at
the stackScript: