|Re: Ctrl+1 key binding lost in 3.3 to 3.6 upgrade. [message #664419 is a reply to message #664332]
||Fri, 08 April 2011 18:12
| Adil Fulara
Registered: July 2009
Thank you for your reply.
In v3.3, as per my understanding as long as we subclassed the
class, key bindings were automatically dispatched from the workbench to my custom implementation of IQuickAssistAssistant + IQuickAssistProcessor.
So pressing 'ctrl+1' or 'ctrl+space' used to trigger my code. This does not seem to be happening on 3.6 as i see with the tracing option turned on.
This http://www.eclipse.org/forums/index.php?t=msg&goto=33460 0& forum entry is where i made the above assumption where Dani confirms that subclassing TextEditor basically hooks u up with ctrl+1. As mentioned in my previous post TextSourceViewerConfiguration subclass is where i provide the text editor with my QuickAssistAssitants. This is the reason why i dont have any bindings defined in my plugin.xml [extension point 'org.eclipse.ui.bindings'] as there is no command as such to invoke.
This is how i think my editor informs the workbench to make it quick fix aware [in reply to your q:Where is the quick fix/ctrl+1 coming from? ]
Action action = new ContentAssistAction(mResourceBundle, "ContentAssistProposal.", this);
String id = ITextEditorActionDefinitionIds.CONTENT_ASSIST_PROPOSALS;
Sorry i am not an expert in the texteditor domain. So i may be stating the obvious
[Updated on: Fri, 08 April 2011 22:55]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.11405 seconds