Re: Help! I'm stuck

[William Prothero via use-livecode]

Richard:
What you suggest makes a lot of sense. As someone who doesn’t build complex 
apps very often, my first question is “why would I turn off error 
notifications?” Would I miss something by turning them off when making a build? 
Anyway I think it would be far more straightforward to just have a different 
(linked) app to do the build.

Also, if there is a separate app, why couldn’t it take care of a lot of the 
mystery of notarizing, adding certificates, etc, at the same time? That would 
be a huge help. Maybe it could even include an installer. Yikes, I would even 
pay a bit for that capability.

Best,
Bill

> On Apr 8, 2021, at 9:43 AM, Richard Gaskin via use-livecode 
>  wrote:
> 
> Standalone building needs to be moved to a separate process.
> 
> Handling it within the IDE process was fine as long as the only thing the 
> Standalone Builder did was bind a copy of the engine to a copy of the stack 
> file.
> 
> But today, building a standalone means deep modifications to the stack file, 
> and this has resulted in multiple successive layers of knock-on effects where 
> design complications are needed to compensate for design complications put in 
> place to compensate for earlier design complications.
> 
> The end result of attempting to build standalones within the current IDE 
> process is not merely cumbersome, but disruptive, confusing, and even 
> requires CODE CHANGES from EVERY USER to compensate even further just for the 
> build sequence.
> 
> LC has gone from the simplest way to build apps to something no less onerous 
> than most, and more confusing than many.
> 
> Standalone building needs to be moved to a separate process.
> 
> With that, LC can begin the return journey back on its path to the simplest 
> way to build apps.
> 
> --
> Richard Gaskin
> Fourth World Systems
> 
> 
> 
> Ralph DiMola wrote:
> 
> > I never built a non-mobile standalone for the first 5 years of using
> > LC. For a mobile build nothing gets closed and gets built from the
> > stack(s) files on disk. What a surprise I got when I built my first
> > desktop standalone. I initially thought that something was very wrong
> > with the IDE and restarted.
> > After some searches I found that this is the correct behavior??? I
> > guess there is a reason for closing the stack(s) but I find it very
> > odd indeed.
> >
> > Ralph DiMola
> 
> 
> ___
> 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

Re: Help! I'm stuck

[Sean Cole (Pi) via use-livecode]

That **would** be good. I see what you mean.


On Thu, 8 Apr 2021 at 18:36, Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> It would be a separate application, but would still be called from the IDE
> like today.  One difference is that as a separate process it would not
> disrupt the current session inside the IDE.
>
> Sent from my iPhone
>
> > On Apr 8, 2021, at 1:21 PM, Sean Cole (Pi) via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Hi Richard,
> >
> > When you say a separate process, do you mean have the standalone builder
> as
> > a separate application from the IDE? Why could it not be accomplished in
> > the IDE where it is more convenient?
> >
> > Handling it within the IDE process was fine as long as the only thing
> >> the Standalone Builder did was bind a copy of the engine to a copy of
> >> the stack file.
> >>
> >
> > Forgive my lack of knowledge, but when we compile it to an application
> for
> > different platforms, what are the differences from one platform build to
> > another, particularly regarding where it is just a stack file bound to
> the
> > engine and the other way(s) not listed here?  I'm genuinely interested.
> >
> > Sean
> >
> >
> >> On Thu, 8 Apr 2021 at 17:43, Richard Gaskin via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >> Standalone building needs to be moved to a separate process.
> >>
> >> Handling it within the IDE process was fine as long as the only thing
> >> the Standalone Builder did was bind a copy of the engine to a copy of
> >> the stack file.
> >>
> >> But today, building a standalone means deep modifications to the stack
> >> file, and this has resulted in multiple successive layers of knock-on
> >> effects where design complications are needed to compensate for design
> >> complications put in place to compensate for earlier design
> complications.
> >>
> >> The end result of attempting to build standalones within the current IDE
> >> process is not merely cumbersome, but disruptive, confusing, and even
> >> requires CODE CHANGES from EVERY USER to compensate even further just
> >> for the build sequence.
> >>
> >> LC has gone from the simplest way to build apps to something no less
> >> onerous than most, and more confusing than many.
> >>
> >> Standalone building needs to be moved to a separate process.
> >>
> >> With that, LC can begin the return journey back on its path to the
> >> simplest way to build apps.
> >>
> >> --
> >>  Richard Gaskin
> >>  Fourth World Systems
> >>
> >>
> >>
> >> Ralph DiMola wrote:
> >>
> >>> I never built a non-mobile standalone for the first 5 years of using
> >>> LC. For a mobile build nothing gets closed and gets built from the
> >>> stack(s) files on disk. What a surprise I got when I built my first
> >>> desktop standalone. I initially thought that something was very wrong
> >>> with the IDE and restarted.
> >>> After some searches I found that this is the correct behavior??? I
> >>> guess there is a reason for closing the stack(s) but I find it very
> >>> odd indeed.
> >>>
> >>> Ralph DiMola
> >>
> >>
> >> ___
> >> 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: Help! I'm stuck

