It may be the issue with repeat loops that do not yield to the engine
periodically. This was an issue all the way back to MetaCard and I am
not sure if it has been changed since then.
Basicaly, running a lengthy repeat loop locks up the entire CPU until
the loop exits. If this is the problem then it isn't just your
standalone that comes to a halt, it's everything currently running on
the machine.
The first couple of paragraphs here describe the problem:
<http://www.hyperactivesw.com/resources_polling.html>
On 12/24/19 1:04 PM, Tom Glod via use-livecode wrote:
Hi Peter, thanks, you are right the wait command does eliminate the window
lock up.... but my question was more so about why the Livecode IDE (with
open file A)...seems forced to share the same cpu core with Standalone of
file A.... and if anyone else has come across that before....they lock up
in tandem...when the OS should be designating cores more intelligently than
that. *shrug*
On Tue, Dec 24, 2019 at 5:51 AM Peter Reid via use-livecode <
use-livecode@lists.runrev.com> wrote:
Hi Tom
I'm not sure about Windows 10 behaviour but I had a similar problem with
Windows 7. It seemed that my LC app was not releasing the processor long
enough to handle basic user I/O. The solution was to add the following to
all my tight loops:
wait 0 milliseconds with messages
The 'with messages' is the key element, this made the LC app hand back
control to Windows to handle other system activities. I add this line to
all my loops when running under Windows. Give this a try and let me know
whether this helps.
Peter
--
Peter Reid
Loughborough, UK
On 23 Dec 2019, at 5:00pm, use-livecode-requ...@lists.runrev.com wrote:
Date: Mon, 23 Dec 2019 10:42:31 -0500
From: Tom Glod <t...@makeshyft.com <mailto:t...@makeshyft.com>>
To: How to use LiveCode <use-livecode@lists.runrev.com <mailto:
use-livecode@lists.runrev.com>>
Subject: a windows 10 wtf
Message-ID:
<
capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com
<mailto:capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com
Content-Type: text/plain; charset="UTF-8"
Hi Peeeps,
So I have a standalone running 24/7 that was built with LiveCode.
When I use Livecode the IDE to work on the application (that I am also
running as a standalone), and the IDE locks up for whatever
reason...being
busy or whatever..... my standalone application also locks up (window
become unresponsive). As soon as the IDE is responsive again, so is my
standalone window.
I have a 4 core machine...and nothing else seems to be locking up....
just
the IDE and the standalone.
Why is the OS insisting on the 2 processes sharing a core?
Has anyone come across this before?
Happy Holidays and Merry Christmas to all those who celebrate it.
--
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com <http://www.makeshyft.com/>)
Office:226-706-9339
Mobile:226-706-9793
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
