Oh good to know Mark. In my case this for internal consumption only, but if I
do distribute an app based on the framework of utility functions and commands I
have built up over the years, I can see I will have to address that.
Bob S
On Jan 12, 2017, at 14:22 , Mark Talluto via use-livecode
ma
> On Jan 12, 2017, at 2:15 PM, Bob Sneidar via use-livecode
> wrote:
>
> Thanks for the assistance, and if any of the dev team thinks this is not how
> a standalone can work, contact me offline as you please, an I will be glad to
> assist. The standalone is too big to send via the QC uploads
Hi Jacque.
As I mentioned, I created a custom property called pIncrement. Each time I
launch the app, I increment this property by 1 then write it out to a log file.
The log file indicates that the property IS getting written to and saved. I
understand that I cannot write to an executable file,
I mean the checkbox "Move Substacks into individual stack files" is UNCHECKED
and the stacks are NOT substacks of the original stack. When I open the package
(OS X), I see that in the MacOS folder there is an executalbe file called Forms
Generator (which is what I told the splash stack the app w
On 1/12/17 12:25 PM, Bob Sneidar via use-livecode wrote:
Even though in the standalone settings I have the option to save
substacks as individual stacks unchecked, it does it anyway. It just
puts them in the app package instead of in another folder.
Did you mean "checked"? If checked, that opti
Thanks all.
What I did was put a function in the backscript script called homestack(),
which simply returns the name of what ought to be the Main Stack (but isn't
anymore in a standalone). I think anyone who wants to start saving as
standalones should be alerted to this little quirk. Even thoug
On 01/11/2017 04:30 PM, Bob Sneidar via use-livecode wrote:
I read in the dictionary:
If you place the constant statement in a handler, you can use the constant
anywhere in the handler. If you place the constant statement in a script
outside any handler, you can use the constant anywhere in th
I read in the dictionary:
If you place the constant statement in a handler, you can use the constant
anywhere in the handler. If you place the constant statement in a script
outside any handler, you can use the constant anywhere in the handlers of that
script.
Any way to declare a global cons
I was a few beers in when I wrote this. Upon thinking about this, what is
actually happening is that every stack becomes it's own mainstack in a
standalone. I think what I will do then is declare a constant with the name of
what I am calling the mainstack when I first launch it. Then I can si
On 1/10/17 10:53 PM, Bob Sneidar via use-livecode wrote:
It's been my whole understanding of the use of splash stacks that the
stack used to create a standalone is read only, and therefore cannot
be a stack you set properties of, or make any changes to. I had no
idea it became the mainstack in a
First let me say that the 8.1.2 compile time is orders of magnitude improved!
WOW what a difference. It was taking me 20 minutes to save as standalone, now
it's under a minute. AWESOME! Now on to my tests.
Okay I see what is happening. In the IDE the mainstack of a substack is the
actual stack
On 01/10/2017 08:04 PM, Monte Goulding via use-livecode wrote:
I can’t give you any solid leads here but I think the idea that custom property
sets don’t work in a standalone is a red herring. I’d start by finding the bit
of code that sets the custom property set and wrap the whole handler in
> On 11 Jan 2017, at 2:52 pm, Bob Sneidar via use-livecode
> wrote:
>
> In the IDE this works famously. In a compiled application however, the column
> updateby in every table I insert or update is empty. The only explanation I
> can come up with for this is that arrays do NOT get stored prop
I'll try to explain a bit better. I have a splash stack that serves no other
purpose than presenting the user with a window with a logo and a message that
it is loading the application. It then opens the "actual" mainstack of the
application and hides itself. This mainstack is NOT the one that g
> On 11 Jan 2017, at 2:24 pm, Bob Sneidar via use-livecode
> wrote:
>
> Ooookaaay. In the IDE I can set a property of the mainstack (not the Splash
> Stack mind you that I use to "shell" the application) to an array. When I
> retrieve that property and access a key of that array, all is well.
Ooookaaay. In the IDE I can set a property of the mainstack (not the Splash
Stack mind you that I use to "shell" the application) to an array. When I
retrieve that property and access a key of that array, all is well. HOWEVER...
when I compile to a standalone, that key is apparently inaccessible
Ooookaaay. In the IDE I can set a property of the mainstack (not the Splash
Stack mind you that I use to "shell" the application) to an array. When I
retrieve that property and access a key of that array, all is well. HOWEVER...
when I compile to a standalone, that key is apparently inaccessible
17 matches
Mail list logo
