Hi, On 7 June 2013 11:16, Marc Chalain <marc.chal...@gmail.com> wrote: > I tried and at now, it seems to add a lot of complexity. > I solution is to read the weston.ini file inside input.c... but is it > regular ?
This is the usual solution for now, yes. > 2013/6/7 Daniel Stone <dan...@fooishbar.org> >> >> Hi, >> >> On 7 June 2013 06:33, Marc Chalain <marc.chal...@gmail.com> wrote: >> > A input device could not be not configurated. That should not be an >> > error >> > and just an unhandled device. >> > On embedded configuration there is different input devices which are not >> > used. >> >> The intention of this codepath is to avoid the situation on desktop >> devices where Weston starts but the input devices are broken. In that >> case, starting with no input devices will leave you unable to exit >> unless you can use SSH or similar to kill it. >> >> I realise it's different on embedded, but in this case, a >> configuration or command-line option saying that it's OK to start with >> no input devices seems appropriate. >> >> Cheers, >> Daniel > > _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
