Re: Standalone build workaround

2018-09-20 Thread J. Landman Gay via use-livecode
Maybe it's a little of both. I was helping out over screen sharing and only saw the openstack handler. The app uses a splash-screen model and we did get the conflict Bob described, where the stack the app opens threw a large number of repeated warnings about same-named stack conflicts. It took

Re: When is suspendStack sent?

2018-09-20 Thread Bob Sneidar via use-livecode
Yes it's in the stack script. It works the first time, and subsequent times it does not fire, even when I click back on the stack and away from it again. I think the stack I clicked on to go away from it is somehow getting the suspendStack message instead of the stack that is *actually*

Re: App Dead on iOS 12

2018-09-20 Thread Terry Judd via use-livecode
> On 21 Sep 2018, at 11:48 am, Terry Judd via use-livecode wrote: > > Panos did some sleuthing of my console output and it appears that my iOS 12 crashes (which occurred with even the most very basic of stacks/apps) are related to the fact that I use an iOS enterprise developer

Re: Standalone build workaround

2018-09-20 Thread Monte Goulding via use-livecode
> On 20 Sep 2018, at 2:51 pm, Brian Milby via use-livecode > wrote: > > What about a front script for the build process that would intercept and > discard these messages? Could be inserted just before each action that used > to be protected by lock messages (close/open stack). I think if

Re: App Dead on iOS 12

2018-09-20 Thread Curry Kenworthy via use-livecode
Monte: > We have not been able to replicate the crash so it’s pretty > important that we get a report with a recipe ASAP. It's been a day or two. Has anyone reported/recipe'd this yet? If not I will. I suspect that a test stack needs more than one card to trigger the bug. Best wishes,

Re: App Dead on iOS 12

2018-09-20 Thread Monte Goulding via use-livecode
> On 21 Sep 2018, at 11:20 am, Curry Kenworthy via use-livecode > wrote: > > > We have not been able to replicate the crash so it’s pretty > > important that we get a report with a recipe ASAP. > > It's been a day or two. Has anyone reported/recipe'd this yet? If not I will. > > I suspect

Re: App Dead on iOS 12

2018-09-20 Thread Monte Goulding via use-livecode
> On 21 Sep 2018, at 11:48 am, Terry Judd via use-livecode > wrote: > > Panos did some sleuthing of my console output and it appears that my iOS 12 > crashes (which occurred with even the most very basic of stacks/apps) are > related to the fact that I use an iOS enterprise developer

Re: When is suspendStack sent?

2018-09-20 Thread Brian Milby via use-livecode
I just set up a couple stacks and it worked every time. Then I switched to another application and then the messages stopped. I will need to go back and see if I can reduce to a recipe. The dictionary says the message is sent to the card, so the stack should see it. Thanks, Brian On Sep 20,

Re: App Dead on iOS 12

2018-09-20 Thread Terry Judd via use-livecode
Panos did some sleuthing of my console output and it appears that my iOS 12 crashes (which occurred with even the most very basic of stacks/apps) are related to the fact that I use an iOS enterprise developer license to sign/distribute my apps - so not a LC issue as such. Will just have to wait

Re: When is suspendStack sent?

2018-09-20 Thread dunbarxx via use-livecode
Hmmm. Not sure of your setup, of course, but if I try an experiment, it always works. Can you check the topStack each time you return to the, er, topStack? You may indeed need to place that handler in a backScript or stack in use in order to do so. Craig -- Sent from:

Re: Standalone build workaround

2018-09-20 Thread Ali Lloyd via use-livecode
Just out of interest, what sorts of things are causing problems in openStack while building a standalone that do not happen when opening stacks for the first time in the IDE? To put it another way, is it simply the re-running of openStack that is causing problems, or is something going wrong?

Re: Standalone build workaround

2018-09-20 Thread Bob Sneidar via use-livecode
When I build a standalone, I use a splash stack, which when run in a standalone opens the mainStack. I do not typically have the mainstack already open, because as has been mentioned multiple times, any stacks already open after a build, say when building for a separate platform (I still cannot

Re: SVG to image

2018-09-20 Thread Brian Milby via use-livecode
I just did a little bit of comparison of the path before and after your widget translated it. The path data is quite a bit different (besides just going to 6 decimal places). Something about how the path is adjusted makes it work better with the path compiler, but it does increase the compiled

Re: Standalone build workaround

2018-09-20 Thread Brian Milby via use-livecode
And the engine itself can support multiple stacks open with the same name. If you do though, you have to use the long name to be sure you access the correct one and the IDE isn't built to always do that. (I've created a demo that validates that the engine can handle this. The engine does prevent

When is suspendStack sent?

2018-09-20 Thread Bob Sneidar via use-livecode
Hi all. I was using modal as a means to prevent a user from switching to another open window while in certain modes (editing a "form" for example). That is fraught with peril for a number of reasons I will not go into here. So alternatively I thought to put a suspendStack handler in the

Re: When is suspendStack sent?

2018-09-20 Thread Bob Sneidar via use-livecode
I'm still curious why suspendStack is not getting sent to what appears for all intents and purposes to be the topStack (I even click the titlebar to make sure), but I found a workaround which is a bit more elegant. If I have a substack open, say for editing the details of a site record, and I

Re: When is suspendStack sent?

2018-09-20 Thread dunbarxx via use-livecode
Bob. Is the suspendStack handler in the stack script of some stack? If so, it will only fire when leaving that stack. You can always place the handler in a backScript, or something similar, so that all stacks will have to listen to it. Craig -- Sent from: