Well, the HistoryManager needs to know what state to save. It isn't practical to iterate over all properties with a for-in loop and save everything, because you'd quickly run up against the limit on the size of data you can store locally.
So you need to implement saveState() and loadState() to tell the HistoryManager what to save and reload. If all your components have similar state information that should be saved, then implement saveState() and loadState() in a base class. - Gordon -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tansht Sent: Tuesday, January 24, 2006 11:46 PM To: [email protected] Subject: [flexcoders] How to define a Global Histroy Manager Hi, there According to the Livedoc (Implementing the saveState() and loadState() methods in the History Manager charpter), it seems every component needs a customized History Manager function. Currently I am working on a large Flex project and there are a great deal of components in the application. I am wondering whether I can have a global History Manager in order to have back/forward of browser function. If it's possible, how can I do it? cheers David -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
