"keyType" is to simulate people type the keyboard and it includes delays between each keystroke. That is why it is slow, but it looks more closer to real people operation. "keyUp" and other key events are different from mouse events and it should be input related, i.e., it should be added to each keystroke, that is why I did not consider them in the respond event attribute.
I would suggest you open an issue, add the key events to the EventHandler class so that the respond attribute can accept the key events, then commit to the trunk. Or wait for me to fix it by tonight. Thanks, Jian On Dec 11, 12:14 pm, Mikhail Koryak <[email protected]> wrote: > Hi, > i need to fire an event in tellurium, in selenium you could do the > following: > fireEvent "locator", "keyUp" > > which would fire the keyUp event on the locator. I need to do this > instead of using keyType because keyType is about 100x slower then > type, and what i should be doing is using type and then firing the > event in order to trigger some javascript on the UI. > > do we have something like this currently, or should i implement it and > commit it to my branch? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en -~----------~----~----~----~------~----~------~--~---