[Brian Milby via use-livecode]

It would be a separate application, but would still be called from the IDE like 
today.  One difference is that as a separate process it would not disrupt the 
current session inside the IDE.

Sent from my iPhone

> On Apr 8, 2021, at 1:21 PM, Sean Cole (Pi) via use-livecode 
>  wrote:
> 
> Hi Richard,
> 
> When you say a separate process, do you mean have the standalone builder as
> a separate application from the IDE? Why could it not be accomplished in
> the IDE where it is more convenient?
> 
> Handling it within the IDE process was fine as long as the only thing
>> the Standalone Builder did was bind a copy of the engine to a copy of
>> the stack file.
>> 
> 
> Forgive my lack of knowledge, but when we compile it to an application for
> different platforms, what are the differences from one platform build to
> another, particularly regarding where it is just a stack file bound to the
> engine and the other way(s) not listed here?  I'm genuinely interested.
> 
> Sean
> 
> 
>> On Thu, 8 Apr 2021 at 17:43, Richard Gaskin via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> Standalone building needs to be moved to a separate process.
>> 
>> Handling it within the IDE process was fine as long as the only thing
>> the Standalone Builder did was bind a copy of the engine to a copy of
>> the stack file.
>> 
>> But today, building a standalone means deep modifications to the stack
>> file, and this has resulted in multiple successive layers of knock-on
>> effects where design complications are needed to compensate for design
>> complications put in place to compensate for earlier design complications.
>> 
>> The end result of attempting to build standalones within the current IDE
>> process is not merely cumbersome, but disruptive, confusing, and even
>> requires CODE CHANGES from EVERY USER to compensate even further just
>> for the build sequence.
>> 
>> LC has gone from the simplest way to build apps to something no less
>> onerous than most, and more confusing than many.
>> 
>> Standalone building needs to be moved to a separate process.
>> 
>> With that, LC can begin the return journey back on its path to the
>> simplest way to build apps.
>> 
>> --
>>  Richard Gaskin
>>  Fourth World Systems
>> 
>> 
>> 
>> Ralph DiMola wrote:
>> 
>>> I never built a non-mobile standalone for the first 5 years of using
>>> LC. For a mobile build nothing gets closed and gets built from the
>>> stack(s) files on disk. What a surprise I got when I built my first
>>> desktop standalone. I initially thought that something was very wrong
>>> with the IDE and restarted.
>>> After some searches I found that this is the correct behavior??? I
>>> guess there is a reason for closing the stack(s) but I find it very
>>> odd indeed.
>>> 
>>> Ralph DiMola
>> 
>> 
>> ___
>> 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: Help! I'm stuck

[Sean Cole (Pi) via use-livecode]

Hi Richard,

When you say a separate process, do you mean have the standalone builder as
a separate application from the IDE? Why could it not be accomplished in
the IDE where it is more convenient?

Handling it within the IDE process was fine as long as the only thing
> the Standalone Builder did was bind a copy of the engine to a copy of
> the stack file.
>

Forgive my lack of knowledge, but when we compile it to an application for
different platforms, what are the differences from one platform build to
another, particularly regarding where it is just a stack file bound to the
engine and the other way(s) not listed here?  I'm genuinely interested.

