of grc "c1" in 10 seconds
>>> end mouseUp
>>>
>>> and all should be fine, but it isn't, because on attempted execution
>>> of the button I get this:
>>>
>>> "button "GO": execution error at line 2 (move: end point is no
,,Richmond.
I was using your first posts handlers.
Craig
-Original Message-
From: Richmond
To: How to use LiveCode
Sent: Wed, Jul 27, 2016 9:59 am
Subject: Re: Move to the points
Usual nonsense: replying to my own postings:
The problem lies in my relying on put (KOUNT * 10) into
,Richmond
I get no errors at all with your handlers. The figure-8 draws fine, and the
tracking is lovely.
Craig
-Original Message-
From: Richmond
To: How to use LiveCode
Sent: Wed, Jul 27, 2016 9:46 am
Subject: Move to the points
So I have a graphic object generated like this
Usual nonsense: replying to my own postings:
The problem lies in my relying on put (KOUNT * 10) into LYNE
to supply me with continuous line numbers for my listField, now sorted out:
on mouseUp
put empty into fld "f1"
put 0.1 into KOUNT
put 1 into LYNE
repeat until KOUNT > 12.6
Of course part of this could be the problem that my initial curve
generation script leaves empty lines in
the listField that contains the points of the curve.
R.
On 27.07.2016 16:44, Richmond wrote:
So I have a graphic object generated like this:
on mouseUp
put empty into fld "f1"
put
So I have a graphic object generated like this:
on mouseUp
put empty into fld "f1"
put 0.1 into KOUNT
repeat until KOUNT > 12.6
put (KOUNT * 10) into LYNE
put ( ( ((sin (KOUNT)) * (cos (KOUNT)) ) * 300) + 400) into LR
put cos (KOUNT)) ) * 300) +400) into TB
pu
You could also have a look to the forum:
moving multiple objects (SOLVED)
http://forums.livecode.com/viewtopic.php?p=137583#p137583
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Move-to-the-points-tp4706104p4706110.html
Sent from the Revolution - User mailing
moveStopped
Thanks so much.
Richmond.
On 26.06.2016 21:03, Dar Scott wrote:
Also of interest might be the moveStopped message.
On Jun 26, 2016, at 10:36 AM, J. Landman Gay wrote:
Use the "without waiting" syntax for the move command, which allows messages to be
generated normally. Then se
Also of interest might be the moveStopped message.
> On Jun 26, 2016, at 10:36 AM, J. Landman Gay wrote:
>
> Use the "without waiting" syntax for the move command, which allows messages
> to be generated normally. Then set up a "send in time" structure that checks
> the movimgControls, and i
Thanks, both.
Meanwhile, I came up with another way of doing things
[Isn't THAT the best thing about Livecode?
That there are almost always many ways to achieve one thing.]
So, my script looks a bit like this:
on mouseUp
put the points of grc "myTRACK" into fld "myTRAK"
put 1 into KOUNT
Use the "without waiting" syntax for the move command, which allows
messages to be generated normally. Then set up a "send in time" structure
that checks the movimgControls, and if the object of interest is in there,
change its icon.
On June 26, 2016 10:31:43 AM Richmond wrote:
It seems th
Both move and wait commands are blocking commands. Now messages are acted upon
when the code runs. If you would like several things happen at the same time
you would need to use “send to me in time” where you then would have to check
current position and set the new position based on this. You c
It is very easy to draw and/or generate a *multi-point vector path* on a
stack
and then *animate* a control to move along it like this:
*move* the *btn* "button" to the points of the *graphic* "wiggle" in 30 secs
but is looks, frankly, bl**dy silly except in the most trivial of instances.
So I
13 matches
Mail list logo
