Bug 328808 - F3 - Keybinding conflicts occurred
Summary: F3 - Keybinding conflicts occurred
Status: RESOLVED WORKSFORME
Alias: None
Product: CDT
Classification: Tools
Component: cdt-editor (show other bugs)
Version: 7.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Anton Leherbauer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-27 06:48 EDT by Yevgeny Shifrin CLA
Modified: 2017-07-27 20:24 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yevgeny Shifrin CLA 2010-10-27 06:48:30 EDT
Build Identifier: 20100617-1415

Please refer to description in CDT user forum:
http://www.eclipse.org/forums/index.php?t=msg&goto=632803&S=a0ea867bbcb8a2f203d12dcfe3bef97d#msg_632803

This issue occured twice. After restarting eclipse problem is solved.  

Reproducible: Sometimes

Steps to Reproduce:
Happened suddenly after while working with eclipse (f3 stopped working). In the last several months this happened twice.
Comment 1 Anton Leherbauer CLA 2010-10-27 07:06:13 EDT
Looks like the macro exploration control has not unregistered its command handlers.  I am not sure how this can happen.  Are there any exceptions in the workspace log?
Comment 2 Yevgeny Shifrin CLA 2010-10-27 08:20:13 EDT
(In reply to comment #1)
> Looks like the macro exploration control has not unregistered its command
> handlers.  I am not sure how this can happen.  Are there any exceptions in the
> workspace log?

Hi,

No exceptions except for the warning that I posted in http://www.eclipse.org/forums/index.php?t=msg&goto=632803&S=a0ea867bbcb8a2f203d12dcfe3bef97d#msg_632803

It does not happen immediately when eclipse is started. Problem occurs on opened and working eclipse after a while. Restarting eclipse solves it.

Thanks,
Yevgeny
Comment 3 Nathan Ridge CLA 2017-01-02 01:14:57 EST
Yevgeny, do you still see this issue?
Comment 4 Nathan Ridge CLA 2017-07-27 20:24:58 EDT
Closing as there hasn't been a response to comment 3.