Jacqueline:
> Exactly 37 years. I remember because I started learning HC when
> my son was born in order to take my mind off diapers.
I like that! Every HC story is poetic, mine too.
Mike:
> it's amazing that even after...a really long time...
> there's still stuff to learn.
Plus the latest
Oh man yes Jacque and Mike! I do feel old, about the same for me, about late
87… grad school at Berkeley, humpback whales, and carrying Macs in big
backpacks. Later MetaCard saved the day!
Fun memories,
Jeff
> On Feb 22, 2024, at 1:51 AM, use-livecode-requ...@lists.runrev.com wrote:
>
> Exac
Exactly 37 years. I remember because I started learning HC when my son was
born in order to take my mind off diapers. If I remember, we can commiserate .
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 21, 2024 8:14:19 PM Mike K
pfft
there is zero chance of that
it's been, what 37 years?
man, i'm so old.
On Wed, Feb 21, 2024 at 8:35 PM Stephen Barncard via use-livecode <
use-livecode@lists.runrev.com> wrote:
> "there's still stuff to
> learn."
>
> . and remember .
> --
> Stephen Barncard - Sebastopol Ca. USA -
>
"there's still stuff to
learn."
. and remember .
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
On Wed, Feb 21, 2024 at 5:24 PM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> thanks, jacque & mark
> it's amazing that even after...a really long time...th
thanks, jacque & mark
it's amazing that even after...a really long time...there's still stuff to
learn.
On Wed, Feb 21, 2024 at 5:16 PM Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with
> messages’) que
It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with
messages’) queue any (low level) events so they are handled at the next wait
(in this case the global one the engine does implicitly when there are no
handlers executing).
Flushing events after the wait as Jacque suggests wil
That seems a little odd, I haven't noticed that. But one way to block the
messages is to use flushEvents() in the button script:
flushEvents("mouseDown")
flushEvents("mouseUp")
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 2
i did.
i have both a button, and a power button.
script:
*local* count
*on* mouseUp
*if* the disabled of me *then* *put* cr & "disabled" after msg
*add* 1 to count
*set* the enabled of me to false
*put* count
*wait* 2 second
*set* the enabled of me to true
*end* mouseUp
On Wed, Feb 21, 20
Mike.
In a new stack I placed a button with this:
on mouseUp
beep 2
end mouseUp
If I click on the button I hear two clicks. I disabled the button and clicked
on it. I enabled the button. No clicks. I did this all by hand. Did you?
Craig
> On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-liv
alright, i'm a little surprised to notice this:
i have a button. i disabled the button.
then i clicked on the button
then i re-enabled the button
the click, from the period while the button was disabled, is received and
processed by the button.
that seems problematic, to me. how would one cause cli
11 matches
Mail list logo