[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-pmc] Feature Request: [KeyBindings] provide conflict information to users outside of logging
|
+1. The old behavior was flawed for anyone who wasn't a developer: Normal
users don't look in the log files, so they would have no way to know why
the key binding did nothing (which was the old "conflict resolution"
strategy). This was effectively a bug.
With the new mechanism, the user can not only tell there is a conflict, but
can easily invoke the desired command. It even supports linking to the
keybindings page, making it easy to rebind one of the key sequences, if
desired.
McQ.
Paul
Webster/Ottawa/IB
M@IBMCA To
Sent by: eclipse-pmc@xxxxxxxxxxx
eclipse-pmc-bounc cc
es@xxxxxxxxxxx
Subject
[eclipse-pmc] Feature Request:
10/05/2007 12:52 [KeyBindings] provide conflict
PM information to users outside of
logging
Please respond to
eclipse-pmc@eclip
se.org
Request to approve a feature to notify the user about key conflicts.
GOALS/BENEFITS:
In 3.2 we didn't notify users about failing keybindings at all, and in 3.3
you still have to know to go to the .log file. We seek to notify the users
using the same mechanism as "partial key completion" i.e. pop up the same
dialog as if you had typed ALT+SHIFT+Q or ALT+SHIFT+X. This would allow
them to pick a command to execute or launch the keys preference page to
resolve the conflict
CORRESPONDING BUG(S):
Bug 186403 [KeyBindings] provide conflict information to users outside of
logging
https://bugs.eclipse.org/bugs/show_bug.cgi?id=186403
RISKS:
This is low risk, using support already available in the keybinding
framework. This introduces no new API.
PERFORMANCE IMPACTS:
This should be minimal. The collection of conflicts was already being
calculated, it's just making the information available at different point
in time.
Later,
PW
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc