Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [platform-ui-dev] Proper way to inherit key binding scopes

> -----Original Message-----
> From: Douglas Pollock [mailto:douglas.pollock@xxxxxxxx]
> Sent: Thursday, May 06, 2004 2:36 PM
> To: platform-ui-dev@xxxxxxxxxxx
> Subject: Re: [platform-ui-dev] Proper way to inherit key 
> binding scopes
> On Thursday 06 May 2004 14:19, Thomas Fletcher wrote:
> >       <scope
> >             name=""
> >             parent="org.eclipse.ui.textEditorScope"
> >             description="%cEditor.description"
> >             id="org.eclipse.cdt.ui.cEditorScope">
> >       </scope>
> Please use "context" instead of "scope" and "parentId" 
> instead of "parent".
> > This doesn't seem to work any more with M8.  A simple 
> CTRL-L to bring up
> Changing "scope" to "context" should fix this.  If not, then 
> please try using 
> the context tracing/debugging options on start-up ("-debug").

Thanks for the response, but it didn't change the behaviour and 
running with the context tracing turned on didn't generate any

The extension now reads:

Can I also get an answer to the basic question of "should I have to be 
hard coding" multiple inheritances in my editor or should it all be
resolved using the extension points.  I'm assuming that from your response
it should be inheriting the values from the extension point.

Also ... how come this <scope to <context extention point change
has not been documented as part of the 3.0 editor migration (the extension 
point information still says since 2.1 and the code examples all still 
use <scope)  Is the plan to deprecate <scope in favour of <context?  Are 
all of the other references to scope (ie in the commands) also going to 
be deprecated and changed to context?  What about parent vs parentId in
the extention point description?

Just trying to plan my future here.

Thanks for any help you can provide,

Back to the top