That would make a good LiveCode article.
Bob
On Jun 24, 2011, at 10:39 AM, Richard Gaskin wrote:
> Nicolas Cueto wrote:
>
>> mouseStillDown, for example. When part of a script set as a behavior,
>> mouseStillDown would not work. But that same script with the same
>> mouseStillDown handler, wh
On 6/24/11 12:39 PM, Richard Gaskin wrote:
In addition to handling simple drags like a splitter, drag-and-drop
operations can be handled using the messages provided for those
(dragStart, dragMove, dragDrop, dragEnd) far more simply than emulating
drag-and-drop behaviors with mouseStillDown.
Un
Nicolas Cueto wrote:
mouseStillDown, for example. When part of a script set as a behavior,
mouseStillDown would not work. But that same script with the same
mouseStillDown handler, when actually stored as a button's script,
worked as expected.
In a way that's kinda good news, as mouseStillDown
> In what way?
mouseStillDown, for example. When part of a script set as a behavior,
mouseStillDown would not work. But that same script with the same
mouseStillDown handler, when actually stored as a button's script,
worked as expected.
One other thing I noticed during development and had though
Nicolas Cueto wrote:
I've just learnt a new handler, mouseStillDown, and, more significantly, that
behavior scripts don't handle mouse handlers as expected.
In what way?
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode deve
> Be careful if you plan to build this into an app. You can't set a script to
> more than 10 lines in a standalone.
Woah, thanks Jacqueline!! My script does indeed have umpteen more lines than 10.
A question then: if I clone a group containing a button object with
script ABC, will the button of t
On 6/23/11 10:39 PM, Nicolas Cueto wrote:
Hold the presses!
I've just learnt a new handler, mouseStillDown, and, more
significantly, that behavior scripts don't handle mouse handlers as
expected.
So my solution has been to use "set script of X to" and not "set
behavior of X to".
Be careful i
Hold the presses!
I've just learnt a new handler, mouseStillDown, and, more significantly, that
behavior scripts don't handle mouse handlers as expected.
So my solution has been to use "set script of X to" and not "set behavior of X
to".
Script and learn.
--
Nicolas Cueto (iPhone)
__
If I've got what you're trying to do right then I'd try the following
approach
1. set two script locals on mouseDown - the first that the mouse is down
(pDown) and the second the starting mouseLoc (pLoc)
2. in a mouseMove hander, check if pDown is true and if it is then show a
'selection' graphic
Actually, I'm not sure working with mouseDown is what'll help with what I'm
after.
Say there's a grid of grouped objects thus:
A. B. C.
D. E. F.
G. H. I.
J. K. L.
and underneath that grid is a graphic
"gcBkgnd"
which is opaque and a few pixels larger than the grid.
The effect I've s
10 matches
Mail list logo