The context is the location in which this binding is valid. For commands that are visible everywhere—typically the kind of options in the default menu—they can be associated with the org.eclipse.ui.contexts.dialogAndWindow
context. If the command should only be invoked from dialogs, then the org.eclipse.ui.contexts.dialog
context would be used instead.
fragment.e4xmi
of the com.packtpub.e4.clock.ui
project.org.eclipse.ui.contexts.dialog
.If there is no change in the behavior, try cleaning the workspace of the target instance at launch, by going to the Run | Run… menu and choosing Clear on the workspace. This is sometimes necessary when making changes to the fragment.e4xmi
file, as some extensions are cached and may lead to strange behavior.
Context scopes allow bindings to be valid for certain situations, such as when a dialog is open. This allows the same KeyBinding to be used for different situations, such as a Format operation—which may have a different effect in a Java editor than an XML editor for instance.
Since scopes are hierarchical, they can be specifically targeted for the contexts in which they may be used. The Java editor context is a sub-context of the general text editor, which in turn is a sub-context of the window context, which in turn is a sub-context of the windowAndDialog
context.
3.141.192.183