FLUID-163: Create a more robust way of passing in custom key bindings.

Metadata

Source
FLUID-163
Type
Sub-task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Colin Clark
Reporter
Colin Clark
Created
2008-01-17T12:36:07.000-0500
Updated
2011-02-22T16:27:52.704-0500
Versions
  1. 0.1
Fixed Versions
  1. 0.3
Component
  1. Framework

Description

At the moment, users can only specify custom activation keys, all of which are bound to the same handler. It's not easy to customize bindings to the up/down actions. I'd like to develop a standard way of mapping keys to particular semantics and their handler functions.

Comments

  • Colin Clark commented 2008-02-08T00:00:44.000-0500

    I implemented a concept of a "key binding," which is a simple object that specifies a connection between a keypress and an activation handler:

    {
    modifier: undefined || null || CTRL || ALT || SHIFT,
    key: key,
    handler: function
    }

    This allows users to specify different activation handlers for different key presses.

  • Michelle D'Souza commented 2011-02-22T16:27:52.702-0500

    Closing issues that were resolved for 1.0 and earlier releases.