Sean


On Thu, 8 Apr 2021 at 17:43, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Standalone building needs to be moved to a separate process.
>
> Handling it within the IDE process was fine as long as the only thing
> the Standalone Builder did was bind a copy of the engine to a copy of
> the stack file.
>
> But today, building a standalone means deep modifications to the stack
> file, and this has resulted in multiple successive layers of knock-on
> effects where design complications are needed to compensate for design
> complications put in place to compensate for earlier design complications.
>
> The end result of attempting to build standalones within the current IDE
> process is not merely cumbersome, but disruptive, confusing, and even
> requires CODE CHANGES from EVERY USER to compensate even further just
> for the build sequence.
>
> LC has gone from the simplest way to build apps to something no less
> onerous than most, and more confusing than many.
>
> Standalone building needs to be moved to a separate process.
>
> With that, LC can begin the return journey back on its path to the
> simplest way to build apps.
>
> --
>   Richard Gaskin
>   Fourth World Systems
>
>
>
> Ralph DiMola wrote:
>
>  > I never built a non-mobile standalone for the first 5 years of using
>  > LC. For a mobile build nothing gets closed and gets built from the
>  > stack(s) files on disk. What a surprise I got when I built my first
>  > desktop standalone. I initially thought that something was very wrong
>  > with the IDE and restarted.
>  > After some searches I found that this is the correct behavior??? I
>  > guess there is a reason for closing the stack(s) but I find it very
>  > odd indeed.
>  >
>  > Ralph DiMola
>
>
> ___
> 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: Help! I'm stuck

[Richard Gaskin via use-livecode]

Standalone building needs to be moved to a separate process.

Handling it within the IDE process was fine as long as the only thing 
the Standalone Builder did was bind a copy of the engine to a copy of 
the stack file.


But today, building a standalone means deep modifications to the stack 
file, and this has resulted in multiple successive layers of knock-on 
effects where design complications are needed to compensate for design 
complications put in place to compensate for earlier design complications.


The end result of attempting to build standalones within the current IDE 
process is not merely cumbersome, but disruptive, confusing, and even 
requires CODE CHANGES from EVERY USER to compensate even further just 
for the build sequence.


LC has gone from the simplest way to build apps to something no less 
onerous than most, and more confusing than many.


Standalone building needs to be moved to a separate process.

With that, LC can begin the return journey back on its path to the 
simplest way to build apps.


--
 Richard Gaskin
 Fourth World Systems



Ralph DiMola wrote:

> I never built a non-mobile standalone for the first 5 years of using
> LC. For a mobile build nothing gets closed and gets built from the
> stack(s) files on disk. What a surprise I got when I built my first
> desktop standalone. I initially thought that something was very wrong
> with the IDE and restarted.
> After some searches I found that this is the correct behavior??? I
> guess there is a reason for closing the stack(s) but I find it very
> odd indeed.
>
> Ralph DiMola


___
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: Help! I'm stuck

[Sean Cole (Pi) via use-livecode]

On Wed, 7 Apr 2021 at 19:27, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> A good compromise would be providing a checkbox in standalone settings
> where we can decide
> whether we want to preserve local variables or not. If we don't care, the
> SB should go ahead
> and lock messages. The default setting should be to lock messages as it
> always has.


This sounds more like a fix than a compromise. Seems like the perfect
solution. No workaround and can be easily spotted when setting up your
standalone. Excellent idea.

Sean
___
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: Help! I'm stuck

[Bob Sneidar via use-livecode]

+1

> On Apr 7, 2021, at 11:27 , J. Landman Gay via use-livecode 
>  wrote:
> 
> On 4/7/21 12:03 PM, Curry Kenworthy via use-livecode wrote:
>> The problems introduced were far more numerous than those "fixed."
> 
> A good compromise would be providing a checkbox in standalone settings where 
> we can decide whether we want to preserve local variables or not. If we don't 
> care, the SB should go ahead and lock messages. The default setting should be 
> to lock messages as it always has.
> 
> -- 
> 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

Re: Help! I'm stuck

