Standalone build workaround

[J. Landman Gay]

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 several dismissals to get rid of them. I don't know 
what handlers are in the separate mainstack but he said he fixed "all of 
them" that had open* and close* handlers. This was before we had a check 
to see if the revStandaloneProgress stack existed.

Also during builds, a blank script error dialog appeared. It was 
unresponsive and empty so we don't know what it was trying to report. A 
stream of other error messages popped in and out of existence so fast we 
couldn't read them, so they weren't modal but their content is unknown.

All this happened in LC 9 so I had him move back to LC 8. I told him to 
remove the content stack from memory and from inclusions and try 
building only the splash app, and that worked, so the problem points to 
the content stack. When he added it back into the Stacks pane in 
Standalone Settings the "can't find stack" error happened because the 
incorrect workaround handler was still in place. I've sent him the 
updated handler Panos posted and haven't heard back yet, but that should 
fix it.

The release notes need updating so we have a record of the correct 
workaround.

Like I said, it isn't the adaptation we need to do that bothers me as 
much as the idea that a lot of people won't know what's happening and 
will blame LC. That's what this person did. He had a bit of a rant about 
how LC didn't test enough and are producing shoddy software. I spent 
some time explaining what the real issue was and he then understood. But 
I'm concerned about other customers out there.

On 9/20/18 6:40 AM, Ali Lloyd via use-livecode wrote:
> 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? Something like a ‘cascade of errors’ sounds like the latter.


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com