I created in Click Examples a page - ActionLinkTreePage that is
reproduction the problem you mention (see attachment - the example is
based on the PageLinkTreePage).
From the example the ActionLinks are added during the rendering event
which occurs after the onProcess event.
Well, I'm calling the method createTree() method in onInit (or Page
constructor), but the PageLinkTree was the only example that allowed
make the display the tree like desired.
Why not use a TreeListener to
detect when nodes are selected or not?
The tree component looks quite confusing, so I adopted the PageLinkTree
example since that looked simpler and had the generated html code that
looked at most like what it does :(.
For simplicity, for the API, I would have expected something like the
Table API - a "Cell Decorator", where the user is responsible for
decorating the cell (with whatever control it wants), and it's also
responsible for those events :(.
Alternatively you might have to
look at adding the ActionLinks in the Tree's onInit event so that they
are available during processing.
I'll try to figure out how to do it so :).
thanks,
Joseph.
