Jarrod, >No problem. I added NotifyObserversHelper as a convenience instead of >having >to use the BeginUpdate, try..finally, EndUpdate construct. It uses a >reference counted interface to do that for you (in its constructor and >destructor). You can use it within the property setter or in other classes >or GUI code that references the object, either with a simple >NotifyObserversHelper call after a single change is made, or hang on to the >interface before making multiple changes to the object and having it >explicitly or automatically de-referenced after the changes.
Thanks for that explanation, it helps immensely. I've seen the BeginUpdate, try..finally, EndUpdate construct and, outside of what does it do, was wondering if NotifyObserversHelper was the preferred method. [snipped code examples] >What NotifyObserversHelper and BeginUpdate/EndUpdate give you is a single >observer notification for multiple changes to avoid things like multiple UI >updates in MGM. Excellent. Thanks again for all your work on this. -- Dave Keighan aka TDelphiHobbyist http://tdelphihobbyist.blogspot.com/ ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk
