Op 2010-07-12 17:09, Werner Schoenmaekers het geskryf: > The devexpress mediators for a list ( + cxGrid ) do change the object > state ( of the list and the object itself ).
Then the Devexpress mediators are implemented differently to the others. I never use inline editing (via Grids etc), so for me any list View is read-only (no direct editing allowed). I use the fpGUI mediators. > But the other (not list) mediators do not do this. Not everybody wants to have the ObjectState updated immediately. This is easily handled in one of two ways: 1) On closing a Edit/Maint form that edited an Object, set the Dirty property and call Save. 2) Implement Setter methods like Andrew mentioned. Demo 21 (Address Book) shows how this can be done. In that demo a TMarkObject was introduced with a single Mark method which sets the ObjectState when appropriate. This method is called by the setters of each descendant and their properties. This has the benefit that ObjectState handling is localized to one place, and not scattered all around in your code wherever you could edit an Object instance. I prefer option 1 though. Regards, - Graeme - ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk
