Age | Commit message (Collapse) | Author | Files | Lines |
|
With this, we fork and let the child deal with the gstreamer pipeline
while the parent is still able to process events from the transimtter.
Using blocking dispatching function will make the main loop be stuck in
processing events without being able to dispatch any handlers that might
be due to the requests from the transmistter side. So in order to allow
the mainloop (still) handle the events, we fork and let child deal with the
gstreamer pipeline.
Bug-AGL: SPEC-3675
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I50e1d49b55849dc32f611538bad2ce1c676c9a97
|
|
This way we inform the users that the receiver won't relaying back
events. This could happen if the user starts the transmitter side after
starts the receiver.
For now this just informs the users, requiring a follow-up fix, as to
determine why we do not have a valid seat and input devices, if the order
in which the transmitter and receiver is started is changed.
Bug-AGL: SPEC-3601, SPEC-3605
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I0c398358f22697323bd90cdaedcbfac03ca5c8dc
|
|
Bug-AGL: SPEC-3605
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: Ia352702d0c43f1f2ccecbffea85f3d0f17f2fd56
|