| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Actual fix is change from keypress to keydown. tested with chrome.
|
|
|
|
|
|
|
|
One line, two changes:
keypress->keydown:
- fixes #137. Chrome doesn't dispatch a keypressed on tab. Firefox and
chrome both dispatch a keydown, so this works in both.
$(document)->element:
- fixes #171. Don't listen to text input events globally, only on the
element.
|
|
|
|
See https://github.com/baconjs/bacon.js
Usage right now:
we have rz_bus to hold global busses:
- names: for autosuggest
- ui busses:
- ui_key
- ui_input
The events are objects with {where: from consts, keys/input}
(could maybe just use the events and rely on the target element
class/id)
And graph has it's own bus:
graph.diffBus
(camelcase probably not the right style - will fix in later commit)
To publish to a bus you use push.
To insert another stream to a bus you use plug.
To listen to a bus you use onValue (you can use subscribe too to get
errors and end of stream event, but we don't use that yet).
This allows usage of map, filter, flatMap, see github repo for cool
examples.
|
|
|
|
|
|
After using up/down keys to select one of the entries you had an extra
enter required to "complete" the sentence.
Reproduce:
ctrl-alt-i (focus on 'Type here to create a network', #textanalysis)
The first enter is the selection, the second is ignored (the bug fixed
by this commit), the third is handled by the #textanalysis keypress
trigger.
The fix was simple, not sure why it works. Seems there is a
keyup/keypress interaction. The keyup was on the document element,
replaced by a keypress on the same element.
|
|
|
|
Possibly introduces required double enters sometimes. This is a result
of an exception thrown in the callback, needs work.
|
|
|
|
|
|
|
