I know I've read this from somewhere, but it bears repeating "Events should always call methods" - unknown
If an object created in one datasession is bound to an object in another datasession some weird behavior can be observed. If the bindevent binds to a method and the only line of code in that bound method calls another method on the object the odd behavior isn't observed. Some things I've seen is missing properties or child objects, and C0000005 issues. I now create two methods: methodname_event and methodname Methodname_event is the delegate and methodname is what it forwards the information to. Tracy -----Original Message----- From: Rick Schummer Sent: Thursday, July 24, 2008 11:44 AM >> In my experience, bindevents is great !!<< I think BindEvent() is great too, but one other *little* drawback is the debugging of your code becomes way more difficult because you are off the call stack. I am not saying this is a showstopper, but I have worked with my own code and other developer's code and can tell you it can lead to hair loss and lots of wasted time if you are not careful. Tracking things down can be time consuming. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
