On 01/14/2015 06:33 AM, Pekka Paalanen wrote:
Btw. showing that message on screen instead of hiding it in the log
would be quite a lot of effort: add an event to desktop-shell.xml, let
Weston emit the event, and make weston-desktop-shell create a new
window with the message. That window might ev
On Mon, 5 Jan 2015 08:46:28 +1000
Peter Hutterer wrote:
> On Fri, Jan 02, 2015 at 02:22:04PM +0100, Sjoerd Simons wrote:
> > On Fri, 2015-01-02 at 13:07 +, Daniel Stone wrote:
> > > Hi,
> > >
> > > On 2 January 2015 at 12:24, Sjoerd Simons
> > > wrote:
> > >
> > > Apart from blatent config
On Fri, Jan 02, 2015 at 02:22:04PM +0100, Sjoerd Simons wrote:
> On Fri, 2015-01-02 at 13:07 +, Daniel Stone wrote:
> > Hi,
> >
> > On 2 January 2015 at 12:24, Sjoerd Simons
> > wrote:
> >
> > > Under the assumption that weston-launch is a tool for developers to
> > > start weston, then sure
On Tue, Dec 30, 2014 at 05:19:45PM +, Daniel Stone wrote:
> Hi,
>
> On 29 December 2014 at 00:03, Peter Hutterer
> wrote:
>
> > On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
> > > The reason for not having any input devices could actually be that there
> > > are no input dev
On Fri, 2 Jan 2015 13:07:57 +
Daniel Stone wrote:
> Hi,
>
> On 2 January 2015 at 12:24, Sjoerd Simons
> wrote:
>
> > Under the assumption that weston-launch is a tool for developers to
> > start weston, then sure fine. If weston-launch gets used to autostart
> > weston on bootup (as i'm do
On Fri, 2015-01-02 at 13:07 +, Daniel Stone wrote:
> Hi,
>
> On 2 January 2015 at 12:24, Sjoerd Simons
> wrote:
>
> > Under the assumption that weston-launch is a tool for developers to
> > start weston, then sure fine. If weston-launch gets used to autostart
> > weston on bootup (as i'm doi
On Fri, 02 Jan 2015 13:24:36 +0100
Sjoerd Simons wrote:
> On Fri, 2015-01-02 at 13:34 +0200, Pekka Paalanen wrote:
> > On Tue, 30 Dec 2014 17:19:45 +
> > Daniel Stone wrote:
> >
> > > Hi,
> > >
> > > On 29 December 2014 at 00:03, Peter Hutterer
> > > wrote:
> > >
> > > > On Sun, Dec 28,
Hi,
On 2 January 2015 at 12:24, Sjoerd Simons
wrote:
> Under the assumption that weston-launch is a tool for developers to
> start weston, then sure fine. If weston-launch gets used to autostart
> weston on bootup (as i'm doing in some cases), that behaviour is
> horrible.
>
It's not a develope
On Fri, 2015-01-02 at 13:34 +0200, Pekka Paalanen wrote:
> On Tue, 30 Dec 2014 17:19:45 +
> Daniel Stone wrote:
>
> > Hi,
> >
> > On 29 December 2014 at 00:03, Peter Hutterer
> > wrote:
> >
> > > On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
> > > > The reason for not havi
On Tue, 30 Dec 2014 17:19:45 +
Daniel Stone wrote:
> Hi,
>
> On 29 December 2014 at 00:03, Peter Hutterer
> wrote:
>
> > On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
> > > The reason for not having any input devices could actually be that there
> > > are no input devices
Hi,
On 29 December 2014 at 00:03, Peter Hutterer
wrote:
> On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
> > The reason for not having any input devices could actually be that there
> > are no input devices attached, imagine that. Mention that cause in the
> > warning and no long
On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
> The reason for not having any input devices could actually be that there
> are no input devices attached, imagine that. Mention that cause in the
> warning and no longer return an error.
>
> This fixes starting weston on boards with
The reason for not having any input devices could actually be that there
are no input devices attached, imagine that. Mention that cause in the
warning and no longer return an error.
This fixes starting weston on boards with no input devices attached.
Signed-off-by: Sjoerd Simons
---
src/libinp
13 matches
Mail list logo
