TabbedMDIManager and Persistence

[James Mulvey]

I''m trying to use TabbedMDIManager with an application which dynamically adds / removes MDI children, but which needs to persist settings.

Looking at the rough implementation of TabbedMDIManager''s persistence I''m a little bit concerned; compared with DockingManager it seems very brittle and limiting.

TabbedMDIManager provides no event to dynamically create a missing control & seems to persist settings using the MDI Child .Text as an identifier. This will clearly break if the MDI child text is ever changed.

DockingManager seems much less problematic:
1) It gives a callback to supply a missing control.
2) It uses Control.Name as an id (which could be a GUID or something as it is not user displayed).

Is there any plan to fix these issues / is there a way to achieve what I''m looking for?

Thanks,

James

[Saradha]

Hi James,

Sorry for the delay in getting back to you. We are able to see the child.Text identifier issue and logged a bug report in this regard. Please track the status of this bug in the link below.

rel='nofollow' href="<http://www.syncfusion.com/support/issues/tools/Default.aspx?ToDo=
view&questId=2765">Defect
#2765 - Tabbed MDI windows state persistence crashes when MDI child''s
text is changed.

We will forward the callback issue to our development team and let you know.

Thanks for bringing this issue to our attention.

Regards,
K.Saradha Devi.

[Saradha]

Hi James,

We regret for the inconvenience caused. Here is the correct link for the Defect # 2765.

Defect #2765 - Tabbed MDI windows state persistence crashes when MDI child''s text is changed.

Regards,
K.Saradha Devi.