[J. Landman Gay via use-livecode]

On 4/7/21 12:03 PM, Curry Kenworthy via use-livecode wrote:

The problems introduced were far more numerous than those "fixed."


A good compromise would be providing a checkbox in standalone settings where we can decide 
whether we want to preserve local variables or not. If we don't care, the SB should go ahead 
and lock messages. The default setting should be to lock messages as it always has.


--
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

Re: Help! I'm stuck

[William Prothero via use-livecode]

Ralph and Curry:
Fortunately, I took a break for a week before trying your solutions. For 
someone who doesn’t do this every day, it is a confusing mess and I suppose 
that somewhere there is an explanation in the help files of what to do, but my 
cursory searches didn’t find anything for such a complicated project I was 
trying to build. Thank heavens for this list!

I also agree that it would be a really good thing if the IDE, or the mothership 
provided more help for the ever-changing security requirements for Apple mobile 
and desktop builds.

Best,
Bill Prothero

> On Apr 7, 2021, at 10:20 AM, Ralph DiMola via use-livecode 
>  wrote:
> 
> I never built a non-mobile standalone for the first 5 years of using LC. For
> a mobile build nothing gets closed and gets built from the stack(s) files on
> disk. What a surprise I got when I built my first desktop standalone. I
> initially thought that something was very wrong with the IDE and restarted.
> After some searches I found that this is the correct behavior??? I guess
> there is a reason for closing the stack(s) but I find it very odd indeed.
> 
> 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 Curry Kenworthy via use-livecode
> Sent: Wednesday, April 07, 2021 1:03 PM
> To: use-livecode@lists.runrev.com
> Cc: Curry Kenworthy
> Subject: Re: Help! I'm stuck
> 
> 
> Jacqueline:
> 
>> It's not a bug, it was intentionally introduced to allow a couple  > of
> features, like retaining script local variables after a build.
>> Given the amount of extra scripting to work around it for existing  >
> stacks, I think it may have introduced more problems than it tried  > to
> cure.
> 
> Agreed! I was too busy the other day but wanted to chime in:
> This was a baffling case of doubling-down on a wonky and toxic "fix."
> 
> The problems introduced were far more numerous than those "fixed."
> I pointed this out right away, but it seems that hubris prevailed.
> LC Ltd needs a more consistent vision of what LC is and how it works.
> 
> Result: workarounds are often needed for standard builds.
> In what RAD paradigm should users have to workaround the IDE?
> If that's a question we're even needing to ask, we may be in trouble.
> 
> (My own stack design usually makes this a moot point. I wasn't affected.
> But I saw the expense and pain this caused, plus a troubling precedent.)
> 
> So ... isn't it great they teach everyone to double down these days?  :)
> Turning off messages - good tactic, although it won't work for everyone.
> 
> Back to work, take care all
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Custom Software Development
> "Better Methods, Better Results"
> LiveCode Training and Consulting
> http://livecodeconsulting.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

RE: Help! I'm stuck

[Ralph DiMola via use-livecode]

I never built a non-mobile standalone for the first 5 years of using LC. For
a mobile build nothing gets closed and gets built from the stack(s) files on
disk. What a surprise I got when I built my first desktop standalone. I
initially thought that something was very wrong with the IDE and restarted.
After some searches I found that this is the correct behavior??? I guess
there is a reason for closing the stack(s) but I find it very odd indeed.

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 Curry Kenworthy via use-livecode
Sent: Wednesday, April 07, 2021 1:03 PM
To: use-livecode@lists.runrev.com
Cc: Curry Kenworthy
Subject: Re: Help! I'm stuck


Jacqueline:

 > It's not a bug, it was intentionally introduced to allow a couple  > of
features, like retaining script local variables after a build.
 > Given the amount of extra scripting to work around it for existing  >
stacks, I think it may have introduced more problems than it tried  > to
cure.

Agreed! I was too busy the other day but wanted to chime in:
This was a baffling case of doubling-down on a wonky and toxic "fix."

The problems introduced were far more numerous than those "fixed."
I pointed this out right away, but it seems that hubris prevailed.
LC Ltd needs a more consistent vision of what LC is and how it works.

