Tom Cornilliac wrote:
A word of caution with large trees... if you are attempting moves with
very large trees please be patient.  If you attempt two moves
simultaneously this can in some situations lead to corruption of the
tree metadata and require you to run the "fix tree" tool to tidy up your
tree.

Yup, I can testify to this one!! Our tree is somewhat large and I have very impatient content contributors that like to move nodes :(

Thanks Geoff, You just reminded me that I've been meaning to look into
a fix for this. Maybe some sort of lock? Have you considered any
solutions?

Not me. This is more Paul from Curtin's domain. I suspect it might be something trickier than that. It seems as though the move takes its cue from the state of the JS UI. Perhaps it should double check the state of the nation for itself without relying on the JS tree for positional information.


-- geoff
http://www.daemon.com.au/

---
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to