On Thu, 17 Jul 2003 15:39:30 +0200 Xavier Nodet <[EMAIL PROTECTED]> wrote:
XN> VZ> So maybe actually we do want to have something like this, after the move
XN> VZ> in your example above:
XN> VZ>
XN> VZ> [A]
XN> VZ> [A/B]
XN> VZ> ... all data for the folder B ...
XN> VZ> VisibleParent=C # folder tree checks this
XN> VZ>
XN> VZ> [C]
XN> VZ> [C/B]
XN> VZ> LinkTo=A/B # or "AliasFor"
XN> VZ>
...
XN> That the information about a folder should be stored using the
XN> identifier as the key. The method
XN>
XN> ProfileImpl::CreateProfile(const String & ipathname,
XN> Profile const *Parent)
XN>
XN> should use the identifier of the folder, instead of its path.
I still don't understand. Identifier is initially the same as path, right?
So we still have this before the move:
[A]
[A/B]
...
[C]
What do we have after it? An how does children enumeration work?
Thanks,
VZ
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Mahogany-Developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-developers
