RE: [flexcoders] Re: Uncaught exceptions in Flex 1.5
What does your mm.cfg file look like? The following settings work general trace output and error reporting: ErrorReportingEnable=1 TraceOutputFileEnable=1 The following setting works only in the debug version of Flash Player 7 (i.e. that that shipped with Flex 1.5, not the normal, non-debug player, such as Flash Player 8 from our website) and is only relevant to Flex 1.5: TraceLocationEnable=1 Also I believe this was still relevant in Flex 1.5... the flex-config.xml file and settings should both be set to false when trying to use the debug player with trace() statements. If you need more then I suggested working with fdb to debug your Flex 1.5 app at runtime. I believe that with all of these approaches (and in my opinion even without many of them) you can build successful applications that are more complicated than a "Hello World" application. As stated earlier, in Flex 2.0 this will not be necessary because it will use AS3 with Flash Player 9 - the debug version of this player will ship with Flex 2.0 and will show stacktrace information with errors etc. -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of maxym.hryniv Sent: Wednesday, May 03, 2006 11:11 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Uncaught exceptions in Flex 1.5 Can someone give a response The question was : when I use debug player, configured by mm.cfg I receive only messages like "Warning: Uncaught exception, message text" of course it's not enough. Can I configure debug player to receive information like sender class&&method? If not it's usable only for "Hello World" applications. Of course I can create BaseError class that will know error context and format error message how I want, but it's not applicable for libraries that I'm using (as2lib). Respect. --- In flexcoders@yahoogroups.com, "maxym.hryniv" <[EMAIL PROTECTED]> wrote: > > I'm still waiting for reply. > --- In flexcoders@yahoogroups.com, "maxym.hryniv" wrote: > > > > Hi, Peter. Thank you one more time for your help. I have one more > > question: when I use debug player, configured by mm.cfg I receive > only > > messages like "Warning: Uncaught exception, message text" of course > > it's not enough. Can I configure debug player to receive information > > like sender class&&method? If not it's usable only for "Hello World" > > applications. Of course I can create BaseError class that will know > > error context and format error message how I want, but it's not > > applicable for libraries that I'm using (as2lib). > > > > Respect. > > > > --- In flexcoders@yahoogroups.com, "maxym.hryniv" wrote: > > > > Thank You Peter. It's a shame for me that i didn't know that. I'll > use > > all of these tools. And i'm waiting for Flex 2. > > Thank You one more time. > > --- In flexcoders@yahoogroups.com, "Peter Farland" > > wrote: > > > > > > Some of the comments I made also apply to Flex 1.5's usage of > > > ActionScript 2 in Flash Player 7. > > > > > > ActionScript 2 has try/catch syntax and the Error type, there are > > debug > > > versions of the flash player that ship with Flex 1.5 which you > > should > > > use during development, you can use trace() to report information > to > > a > > > debug log - it too was called flashlog.txt and the mm.cfg file > still > > > applies to Flex 1.5. In fact, this file should be setup and > > monitored > > > for warnings and errors from the flash player during development > at > > all > > > times (I use tail.exe from cygwin to monitor this file like a > > console > > > log). There is a command line debugger in Flex 1.5 called fdb... > > and, of > > > course, we built all of the ActionScript 2 code for Flex 1.5 using > > all > > > of these tools... though admittedly the tools and language > features > > we > > > had to build Flex 2 are even better and will be available soon. > > > > > > Do you have the debug versions of the player? > > > Do you have mm.cfg setup in your user directory and do you monitor > > the > > > flashlog.txt file? > > > > > > > > > -Original Message- > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] > com] > > On > > > Behalf Of maxym.hryniv > > > Sent: Friday, April 28, 2006 5:17 AM > > > To: flexcoders@yahoogroups.com > > > Subject: [flexcoders] Re: Uncaught exceptions in Flex 1.5 > > > > > > I'm still waiting for reply. > > > --- In flexcoders@yahoogroups.com, "maxym.hryniv" wrote: > > > > > > > > Hi, Peter > > > > It's good that we have at last normal exception handling in 8. 5 > > > beta. > > > > But it's only beta for now and we are creating apps using Flex > 1. > > 5. > > > So > > > > the question is "How we can fight silent exceptions death in > Flex > > 1. > > > 5 > > > > ???". > > > > I have some ideas but to realise them i have to rewrite all flex > > 1.5 > > > > framework and i think it's not acceptable. > > > > > > > > Waiting for reply , > > > > Max > > > > --- In flexcoders@yahoog
RE: [flexcoders] Re: Uncaught exceptions in Flex 1.5
Some of the comments I made also apply to Flex 1.5's usage of ActionScript 2 in Flash Player 7. ActionScript 2 has try/catch syntax and the Error type, there are debug versions of the flash player that ship with Flex 1.5 which you should use during development, you can use trace() to report information to a debug log - it too was called flashlog.txt and the mm.cfg file still applies to Flex 1.5. In fact, this file should be setup and monitored for warnings and errors from the flash player during development at all times (I use tail.exe from cygwin to monitor this file like a console log). There is a command line debugger in Flex 1.5 called fdb... and, of course, we built all of the ActionScript 2 code for Flex 1.5 using all of these tools... though admittedly the tools and language features we had to build Flex 2 are even better and will be available soon. Do you have the debug versions of the player? Do you have mm.cfg setup in your user directory and do you monitor the flashlog.txt file? -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of maxym.hryniv Sent: Friday, April 28, 2006 5:17 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Uncaught exceptions in Flex 1.5 I'm still waiting for reply. --- In flexcoders@yahoogroups.com, "maxym.hryniv" <[EMAIL PROTECTED]> wrote: > > Hi, Peter > It's good that we have at last normal exception handling in 8.5 beta. > But it's only beta for now and we are creating apps using Flex 1.5. So > the question is "How we can fight silent exceptions death in Flex 1. 5 > ???". > I have some ideas but to realise them i have to rewrite all flex 1.5 > framework and i think it's not acceptable. > > Waiting for reply , > Max > --- In flexcoders@yahoogroups.com, "Peter Farland" > wrote: > > > > Hi Mykola, > > > > Have you used the debug versions of the Flash Player during > > development? The debug version of the Flash Player reports uncaught > > exceptions and it also traces information to a flashlog.txt file as > long > > as you have a mm.cfg file setup in your user directory. We include > debug > > versions of the Flash Player (i.e. the Standalone Player, the > > Firefox/Netscape/Opera plugin and MSIE Active-X player) in the Flex > > installer. We include them for the same reasons that you state - > > "without having proper error reporting it is impossible to build > > anything larget than hello-world presentations". Flex Builder has a > > visual debugger with breakpoints and watch statements. Also AS3 > Error > > objects remember their stacktraces and you can print them out if > you're > > using the debug player. We built the Flex 2 framework of over 1000 > > classes using the same tools as you would to build your own > > applications... I feel that they are adequate. > > > > Regarding the confusion, it wasn't that important - it was just > that > > from my reading the various posts on this thread I got the > impression > > that there were two complaints here that were at odds with each > other. > > One complaining they couldn't manage errors coming from lots of > > different places and the other that they weren't getting enough > errors > > and related information at runtime. > > > > Regards, > > Pete > > > > > > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] com] > On > > Behalf Of Mykola Paliyenko > > Sent: Tuesday, April 25, 2006 5:24 PM > > To: flexcoders@yahoogroups.com > > Subject: Re: [flexcoders] Uncaught exceptions in Flex 1.5 > > > > > > Ok Peter, > > no idea why you've been confused but... > > ActionScript specification has a notion of throwable objects, so > saying > > that Exception is a bug of the AS2Lib is slightly incorrect. I'm > > relaizing that due to the size constraints of the player it might be > > good idea not to include exception handling in it, but once more > again > > you can add this in the development version of the player and this > > should be extremely easy to do if the overal palyer's architecture > is > > good enough, isn't it? > > > > My opinion is that without having proper error reporting it is > > impossible to build anything larger than hello-world presentations > with > > a very good quality, so I'd warn people to treat Flex/Flash as a > really > > serious platform unless this feature will be implemented. > > Flex Developers in my company mostly are very unhappy with the > quality > > of the framework and the level of the support Adobe provide for the > > users, I'm not saying about paid support I'm saying about community > > support, feature requests, bugfixes, open source frameworks around > Flex > > etc. I see no other way for developing the really good product other > > than involve the community into the development. It is the way lots > of > > really cool stuff were developed for the last year and it is mostly > > ignored by Adobe. > > > > You have a great idea of RIA and a