Result: workarounds are often needed for standard builds.
In what RAD paradigm should users have to workaround the IDE?
If that's a question we're even needing to ask, we may be in trouble.

(My own stack design usually makes this a moot point. I wasn't affected.
But I saw the expense and pain this caused, plus a troubling precedent.)

So ... isn't it great they teach everyone to double down these days?  :)
Turning off messages - good tactic, although it won't work for everyone.

Back to work, take care all

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.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

Re: Help! I'm stuck

[Curry Kenworthy via use-livecode]

Jacqueline:

> It's not a bug, it was intentionally introduced to allow a couple
> of features, like retaining script local variables after a build.
> Given the amount of extra scripting to work around it for existing
> stacks, I think it may have introduced more problems than it tried
> to cure.

Agreed! I was too busy the other day but wanted to chime in:
This was a baffling case of doubling-down on a wonky and toxic "fix."

The problems introduced were far more numerous than those "fixed."
I pointed this out right away, but it seems that hubris prevailed.
LC Ltd needs a more consistent vision of what LC is and how it works.

Result: workarounds are often needed for standard builds.
In what RAD paradigm should users have to workaround the IDE?
If that's a question we're even needing to ask, we may be in trouble.

(My own stack design usually makes this a moot point. I wasn't affected.
But I saw the expense and pain this caused, plus a troubling precedent.)

So ... isn't it great they teach everyone to double down these days?  :)
Turning off messages - good tactic, although it won't work for everyone.

Back to work, take care all

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.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: Help! I'm stuck

[William Prothero via use-livecode]

Hot Dang! It built the App. 
Sean and Jacqueline, you made my day!
Thanks!
Bill

> On Apr 4, 2021, at 6:08 AM, Sean Cole (Pi) via use-livecode 
>  wrote:
> 
> 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)  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
>>> 
>>> page 2: 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
>> 
>>> 

Re: Help! I'm stuck

[William Prothero via use-livecode]

Thanks so much, Sean and Jacqueline!
I’ll try that.
Bill

> On Apr 4, 2021, at 9:04 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> It's not a bug, it was intentionally introduced to allow a couple of 
> features, like retaining script local variables after a build. Given the 
> amount of extra scripting to work around it for existing stacks, I think it 
> may have introduced more problems than it tried to cure.
> 
> I did try turning off messages before a build but it didn't work.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On April 3, 2021 7:13:25 PM William Prothero via use-livecode 
>  wrote:
> 
>> 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).???
> 
> 
> 
> 
> ___
> 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

Re: Help! I'm stuck

[J. Landman Gay via use-livecode]

It's not a bug, it was intentionally introduced to allow a couple of 
features, like retaining script local variables after a build. Given the 
amount of extra scripting to work around it for existing stacks, I think it 
may have introduced more problems than it tried to cure.


I did try turning off messages before a build but it didn't work.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On April 3, 2021 7:13:25 PM William Prothero via use-livecode 
 wrote:


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).???





___
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: Help! I'm stuck

[Sean Cole (Pi) via use-livecode]

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)  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
>> 
>> page 2: 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>:
>> 

Re: Help! I'm stuck

[Sean Cole (Pi) via use-livecode]

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
> 
> 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
> >>

Re: Help! I'm stuck

[William Prothero via use-livecode]

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 

page 2: 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 
>  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 
>> :
>> 
>> 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 
>>>  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 
 :
 
 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 

Re: Help! I'm stuck

[ELS Prothero via use-livecode]

Thank you, Matthias! I’ll try that.
Best,
Bill

William Prothero
https://earthlearningsolutions.org

> On Mar 20, 2021, at 1:39 PM, matthias rebbe via use-livecode 
>  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 
>> :
>> 
>> 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 
  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 
 :
 
 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


___
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: Help! I'm stuck

[matthias rebbe via use-livecode]

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 
> :
> 
> 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 
>>  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 
>>> :
>>> 
>>> 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

Re: Help! I'm stuck

[William Prothero via use-livecode]

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 
>  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 
>> :
>> 
>> 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

Re: Help! I'm stuck

[ELS Prothero via use-livecode]

