You can also turn off messages and errors from the Toolbar before you build. This should prevent any pre/open or pre/close scripts from running. And make sure all inspectors, message box and project browser are closed too as well as any windows/stacks other than your main stack.
Sean On Sun, 4 Apr 2021 at 13:57, Sean Cole (Pi) <s...@pidigital.co.uk> wrote: > ResolveID is referring to the stack, card and object IDs to tie it to your > breakpoints. > > Focus on your main stack. In the Development menu bar, choose Clear All > Breakpoints. It’s a good idea to do this every time before a main > standalone build. > > So, Delete all your breakpoints. Then resave. (Close and reopen your stack > and LC if you like). Rebuild. It will be ok. > > Sean > > On Sun, 4 Apr 2021 at 01:10, William Prothero via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> Matthias, or anybody: >> >> I got side-tracked but am back to needing to build this standalone and >> guess what the error message from the builder means. This build problem has >> been known for some time, as Matthias kindly notified me. >> >> My question is:Is it possible to tell what stacks are causing the >> problem, from the builder error codes. I have But it seems a bit odd that I >> would have to disable the preopenStack, openstack, closestack, preopencard, >> opencard, etc, etc ad-nauseum. >> >> Before I cause myself a bunch of thrashing around changing a bunch of >> stacks, is there anything in the error dialog that’s attached that would >> give me a hint as to where this is happening? Also, I wonder if disabling >> all these open …. handlers during build might cause build problems. If it >> was a universal problem/bug, I would think it would have been fixed by LC >> version 9.6.2 (RC3).??? >> >> Thanks for any insight and direction. (I”m on Big Sur 11.2.2). I have 10 >> stacks and a number of script only lib stacks in this project. >> >> Bill >> >> Links to the error dialog: >> page 1: https://www.dropbox.com/s/f4bmxx3zkuoy0zq/ErrorWindow-p1.png?dl=0 >> <https://www.dropbox.com/s/f4bmxx3zkuoy0zq/ErrorWindow-p1.png?dl=0> >> page 2: https://www.dropbox.com/s/zc18s3gkzv92w2w/Errors-page-2.pdf?dl=0 >> <https://www.dropbox.com/s/zc18s3gkzv92w2w/Errors-page-2.pdf?dl=0> >> >> > On Mar 20, 2021, at 1:38 PM, matthias rebbe via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> > >> > Bill, >> > >> > i've just checked the release notes of 9.0.x >> > The release notes of 9.0.2 contain updated information about this topic >> and an enhanced script example. >> > opencard scripts should also be adjusted. >> > https://downloads.livecode.com/livecode/9_0_2/LiveCodeNotes-9_0_2.pdf >> > >> > Please excuse me for pointing to 9.0.1rc1 release notes yesterday. >> > >> > >> > Regards >> > Matthias >> > >> > >> > >> > >> > >> > >> > - >> > Matthias Rebbe >> > Life Is Too Short For Boring Code >> > >> >> Am 20.03.2021 um 18:22 schrieb William Prothero via use-livecode < >> use-livecode@lists.runrev.com>: >> >> >> >> Matthias: >> >> I see that openstack and closestack messages are inhibited during >> application build, using: >> >> >> >> on closeStack >> >> if the mode of stack “revStandaloneProgress” > 0 then >> >> exit closeStack >> >> end if >> >> end >> >> >> >> So, before I start adding this to all openstack, closestack, scripts >> of my 12 stacks, I'm’ wondering if I could mess up the build process by >> by-passing some of the scripts in these handlers. Is there any way to tell >> more precisely what is causing the problem? Any recommendations on >> strategy? Should I just change one stack at a time and look for changes in >> the error window, or just change all them and wonder what affect that would >> have on the integrity of the build process? >> >> >> >> Also, opencard scripts are also called when a stack in launched and I >> wonder if those need to be escaped too. >> >> >> >> Best, >> >> Bill >> >> >> >>> On Mar 19, 2021, at 5:46 PM, matthias rebbe via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >>> >> >>> Another thing. I am not sure if your problems are also a result of >> the following, but you could giv it a try. >> >>> >> >>> There was something changed in Standalonebuilder process starting in >> LC 9.0 or so to fix a problem. But this fix could cause other problems in >> some situation. >> >>> While before that fix the main stacks did not receive any openstack >> and closestack messages during standalone build, now with the fixed >> standalone builder they do. >> >>> Therefore some lines of code need to be added to avoid this. >> >>> >> >>> See here on page 2 for an explanation what you have to add to your >> openstack and closestack handler >> >>> >> https://downloads.livecode.com/livecode/9_0_1/LiveCodeNotes-9_0_1_rc_1.pdf >> >>> >> >>> >> >>> - >> >>> Matthias Rebbe >> >>> Life Is Too Short For Boring Code >> >>> >> >>>> Am 20.03.2021 um 01:31 schrieb ELS Prothero via use-livecode < >> use-livecode@lists.runrev.com>: >> >>>> >> >>>> It’s mystifying that all messages seem to come from the rev builder >> scripts, with no hint of what could be the problem. >> >>> >> >>> _______________________________________________ >> >>> 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 >> >> >> >> William Prothero >> >> waproth...@gmail.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 >> > >> > >> > _______________________________________________ >> > 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 >> >> William Prothero >> waproth...@gmail.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 >> > -- > Pi Digital > -- Pi Digital _______________________________________________ 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
