Eclipse Community Forums: Eclipse Platform » CommonNavigator and default resource open behaviour

Help

Home

Home » Eclipse Projects » Eclipse Platform » CommonNavigator and default resource open behaviour

Show: Today's Messages :: Show Polls :: Message Navigator

CommonNavigator and default resource open behaviour [message #1425837]

Wed, 17 September 2014 22:52

Nigel Daniels

Messages: 40
Registered: May 2011

Member

Hi,

I am building an RCP product that includes a GMF editor and decided to
use the CommonNavigator to provide a much cleaner look to the
navigation. However having implemented this I can no longer
double-click the files associated with my editor to open them. This used
to work with the previous default navigator. If I look in the
preferences the files I am using are associated with the correct editor.

What am I missing? Is there an extension point I need to update to
re-enable this behavior?

Thanks for any help,

Nigel

Report message to a moderator

Re: CommonNavigator and default resource open behaviour [message #1475150 is a reply to message #1425837]

Sun, 16 November 2014 02:14

Nigel Daniels

Messages: 40
Registered: May 2011

Member

Any suggestions out there??

On 17/09/2014 15:52, Nigel Daniels wrote:
> Hi,
>
> I am building an RCP product that includes a GMF editor and decided to
> use the CommonNavigator to provide a much cleaner look to the
> navigation. However having implemented this I can no longer
> double-click the files associated with my editor to open them. This used
> to work with the previous default navigator. If I look in the
> preferences the files I am using are associated with the correct editor.
>
> What am I missing? Is there an extension point I need to update to
> re-enable this behavior?
>
> Thanks for any help,
>
> Nigel

Report message to a moderator

Re: CommonNavigator and default resource open behaviour [message #1482636 is a reply to message #1475150]

Fri, 21 November 2014 23:54

Nigel Daniels

Messages: 40
Registered: May 2011

Member

I've done some more tracing and determined the problem is caused because
when the CommonNavigatorManager classes open method is called it calls
the openAction.run() method. This method then checks for a handler.
When I use a Navigator such as the ProjectExplorer the openAction
handler is set to an OpenFileAction, however when I use my own Navigator
based on the CommonNavigator the handler is null.

Can any one suggest what I need to do to ensure that the handler is not
null?

Again thanks for any suggestion.

On 15/11/2014 18:14, Nigel Daniels wrote:
> Any suggestions out there??
>
> On 17/09/2014 15:52, Nigel Daniels wrote:
>> Hi,
>>
>> I am building an RCP product that includes a GMF editor and decided to
>> use the CommonNavigator to provide a much cleaner look to the
>> navigation. However having implemented this I can no longer
>> double-click the files associated with my editor to open them. This used
>> to work with the previous default navigator. If I look in the
>> preferences the files I am using are associated with the correct editor.
>>
>> What am I missing? Is there an extension point I need to update to
>> re-enable this behavior?
>>
>> Thanks for any help,
>>
>> Nigel
>

Report message to a moderator

Previous Topic:	Plugin start and Application start
Next Topic:	[E4] Memory leak on actions?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 13:11:30 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter