On Thu, 17 Jul 2003 11:53:56 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
VZ> So maybe actually we do want to have something like this, after the move VZ> in your example above: VZ> VZ> [A] VZ> [A/B] VZ> ... all data for the folder B ... VZ> VisibleParent=C # folder tree checks this VZ> VZ> [C] VZ> [C/B] VZ> LinkTo=A/B # or "AliasFor" VZ> VZ> Of course, we can have more than one LinkTo but a whole chain of them... Isn't it what Xavier and Robert discussed and decided against it? VZ> Another possibility I see is to simply forbid changing the parent, i.e. VZ> renaming/moving folders should only be allowed between siblings. This is VZ> more restrictive, of course It would be unusable, at least for me. Moving between siblings means only changing appearance order in the folder list, which I almost never use (if we don't count renaming). What I use most is changing parents. Regards, Nerijus ------------------------------------------------------- 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
