[platform-dev] Re: Reset currentSelected Node after a update of keys

[tomwheeler]

I have always been confused by the differences (if there are any)
between selected nodes, activated nodes and current nodes. The
javadoc doesn't provide much clue that I've ever found.

To take a guess in your case, maybe the equivalent is in
ExplorerManager.setSelectedNodes(). If so, maybe you could iterate
over all the opened TopComponents, pass each to ExplorerManager.find()
and then call setSelectedNodes on whatever you get back. Of course,
there's no preventing you from having multiple TCs open at once, each
with their own ExplorerManager, and this approach would likely fail in
such a case.

Hopefully someone can expound on the differences between
selected/activated/current nodes. If so, it might help you. I'd even
volunteer to document what they say in the Wiki and/or API
documentation.

On Tue, Mar 23, 2010 at 1:11 PM, bruehlicke <address-removed> wrote:

[bruehlicke]

Thanx Tom,

yea - I have multiple Topcomponents open - but - lucky only one
Explorer Tree view - so this may work ...

B-)

On Wed, Mar 24, 2010 at 12:58 PM, Tom Wheeler <address-removed> wrote: