AW: Untitled... has a problem
Tiemo Hollmann TB
toolbook at kestner.de
Thu Nov 13 10:27:17 CST 2008
Thanks Eric and Mark,
I don't have any send in time, but Marks approach of closing did it :) The
main difference seems to be that I didn't used quit for the standalone.
Could it be that? But why, if the error only happened when having had open a
special stack and not all the time?
And as I see in Marks script, you don't use the destroystack. Probably
because the memory is freed completely, when closing the app and I have to
use destroystack only to free memory, while my app is running - right?
> -----Ursprüngliche Nachricht-----
> Von: use-revolution-bounces at lists.runrev.com [mailto:use-revolution-
> bounces at lists.runrev.com] Im Auftrag von Mark Schonewille
> Gesendet: Donnerstag, 13. November 2008 16:45
> An: How to use Revolution
> Betreff: Re: Untitled... has a problem
> Hi Tiemo,
> You can copy this script and delete the parts that you don't need
> (e.g. the MySQL part, if you don't include the MySQL drivers in the
> Best regards,
> Mark Schonewille
> Economy-x-Talk Consulting and Software Engineering
> Dutch forum: http://runrev.info/rrforum
> Color Converter has been updated! Get it at
> http://colorconverter.economy-x-talk.com !
> On 13 nov 2008, at 16:39, Tiemo Hollmann TB wrote:
> > Hello,
> > With my Rev 3.0, developed on Win XP, Standalone tested on Win XP I am
> > running into following problem. When closing my app I get the
> > following
> > error message, AFTER my App is closed: "Untitled 220.127.116.11 for Windows
> > has
> > encountered a problem and has to be finished". In the details it
> > show that
> > my standalone exe (my startstack) throws this error. This error ONLY
> > happens, if I had a special substack opened, while testing. I can't
> > find any
> > difference in handling this substack compared to the other substacks.
> > Perhaps I am doing something not suitable in opening and closing my
> > stacks.
> > What I am doing is the following:
> > Startstack: on open card
> > --- some other stuff
> > go MainStack
> > close this stack
> > MainStack:
> > --- I open every substack only with the first access and after that
> > I do
> > only hide and show with the stacks, because of performance in opening
> > --- When closing my MainStack I set the destroywindow and the
> > destroystack
> > of all of my stacks (StartStack, MainStack and Substacks) to true
> > and close
> > one by one (just to be on the safe side, without asking if any still
> > is
> > open). This procedure seems to work fine, beside of the one special
> > substack, where I can't find any difference.
> > Is there something completely wrong in handling the open and closes
> > where
> > this error could come from, or does it perhaps has nothing to do
> > with the
> > opening and closing and I have to look at a different issue?
> > Any ideas, any hints welcome!
> > Tiemo
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode