The September/October 2010 edition of REALbasic Developer came out this week. Marc Zeedar has additional information about the REAL Studio Web Edition and includes some details that I didn’t cover in my Web Edition blog post.
JC has an article on Trapping For Errors which is a good read. Coincidentally, in my regular column I talk about how having a program fail can be instructive and how ‘failure is always an option’.
More information on REALbasic Developer Magazine can be found here.
In almost all of my applications I have an automated bug reporter class that allows the user to send me the Runtime Error type, the Error Stack and (hopefully) a brief description from the user on what they were doing. It lives only in the App.UnhandledException event and nowhere else. It’s far from perfect, but it’s better than nothing.
What do you have in your RB apps to get that crucial error information?