More Standalone Building Weirdness...
paul at researchware.com
Fri Aug 14 11:24:00 EDT 2020
The stack where building a Windows Standalone just stays on "Attaching
Engine..." forever had no 'closeStack' handlers at all.
I added the following:
-----------------build close issue----------
if the environment is "development" and \
there is a stack "revStandaloneProgress" and \
the mode of stack "revStandaloneProgress" > 0 then
An there was no change in behavior. Under LC960 (I have not tried other
versions), it builds the standalone, but then just remains on "Attaching
engine..." and I have to force LC to exit.
If no one else has seen anything like this, then it is probably
something about the stack. I don't have problems building other
standalones in LC960.
On 8/13/2020 1:06 PM, JeeJeeStudio via use-livecode wrote:
> Put this in every stack you build, and i mean the "build close issue" part
> in the on closeStack Handler
> It was in one of the release notes.
> Maybe that is holding your build to complete
> on shutdownRequest
> answer question "Are you sure you want to stop?" with "Y" or "N"
> if it is "Y" then
> pass shutdownRequest
> end if
> end shutdownRequest
> on closeStack
> -----------------build close issue----------
> if the environment is "development" and \
> there is a stack "revStandaloneProgress" and \
> the mode of stack "revStandaloneProgress" > 0 then
> exit closeStack
> end if
> lock messages
> quit --triggers shutdownrequestmessage, if not handled then it hangs
> pass closeStack
> end closeStack
> Op wo 12 aug. 2020 om 20:32 schreef Paul Dupuis via use-livecode <
> use-livecode at lists.runrev.com>:
>> I have a stack that when I build into a Windows Standalone (only
>> Windows) in LC 9.6.0 under Windows, the dialog that says "Attaching
>> Engine..." never finishes.
>> The Standalone gets built and runs properly, but the "Attaching
>> engine..." dialog in the building process never finishes (waiting over
>> an hour for a tiny stack) and I have to bring up teh Task Manager and
>> force the LiveCode app to exit.
>> Anyone seen anything like this? Have any idea what causes it?
>> Since the app does get built and runs fine, and I am under a deadline, I
>> don't really have time to troubleshoot it. It is easier to just force LC
>> to exit, but if someone has seen this and knows the cause, please let me
>> Thanks in advance.
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode