On Thu, Oct 24, 2013 at 12:33 PM, Jonas Ådahl wrote:
> On Wed, Oct 23, 2013 at 06:08:29PM -0500, Jason Ekstrand wrote:
> > Jonas,
> > Thanks for the review!
> >
> > On Wed, Oct 23, 2013 at 3:56 PM, Jonas Ådahl wrote:
> >
> > > Hi,
> > >
> > > Using this protocol, how would the fullscreen shell c
On Wed, Oct 23, 2013 at 06:08:29PM -0500, Jason Ekstrand wrote:
> Jonas,
> Thanks for the review!
>
> On Wed, Oct 23, 2013 at 3:56 PM, Jonas Ådahl wrote:
>
> > Hi,
> >
> > Using this protocol, how would the fullscreen shell client turn on and
> > off outputs? I can see how clone, next-to and mod
Jonas,
Thanks for the review!
On Wed, Oct 23, 2013 at 3:56 PM, Jonas Ådahl wrote:
> Hi,
>
> Using this protocol, how would the fullscreen shell client turn on and
> off outputs? I can see how clone, next-to and modeset by controlling
> what surface is presented and what fullscreen method is used
Hi,
Using this protocol, how would the fullscreen shell client turn on and
off outputs? I can see how clone, next-to and modeset by controlling
what surface is presented and what fullscreen method is used, but that
is not enough for turning an output off, isn't it?
Another question is synchronisi
---
protocol/fullscreen-shell.xml | 44 +++
1 file changed, 44 insertions(+)
create mode 100644 protocol/fullscreen-shell.xml
diff --git a/protocol/fullscreen-shell.xml b/protocol/fullscreen-shell.xml
new file mode 100644
index 000..b696828
--- /dev/nu
