Summary: | KeySequenceText should have API to limit number of key strokes | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Douglas Pollock <douglas.pollock> | ||||
Component: | UI | Assignee: | Chris McLaren <csmclaren> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P1 | CC: | csmclaren | ||||
Version: | 3.0 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Douglas Pollock
2003-08-26 16:27:35 EDT
Created attachment 5864 [details]
Patch for KeysPreferencePage and KeySequenceText
KeySequenceText now has a setMaxStrokes, which makes sure that the key sequence
it generates is capped at the given value. It exports a constant of INFINITE,
which means no capping. KeysPreferencePage sets the cap to 4.
Check the patch and then commit. Change 4 to any value you want. patch applied. works fine. changed CommandManager to reject KeyBindingDefinitions with strokes longer than 4 (to avoid the Keys preference page truncating selected key sequences) |