Re: More Standalone Building Weirdness...
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 'closeStack' handlers at all. > > I added the following: > > 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 > --- > pass closeStack > end closeStack > > 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@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 > >> know. > >> > >> Thanks in advance. > >> > >> ___ > >> 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 > >> > > ___ > > 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 > > > ___ > 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 > ___ 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
Re: More Standalone Building Weirdness...
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 "revStandaloneProgress" and \ the mode of stack "revStandaloneProgress" > 0 then exit closeStack end if --- pass closeStack end closeStack 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@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 know. Thanks in advance. ___ 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 ___ 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 ___ 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
Re: More Standalone Building Weirdness...
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.FourthWorld.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
Re: More Standalone Building Weirdness...
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@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 > know. > > Thanks in advance. > > ___ > 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 > ___ 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
More Standalone Building Weirdness...
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 know. Thanks in advance. ___ 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
Standalone Building
Hi all. On the issue of Standalone Building with a call to open stacks modally in a script, I noted that I can suppress messages and then build the standalone without issue. I am wondering if this doesn't cause problems for the standalone builder, why not have the standalone builder save the current setting and suppress messages before it begins the build brocess, then restore the prior setting when it's done? Bob S ___ 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
Re: Standalone Building for multiple platforms
I have a similar issue when I even build for one platform, except with behavior stacks. After the build, all the behaviors unload and the stacksInUse is reset. Every time I build I have to preOpenStack to get the other stacks back in. On Wed, Oct 25, 2017 at 11:34 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi all. > > Not sure if this would qualify for a bug, but I think the issue where > building for multiple platforms failing for a variety of reasons can be > resolved, if the Standalone Builder simple CLOSED ALL STACKS before > building for the next platform. I just build for Windows, and now what > ought to be a main stack with a number of substacks has all the substacks > as main stacks, and any attempt to open the original file causes all kinds > of problems. I have to actually quit Livecode after buildign for each > platform individually. > > Should I submit this as a bug? Should be pretty simple to fix. > > Bob S > > > > ___ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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
Standalone Building for multiple platforms
Hi all. Not sure if this would qualify for a bug, but I think the issue where building for multiple platforms failing for a variety of reasons can be resolved, if the Standalone Builder simple CLOSED ALL STACKS before building for the next platform. I just build for Windows, and now what ought to be a main stack with a number of substacks has all the substacks as main stacks, and any attempt to open the original file causes all kinds of problems. I have to actually quit Livecode after buildign for each platform individually. Should I submit this as a bug? Should be pretty simple to fix. Bob S ___ 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
Re: sloooowww standalone building with many included files
No, this one hasn’t been submitted yet. The app is about 85 MB, maybe around 90 once we’re all done with the audio. Very small audio files. Just a narrator saying a single word in each one. We’ve done this kind of thing before and never had any problems. On May 27, 2014, at 2:49 PM, Bob Sneidar bobsnei...@iotecdigital.com wrote: Apple let an app through with 8500 audio files attached? How big is the app when compiled? Bob On May 22, 2014, at 11:29 , Chris Sheffield cmsheffi...@icloud.commailto:cmsheffi...@icloud.com wrote: So I have an app. An iOS app. This app includes lots and lots of small audio files (nearly 8500). ___ 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 ___ 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
Re: sloooowww standalone building with many included files
Apple let an app through with 8500 audio files attached? How big is the app when compiled? Bob On May 22, 2014, at 11:29 , Chris Sheffield cmsheffi...@icloud.commailto:cmsheffi...@icloud.com wrote: So I have an app. An iOS app. This app includes lots and lots of small audio files (nearly 8500). ___ 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
sloooowww standalone building with many included files
So I have an app. An iOS app. This app includes lots and lots of small audio files (nearly 8500). All those files are in a folder, which is included in the Copy Files pane of the standalone build settings. Creating the build works just fine, but it takes a very long time. I haven’t kept track exactly, but probably close to 10 minutes. Maybe not quite. Anyway, can anyone think of a way to speed this up? I tried creating my own routine to copy that folder into the app bundle in a savingMobileStandalone handler. This worked very well as far as the copying goes. I used revCopyFolder and it worked great and was very quick. It probably only took about 20 seconds to create the build, if that. Unfortunately, it appears that the signing of the app takes place *before* what happens in the savingMobileStandalone handler, which seems to be invalidating the signature, as the app bundle is being modified after the signing. I was able to manually install the app on my device and run it just fine, but once I uploaded the build to Testflight for testing purposes, no one was able to download and install it successfully from there. So any thoughts? Or should I create an enhancement request to see if the build process can be sped up a bit. Not sure why it takes so long, when revCopyFolder is quite fast. Thanks, Chris -- Chris Sheffield Read Naturally, Inc. www.readnaturally.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
Re: sloooowww standalone building with many included files
I know. You’d think so. But it’s not the signing of the app that takes a long time. It’s the copying of the files into the app bundle. At least, that’s the step that’s shown in the standalone builder progress dialog. The actual signing is quick. On May 22, 2014, at 1:39 PM, Mike Kerner mikeker...@roadrunner.com wrote: You don't think it would have anything to do with signing an app that has 8500 files in it, do you? I would bet that THAT would take forEVER On Thu, May 22, 2014 at 2:29 PM, Chris Sheffield cmsheffi...@icloud.comwrote: So I have an app. An iOS app. This app includes lots and lots of small audio files (nearly 8500). All those files are in a folder, which is included in the Copy Files pane of the standalone build settings. Creating the build works just fine, but it takes a very long time. I haven’t kept track exactly, but probably close to 10 minutes. Maybe not quite. Anyway, can anyone think of a way to speed this up? I tried creating my own routine to copy that folder into the app bundle in a savingMobileStandalone handler. This worked very well as far as the copying goes. I used revCopyFolder and it worked great and was very quick. It probably only took about 20 seconds to create the build, if that. Unfortunately, it appears that the signing of the app takes place *before* what happens in the savingMobileStandalone handler, which seems to be invalidating the signature, as the app bundle is being modified after the signing. I was able to manually install the app on my device and run it just fine, but once I uploaded the build to Testflight for testing purposes, no one was able to download and install it successfully from there. So any thoughts? Or should I create an enhancement request to see if the build process can be sped up a bit. Not sure why it takes so long, when revCopyFolder is quite fast. Thanks, Chris -- Chris Sheffield Read Naturally, Inc. www.readnaturally.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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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 ___ 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
RE: sloooowww standalone building with many included files
Mike, I found that zipping them up and doing an unzip on first launch was the best compromise. I have an unzip function that will replicate a directory tree if you're interested. It works for Android and iOS. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Mike Kerner Sent: Thursday, May 22, 2014 3:39 PM To: How to use LiveCode Subject: Re: slwww standalone building with many included files You don't think it would have anything to do with signing an app that has 8500 files in it, do you? I would bet that THAT would take forEVER On Thu, May 22, 2014 at 2:29 PM, Chris Sheffield cmsheffi...@icloud.comwrote: So I have an app. An iOS app. This app includes lots and lots of small audio files (nearly 8500). All those files are in a folder, which is included in the Copy Files pane of the standalone build settings. Creating the build works just fine, but it takes a very long time. I haven’t kept track exactly, but probably close to 10 minutes. Maybe not quite. Anyway, can anyone think of a way to speed this up? I tried creating my own routine to copy that folder into the app bundle in a savingMobileStandalone handler. This worked very well as far as the copying goes. I used revCopyFolder and it worked great and was very quick. It probably only took about 20 seconds to create the build, if that. Unfortunately, it appears that the signing of the app takes place *before* what happens in the savingMobileStandalone handler, which seems to be invalidating the signature, as the app bundle is being modified after the signing. I was able to manually install the app on my device and run it just fine, but once I uploaded the build to Testflight for testing purposes, no one was able to download and install it successfully from there. So any thoughts? Or should I create an enhancement request to see if the build process can be sped up a bit. Not sure why it takes so long, when revCopyFolder is quite fast. Thanks, Chris -- Chris Sheffield Read Naturally, Inc. www.readnaturally.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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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 ___ 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
Re: standalone building and externals as inclusions
I'm going to guess that it puts the external into the same folder as the mainStack. And I do not know what you mean by one object per external or one for all. I imagine each external is it's own file. One way to tell would be to add a couple of externals, compile a standalone, then look to see where LC put them. That is what I would do anyway. Bob On Jul 29, 2012, at 11:25 AM, Dar Scott wrote: How does the standalone builder integrate externals into a standalone? In particular, where does it insert them in the path? And does it use one object per external or one for all? ___ 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 ___ 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
Re: standalone building and externals as inclusions
On 7/29/12 1:25 PM, Dar Scott wrote: How does the standalone builder integrate externals into a standalone? It creates a folder named Externals in the same folder as the engine/mainstack. On Mac, that's inside the bundle. On Windows it's next to the standalone. However, there is (was?) a bug where the external files themselves didn't actually get copied. You have to move them there yourself after the build. In particular, where does it insert them in the path? Into the back, I believe. And does it use one object per external or one for all? I'm not sure what this means. The externals are available in the file directory and your scripts load them into RAM. They aren't attached to any stacks per se, though you can use the externals property of a stack to tell the engine to automatically load them. -- 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
standalone building and externals as inclusions
How does the standalone builder integrate externals into a standalone? In particular, where does it insert them in the path? And does it use one object per external or one for all? ___ 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
