| dialogAndWindows and windows contexts problems [message #277218] |
Mon, 06 December 2004 18:42  |
Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
I'm trying to define CTRL+B to be BOLD when in the "graphicalText" scope,
which extends dialogAndWindows. However, CTRL+B is defined in the "window"
scope as being buildAll. But, the graphicalText context should win here
because the binding matches exactly the active Scope: "graphicalText". So
why do I get a warning message and disabled keybindings in this scenario?
My workaround is to have "graphicalText" extend the "windows" scope. But
this seems like it limits the use of the text function to the main workbench
window.
|
|
|
| Re: dialogAndWindows and windows contexts problems [message #277358 is a reply to message #277218] |
Thu, 09 December 2004 11:20  |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
I need that "graphicalText" scope be a sub-scope of both dialog and window
scopes. But multiple parents aren't supported, so I must choose
inDialogAndWindows scope. The problem being that "inWindows" is considered
to be a sibling of "graphicalText", when really it should be one of its two
possible parents. The hierarchy seems inverted to me. We have inWindows
extends inDialogAndWindows instead of inDialogAndWindows extends both dialog
and windows scopes.
"Randy Hudson" <none@us.ibm.com> wrote in message
news:cp2qom$t2m$1@www.eclipse.org...
> I'm trying to define CTRL+B to be BOLD when in the "graphicalText" scope,
> which extends dialogAndWindows. However, CTRL+B is defined in the
"window"
> scope as being buildAll. But, the graphicalText context should win here
> because the binding matches exactly the active Scope: "graphicalText". So
> why do I get a warning message and disabled keybindings in this scenario?
>
> My workaround is to have "graphicalText" extend the "windows" scope. But
> this seems like it limits the use of the text function to the main
workbench
> window.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02344 seconds
Home