Update problems switching from LC 5 to 6.6.5

[Marty Knapp]

I recently updated one of my apps from LC 5.05 to 6.6.5. And I've since
made a second update built with 6.6.5. If you update from a version
built with LC 5.05 it updates fine. But once you have an app with the
6.6.5 engine and try to update, it stops when the download is complete.
The update window says it's "Installing update." But it doesn't quit and
restart like it should. You can manually cancel and the app loads but
the previous version of the "program" stack seems to be loaded rather
than the updated version as any new code is not available (though the
version number indicates the updated version number). If you then quit
the app and restart it's fine - the update seems complete.

I've gone back and commented out code that is new to the 6.6.5 version
but so far no luck in tracking this down.

I checked the libURL version and it is: v1.2.0 2010-09-16 Is that the
most current?

Has anyone had any issue like this?

--
Best regards,
Marty K

[MartyK]

Well I finally tracked it down to the _relaunchapplication handler. When it got to "quit" it was not quitting. I inserted "lock messages" in the line before and now it works. But why would that be? I didn't think you could trap for quit, but I looked to see if I was somewhere but found nothing. I didn't try a wait before quit, maybe that would be better? Any thoughts???

[Trevor DeVore]

On Sat, Jan 31, 2015 at 5:06 PM, MartyK <marty...@comcast.net> wrote:

Well I finally tracked it down to the _relaunchapplication handler. When it got to "quit" it was not quitting. I inserted "lock messages" in the line before and now it works. But why would that be? I didn't think you could trap for quit, but I looked to see if I was somewhere but found nothing. I didn't try a wait before quit, maybe that would be better? Any thoughts???

Hmm, that is a strange one. I haven't really used 6.6 at all, I went right to 6.7. I wonder if there is some kind of bug in 6.6?

-- 

Trevor DeVore

ScreenSteps

www.screensteps.com    -    www.clarify-it.com 

[Marty Knapp]

To make it even more strange, I have another app, built with LC 6.6.5 and the updater works fine without having to lock messages before the quit. Could there be pending messages - would that interrupt a quit?

Marty K

--

[Trevor DeVore]

On Tue, Feb 3, 2015 at 3:03 PM, Marty Knapp <martykn...@gmail.com> wrote:

To make it even more strange, I have another app, built with LC 6.6.5 and the updater works fine without having to lock messages before the quit. Could there be pending messages - would that interrupt a quit?

I'm not sure. The framework tries to go through and cancel any pending messages and close any open sockets when it is quit time, so I wouldn't think that it would be a problem.