Closed GoogleCodeExporter closed 8 years ago
With 'contents screen' you mean a preview pane in your application?
ad 3.
We are in fact calling deactivate() for the active node, when the context
changes.
That reflects the context status best, I think
ad 4.
in that case clicking the node again would work as expected.
Alternatively you could use onClick(node) instead of onActivate(node), this is
fired always.
Original comment by moo...@wwwendt.de
on 8 Nov 2010 at 4:07
Duh. onClick is exactly what I was thinking of.
I found that I need to leave the onActivate option, even though there is
nothing in the function, otherwise the node would not be activated. So it
currently looks like...
onActivate: function(n) {
},
onClick: function(n) {
loadPluginView(n.data.plugin_id, n.data.plugin_type, n.data.plugin_type+'_edit_view', false);
},
So with the onClick I am getting my "preview pane"/"contents screen" as I was
hoping. The only problem now is I would like to check if the node is already
open, if so, do not collapse the children. Only the plus/minus sign would be
doing the collapse in this situation.
Original comment by oll...@gmail.com
on 8 Nov 2010 at 4:19
> I found that I need to leave the onActivate option...
I would consider this a bug but i could not reproduce it.
Could you confirm this one?
Original comment by moo...@wwwendt.de
on 9 Nov 2010 at 7:09
Original comment by moo...@wwwendt.de
on 9 Nov 2010 at 7:09
could not reproduce
Original comment by moo...@wwwendt.de
on 14 Nov 2010 at 2:36
Original issue reported on code.google.com by
oll...@gmail.com
on 8 Nov 2010 at 2:37