That's pretty much how mine will work as well. Although I haven't had to add
the ajax part. I just needed to create it to display to another team how it's
supposed to work.
With looking at an older message of yours, your getting the same results I
was getting. That's when I removed all the treeview applied html and attributes
and that got it working right.
I assume your using a button or submit for the refresh as your saving it. On
that note I would remove all the treeview attributes at that time, just before
the save.
rolfsf <[EMAIL PROTECTED]> wrote:
Our tree will potentially change within the time that someone is using
it. In fact, the user will be creating and saving new nodes; Other
users will be creating and saving new nodes. Both users need to be
able to refresh the tree to see nodes added by themselves and others.
The async tree starts as an empty
. We want to return to that
initial state when we click a refresh button. A completely clean
slate, then reload with the fresh data as if we had just opened it for
the first time.
On May 1, 10:40 am, ripple wrote:
> I'm not sure why you write about removing the contents in a
? At what point would that beneficial? Your working with the ajax tree, but how
much ajax interaction are using? Only at onload time?
>
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
