Thank you, Mark. You’re very kind! And very helpful. I do remember now how one
needs to wait with messages.
Roger
> On Nov 8, 2020, at 9:05 PM, Mark Wieder via use-livecode
> wrote:
>
> On 11/8/20 8:02 PM, Mark Wieder via use-livecode wrote:
>> On 11/8/20 6:57 PM, Roger Guay via use-livecode
On 11/8/20 8:02 PM, Mark Wieder via use-livecode wrote:
On 11/8/20 6:57 PM, Roger Guay via use-livecode wrote:
Please tell me why this doesn’t work:
...and that is, btw, hardly a stupid question.
You want stupid you'll have to get in line after me.
--
Mark Wieder
ahsoftw...@gmail.com
_
On 11/8/20 6:57 PM, Roger Guay via use-livecode wrote:
Please tell me why this doesn’t work:
on mouseUp
put "start"
wait for 5 seconds
put "stop"
end mouseUp
“start” never appears in the message box and after 5 seconds, “stop” appears
The wait command is blocking a
Please tell me why this doesn’t work:
on mouseUp
put "start"
wait for 5 seconds
put "stop"
end mouseUp
“start” never appears in the message box and after 5 seconds, “stop” appears
___
use-livecode mailing list
use-livecode@li
The basic windows code signing cert works fine. You do not need the more
expensive "EV" certificate.
On 11/8/2020 12:58 PM, General 2018 via use-livecode wrote:
Hi ,
Are the standard Livecode .dll that are included with the standalone Kernel
mode drivers ??
The reason for asking is that code
Hi ,
Are the standard Livecode .dll that are included with the standalone Kernel
mode drivers ??
The reason for asking is that codesigning for Windows 10 needs a more expensive
certificate if kernel mode drivers signing is required.
Regards
Cam
___
u
This enhancement request (which from various paths has a 14 year history) is
still relevant IMHO:
https://quality.livecode.com/show_bug.cgi?id=4636
(It also has a handy suggestion from Mark Waddingham of a function to return
"ISO date time" (as the discussions in the report shows, a misnomer),