Thanks to all of you for questions and suggestions.
Bob : unfortunately no, user shall not have to specify names of buttons
Craig: no, button scripts shall not have to be pre-modified, they are of
several kinds, scripted by stack handlers
Mike: I have been experimenting a lot with your script, it
Thanks for replies
John: if a mouseenter can do the job, I guess that would be OK, -does this
suggestion imply, that Altclick cannot be used ?
Craig: Unfortunately modifying button scripts is out of the question
I am afraid, that I need a step by step, line by line, guidance in this
I paste my lat
way perhaps through a "Wait until condition", but don't know how to
formulate such script. I am also uncertain: Is the use of the ALT-click a
realistic strategy to get hold of the button-IDs?
I cannot imagine that something like this should be impossible in livecode
Happy New Ye
To James
Thank you for new reply to my first question
Because month-shift and time-differences you missed my followup:
I repeat it here
The previous replies suggested to produce new buttons and specify new scripts
for the buttons.
But the buttons will already be named and produced by the user
Thank you for replies to my first question (I repeat it, as October postings
not included here) :
"I have been experimenting to create a handler (as button or menu), which will
permit user
a)To select two existing moveable button
b)Create a line, attaching its endpoints to the buttons, so line w
patient/citizen diary www.phenomenalog.dk<http://www.phenomenalog.dk>
Best regards
Kresten Bjerg kresten.bj...@psy.ku.dk<mailto:kresten.bj...@psy.ku.dk>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url