ray at linkit.com
Tue Oct 29 13:51:43 EDT 2013
That's what I was afraid of. Thanks for the code ideas. Maybe I'll
post something on the improve list. It would be useful if the move
command returned something so more than just moving object could be done.
On 10/29/2013 1:34 PM, Ender Nafi Elekcioglu wrote:
> Hi Ray,
> I’ll just state the obvious.
> According to dictionary,
> the only message related to *move* command is “moveStopped”.
> That’s not good for your task.
> It seems that, the only solution you can implement is constructing
> your own “move” handler.
> Something as follows, maybe:
> _ on mouseUp
> __ put the long id of img myImage into tObjectID
> __ put the points of grc myPoints into tPoints
> __ send “moveObjectToPoints tObjectID, tPoints” to me in 0 milliseconds
> _ end mouseUp
> _ on moveObjectToPoints pObjectID, pPoints
> __ put pPoints into tPoints
> __ put pObjectID into tObjectID
> __ set the loc of tObjectID to line 1 of tPoints
> __ delete line 1 of tPoints
> __ # do your thing, rotate, blend, etc.
> __ if the number of lines of tPoints > 0 then
> ____ send “moveObjectToPoints tObjectID, tPoints” to me in 0 milliseconds
> __ end if
> _end moveObjectToPoints
> ~ Ender Nafi
More information about the Use-livecode