Thanks, Matthias,
I’ll try it. Time for dinner, tho so it will be a bit.
Bill

William Prothero
https://earthlearningsolutions.org

> On Mar 19, 2021, at 5:47 PM, matthias rebbe via use-livecode 
>  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 
>> :
>> 
>> 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


___
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: Help! I'm stuck

[matthias rebbe via use-livecode]

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 
> :
> 
> 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

Re: Help! I'm stuck

[ELS Prothero via use-livecode]

Matthias,
I know, I don’t think I’m using the remote debugger. I’m building a standalone 
app for the computer I’m developing on, so I wouldn’t need the remote debugger. 
I have some code that is never called...I wonder if that could cause problems. 
Of course, that is the situation for libs, so I wouldn’t think that was a 
problem. I cleared all breakpoints using the development menu of the IDE, for 
all the stacks. It’s mystifying that all messages seem to come from the rev 
builder scripts, with no hint of what could be the problem.

Bill

William Prothero
https://earthlearningsolutions.org

> On Mar 19, 2021, at 5:03 PM, matthias rebbe via use-livecode 
>  wrote:
> 
> Hi Bill,
> 
> i am not an expert for that kind of error message. Too much numbers i do not 
> know what they mean. 
> The text in the error message mentions several time revdebugger.
> 
> Are you including the RemoteDebugger to your standalone or do you have red 
> breakpoints somewhere in the script which might cause this?
> 
> Sometimes it helps to close Livecode, reopen it and try to build the 
> standalone again. 
> But i am sure you did that already.
> 
> Regards,
> Matthias
> -
> Matthias Rebbe
> Life Is Too Short For Boring Code
> 
>> Am 20.03.2021 um 00:03 schrieb prothero--- via use-livecode 
>> :
>> 
>> Folks:
>> I have a pretty complicated application, with numerous stacks and lib 
>> stacks. I’m trying to build a stand-alone but after making a bunch of 
>> progress dealing with obvious errors, the standalone builder gives me an 
>> error listing that I can’t figure out where to go from here. All of the 
>> stacks and text only stacks are in the “Stacks” list. The app runs fine in 
>> the IDE.
>> 
>> I’d really appreciate it if someone would look at this error list and give 
>> me some hints about where I should go from here to get an app built. There 
>> are no reverences to stacks that I created in the error list, only to rev 
>> code.
>> 
>> I’m on Big Sur, Macintosh, LC 9.6.2 (RC-3), Business Version
>> 
>> Link to page 1: 
>> https://www.dropbox.com/s/h1q7d3emqq8ygis/Errors-Page-1.pdf?dl=0 
>> 
>> Link to page 2: 
>> https://www.dropbox.com/s/zc18s3gkzv92w2w/Errors-page-2.pdf?dl=0 
>> 
>> 
>> Thanks for any insight!
>> Bill
>> 
>> William A. Prothero, Ph.D.
>> University of California, Santa Barbara Dept. of Earth Sciences (Emeritus)
>> Santa Barbara, CA. 93105
>> http://earthlearningsolutions.org/
>> 
>> ___
>> 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: Help! I'm stuck

[matthias rebbe via use-livecode]

Hi Bill,

i am not an expert for that kind of error message. Too much numbers i do not 
know what they mean. 
The text in the error message mentions several time revdebugger.

Are you including the RemoteDebugger to your standalone or do you have red 
breakpoints somewhere in the script which might cause this?

Sometimes it helps to close Livecode, reopen it and try to build the standalone 
again. 
But i am sure you did that already.

