On 5/9/11 1:36 AM, David Glass wrote:
Definitely much more ... fluid/loose than I'm used to.
That's one of the hardest things for people to get used to if they come
from more structured languages. Eventually you start loving it.
The tool check won't hurt anything, so it wasn't really an err
Hmmm...I could have sworn I was getting resize interaction while trying
to edit, and as a result added that check.
Not happening now, so maybe it's just my unfamiliarity/lack of comfort
with the LC workflow (no edit-compile-test process) that's got me
misremembering.
Definitely much more ...
On 5/8/11 11:37 PM, David Glass wrote:
That subject is pretty bad, but I don't know how else to describe the
issue. :oops:
I have a multi-paned interface with one horizontal splitter, and one
vertical splitter. The code for the horizontal splitter looks like this:
-
on m
That was it! Weird.
Thanks!
On 05/08/2011 9:51 PM, Terry Judd wrote:
Maybe something to do with using a repeat loop within the
mouseMove handler.
--
David Glass - Gray Matter Computing
graymattercomputing.com
___
use-livecode mailing list
use-liv
Hi David - Maybe something to do with using a repeat loop within the
mouseMove handler. Here's a script for a split pane (horizonal split)
display out of a stack of mine that does something similar (ignore the
internal details of the mouseDown handler) and uses a flag to track the
status of the mou
That subject is pretty bad, but I don't know how else to describe the
issue. :oops:
I have a multi-paned interface with one horizontal splitter, and one
vertical splitter. The code for the horizontal splitter looks like this:
-
on mouseenter
if the tool is "
