I have a handler that calls itself over and over by sending a message "in time". It does its thing continuously until I manually terminate it. Control is, of course, regularly returned to the user each iteration.
I have a button with an "ask" command in its script. When I open the "ask" dialog, keyboard text entry is both delayed and scrambled.
None of this is surprising, since the "running" handler is always, er, running. I understand that keyboard text entry competes for processing time with that handler.
I do not want the running handler to pause, so I do not want to put the blocking ask command in-line.
I bet not, but is there a way to have my cake after I have already digested or (er...never mind) it?
Craig
Ask dialog not "blocking"
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 10055
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: Ask dialog not "blocking"
Modal execution in LC is blocking by nature, including the Ask and Answer modal dialogs.
But since it's a single field and a button, you could probably make a non-blocking top-level, palette, or modeless custom stack for that easily enough.
But since it's a single field and a button, you could probably make a non-blocking top-level, palette, or modeless custom stack for that easily enough.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn