on 7-01-2007 21:46, Massimo Valle at [EMAIL PROTECTED] wrote: > > On 07/gen/07, at 21:12, Tobias Bußmann wrote: > >> Hi, >> >> Massimo Valle schrieb: >> >>> As a complement to the above, I noticed that the >>> RuntimeException.stack works even if the "Include function names" >>> flag is not enabled. >>> I tried to build an UB target (RB 2006r4) with and without >>> function names and the binary size is exactly the same. >>> Is this a bug? >> >> Maybe this one? >> http://www.realsoftware.com/feedback/viewreport.php?reportid=eedjprwd >> > > Playing with exception, I just find a bug of 2007r1 > > An exception raised in a Window.Open event and catched by > App.UnhandledException, always cause the application to quit, > regardless of the return value of App.UnhandledException > http://www.realsoftware.com/feedback/viewreport.php?reportid=mdeumldc > > The above bug doesn't apply to 2006r4, since for this version the > App.UnhandledException doesn't fire at all. >
aha! so maybe some variant of this is causing my app freeze on launch, but only on MacIntels I fixed this eliminating the Exception handlers in a prefs reading method (you know which one Massimo ;-) but couldn't reproduce it on demo project (don't have a MacIntel myself to test so I had to ask some kind fellow to do me a favor - hi Joe!) So maybe key to reproduce is to invoke the exceptions while in the app.Open event... Cool Runnings, Erne. -- / |\ |\ | / |/ | \ | \ |\ | \| \ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
