summaryrefslogtreecommitdiff
path: root/tools/gst-play-kb.c
Commit message (Collapse)AuthorAgeFilesLines
* gst-play: Handle KeyDown event instead of KeyUp on Win32 keyboard handlerSeungha Yang2019-11-191-1/+1
| | | | | | To handle long press case, KeyDown input should be handled instead of KeyUp. Note that OS will take care of the sensitivity of KeyDown event, so we can safely assume one KeyDown as one input. That will not break user experience.
* gst-play: Remove timer GSource from Win32 keyboard handlerSeungha Yang2019-11-191-16/+91
| | | | | Use WaitForMultipleObjects to handle keyboard input only if pending keyboard input exists.
* build: fix werror build on windowsMatthew Waters2019-10-011-0/+1
| | | | _isatty() is in the io.h header
* gst-play: Add support for interacting console input on WindowsSeungha Yang2019-09-261-4/+81
| | | | | Add Windows keyboard input handler. This could make gst-play UX consistent between *nix and Windows.
* tools: play: fix leaving STDIN in non-blocking mode after exitAntonio Ospite2018-03-261-5/+2
| | | | | | | | | | | | | | | | | | | | gst-play-1.0 sets STDIN to non-blocking mode to have the input characters read as soon as they arrive. However, when gst_play_kb_set_key_handler() gets called from restore_terminal() it forgets to restore the STDIN blocking status. This can result in broken behavior for cli command executed in the same terminal after gst-play-1.0 exited. It turns out that putting STDIN in non-blocking mode is not even the proper way to achieve the desired effect, instead VMIN and VTIME in struct termios should be set to 0. Let's do that, and don't mess with the STDIN blocking mode now that it's not necessary. https://bugzilla.gnome.org/show_bug.cgi?id=794591
* tools: play: fix compiler warning on windowsTim-Philipp Müller2013-12-091-0/+1
|
* tools: play: add --interactive switch and basic keyboard handlingTim-Philipp Müller2013-11-241-0/+142
Only pause/play with spacebar for now.
View Lorry Controller Status