Well I for one am not getting a good snapshot of your form handling in general. You may have a systematic problem going on from an unlikely source. Unless this app is just these two (or 3) forms?
re: the resource problem. I've never heard of these kind of problems and have never seen them on my apps (running on everything but Vista). Are you doing something unusual with resource handling? Dave Jeremy Grand <[EMAIL PROTECTED]> wrote: Dave, I know what you mean. But as a practical matter, there is just far too much code in the viewer to expect anyone to wade through. I'm hoping for ideas on where to look, really. I have eurekalog implemented, so I can see the call stack when the problem happens, but there is nothing unusual there. I've verified that the viewDetail form does not refer to the search form. It is not Used, so, how could anything that happens in viewDetail affect search? The problem happens sometime before self.show, and by inference after self.hide. They ain't nothin else between, cept viewDetail. I'm thinking external forces. I have another issue that comes and goes, which very likely is external: the app issues an out of resources message and claims the window doesn't have scroll bars. This gives credence to environmental issues, but no clue on how to diagnose. Jeremy --------------------------------- From: advanced_delphi@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of David Smith Sent: Wednesday, December 05, 2007 10:52 AM To: advanced_delphi@yahoogroups.com Subject: Re: [advanced_delphi] Mysterious vanishing form There appears to be nothing wrong with the code you have shown so how about showing the rest of it so someone can make a stab at debugging it for you? Dave Jeremy Grand <[EMAIL PROTECTED]> wrote: My app sometimes tries to show a hidden form that is no longer in existence, but I can't think of a reason for it to no longer exist. Here's the scenario: There is a search form, and a detail form, both Created and in existence always, but only one is visible at a given moment. In the search screen a click handler does this: myobj.loaddata; self.hide; viewDetail(myobj); // does a ShowModal on the detail form. Detail form closes itself, but does not free. self.show; //access violation here --sometimes, not always--. This works fine almost all the time. Obviously, some users (or the OS) are doing something I'm not expecting, but what? The detail form is modal, and the search form is not visible, so how can it be freed? Or maybe more precisely, how can Self not point to something Show-able? I must have a blind spot here. Any suggestions? Jeremy --------------------------------- Never miss a thing. Make Yahoo your homepage. --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search.