Regards,
Matthias
-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 20.03.2021 um 00:03 schrieb prothero--- via use-livecode 
> :
> 
> Folks:
> I have a pretty complicated application, with numerous stacks and lib stacks. 
> I’m trying to build a stand-alone but after making a bunch of progress 
> dealing with obvious errors, the standalone builder gives me an error listing 
> that I can’t figure out where to go from here. All of the stacks and text 
> only stacks are in the “Stacks” list. The app runs fine in the IDE.
> 
> I’d really appreciate it if someone would look at this error list and give me 
> some hints about where I should go from here to get an app built. There are 
> no reverences to stacks that I created in the error list, only to rev code.
> 
> I’m on Big Sur, Macintosh, LC 9.6.2 (RC-3), Business Version
> 
> Link to page 1: 
> https://www.dropbox.com/s/h1q7d3emqq8ygis/Errors-Page-1.pdf?dl=0 
> 
> Link to page 2: 
> https://www.dropbox.com/s/zc18s3gkzv92w2w/Errors-page-2.pdf?dl=0 
> 
> 
> Thanks for any insight!
> Bill
> 
> William A. Prothero, Ph.D.
> University of California, Santa Barbara Dept. of Earth Sciences (Emeritus)
> Santa Barbara, CA. 93105
> http://earthlearningsolutions.org/
> 
> ___
> 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: Help! I'm stuck

[ELS Prothero via use-livecode]

Thanks, Bob,
I tried it and got the same error message.
Tnx,
Bill

William Prothero
https://earthlearningsolutions.org

> On Mar 19, 2021, at 4:10 PM, Bob Sneidar via use-livecode 
>  wrote:
> 
> Do you have a copy of 9.6.0? Try compiling with that. 
> 
> Bob S
> 
> 
>> On Mar 19, 2021, at 4:03 PM, prothero--- via use-livecode 
>>  wrote:
>> 
>> Folks:
>> I have a pretty complicated application, with numerous stacks and lib 
>> stacks. I’m trying to build a stand-alone but after making a bunch of 
>> progress dealing with obvious errors, the standalone builder gives me an 
>> error listing that I can’t figure out where to go from here. All of the 
>> stacks and text only stacks are in the “Stacks” list. The app runs fine in 
>> the IDE.
>> 
>> I’d really appreciate it if someone would look at this error list and give 
>> me some hints about where I should go from here to get an app built. There 
>> are no reverences to stacks that I created in the error list, only to rev 
>> code.
>> 
>> I’m on Big Sur, Macintosh, LC 9.6.2 (RC-3), Business Version
>> 
>> Link to page 1: 
>> https://www.dropbox.com/s/h1q7d3emqq8ygis/Errors-Page-1.pdf?dl=0 
>> 
>> Link to page 2: 
>> https://www.dropbox.com/s/zc18s3gkzv92w2w/Errors-page-2.pdf?dl=0 
>> 
>> 
>> Thanks for any insight!
>> Bill
>> 
>> William A. Prothero, Ph.D.
>> University of California, Santa Barbara Dept. of Earth Sciences (Emeritus)
>> Santa Barbara, CA. 93105
>> http://earthlearningsolutions.org/
>> 
>> ___
>> 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: Help! I'm stuck

[Bob Sneidar via use-livecode]

Do you have a copy of 9.6.0? Try compiling with that. 

Bob S


> On Mar 19, 2021, at 4:03 PM, prothero--- via use-livecode 
>  wrote:
> 
> Folks:
> I have a pretty complicated application, with numerous stacks and lib stacks. 
> I’m trying to build a stand-alone but after making a bunch of progress 
> dealing with obvious errors, the standalone builder gives me an error listing 
> that I can’t figure out where to go from here. All of the stacks and text 
> only stacks are in the “Stacks” list. The app runs fine in the IDE.
> 
> I’d really appreciate it if someone would look at this error list and give me 
> some hints about where I should go from here to get an app built. There are 
> no reverences to stacks that I created in the error list, only to rev code.
> 
> I’m on Big Sur, Macintosh, LC 9.6.2 (RC-3), Business Version
> 
> Link to page 1: 
> https://www.dropbox.com/s/h1q7d3emqq8ygis/Errors-Page-1.pdf?dl=0 
> 
> Link to page 2: 
> https://www.dropbox.com/s/zc18s3gkzv92w2w/Errors-page-2.pdf?dl=0 
> 
> 
> Thanks for any insight!
> Bill
> 
> William A. Prothero, Ph.D.
> University of California, Santa Barbara Dept. of Earth Sciences (Emeritus)
> Santa Barbara, CA. 93105
> http://earthlearningsolutions.org/
> 
> ___
> 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