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
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
> d
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 Ric
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
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
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
+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
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
; 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.
-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
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
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 ru
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
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 o
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 Ap
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
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 pr
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
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 pointin
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, script
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, bu
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
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
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
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
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 progres
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 stac
27 matches
Mail list logo
