What if you unload it.
Turn messages off. Load your stack and build it right away. Does that work?
Op vr 14 aug. 2020 17:25 schreef Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com>:
> The stack where building a Windows Standalone just stays on "Attaching
> Engine..." forever had no '
The stack where building a Windows Standalone just stays on "Attaching
Engine..." forever had no 'closeStack' handlers at all.
I added the following:
on closeStack
-build close issue--
if the environment is "development" and \
there is a stack "revStandalo
The Standalone Builder really needs to be a separate process.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.comhttp://www.
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
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
