On 2018-04-16 10:36 AM, Pekka Paalanen wrote:
> that's seems contradictory to what you replied here:
You're right, it does.
> > You could do this but it would be exceedingly silly of you considering
> > that the other xdg_output requests furnish the client with layout
> > information anyway.
>
On Fri, 13 Apr 2018 16:16:34 +0200
Jonas Ådahl wrote:
> On Fri, Apr 13, 2018 at 10:05:39AM -0400, Drew DeVault wrote:
> > On 2018-04-13 4:02 PM, Jonas Ådahl wrote:
> > >
> > > > - Xwayland can name the X11 outputs based on their genuine names rather
> > > > than
On Sat, 14 Apr 2018 10:08:35 -0400
Drew DeVault wrote:
> On 2018-04-13 4:33 PM, Pekka Paalanen wrote:
> > The other events have more precise wording here, allowing the event to
> > be sent again if the information changes.
>
> This is deliberate - I don't think the name
On 2018-04-13 4:33 PM, Pekka Paalanen wrote:
> The other events have more precise wording here, allowing the event to
> be sent again if the information changes.
This is deliberate - I don't think the name should change. I'll write it
up explicitly.
On 2018-04-13 4:16 PM, Jonas Ådahl wrote:
> If that is the case, I'd rather we introduced data that has actual
> meaning, like something similar to "connector" (even though connector is
> the wrong thing here since an "xdg_output" might not have one, maybe,
> something that doesn't identify the
On Fri, Apr 13, 2018 at 10:05:39AM -0400, Drew DeVault wrote:
> On 2018-04-13 4:02 PM, Jonas Ådahl wrote:
> > > - A client using fullscreen-shell could offer the user a list of outputs
> > > by name to fullscreen on
> >
> > I think this would need something different, an actual "human
On 2018-04-13 4:02 PM, Jonas Ådahl wrote:
> > - A client using fullscreen-shell could offer the user a list of outputs
> > by name to fullscreen on
>
> I think this would need something different, an actual "human friendly"
> name, like 'Dell 24"' or 'Builtin monitor'. If you'd have strings
On Wed, Apr 11, 2018 at 08:35:34AM -0400, Drew DeVault wrote:
> On 2018-04-11 9:17 AM, Philipp Kerling wrote:
> > maybe I missed it at some point in the discussion (sorry if that is the
> > case), but what is your use case for the "name?" What are clients
> > expected to use it for?
>
> This is
On Tue, 10 Apr 2018 20:27:55 -0400
Drew DeVault wrote:
> Signed-off-by: Drew DeVault
> Reviewed-by: Simon Ser
> ---
> This version clarifies the uniqueness constraint, mapping of names to
> wl_outputs, and persistence between sessions.
>
>
More good questions.
On 2018-04-11 11:02 AM, Pekka Paalanen wrote:
> There is still the corner-case of: can removing wl_output global A
> cause the name for wl_output global B to change, but I suppose that
> falls to common sense to not do so strange things.
I suppose I can add a note about this
On 2018-04-11 9:17 AM, Philipp Kerling wrote:
> maybe I missed it at some point in the discussion (sorry if that is the
> case), but what is your use case for the "name?" What are clients
> expected to use it for?
This is ideally combined with other protocols. Some example use-cases:
- A client
On Tue, 10 Apr 2018 20:27:55 -0400
Drew DeVault wrote:
> Signed-off-by: Drew DeVault
> Reviewed-by: Simon Ser
> ---
> This version clarifies the uniqueness constraint, mapping of names to
> wl_outputs, and persistence between sessions.
>
>
Hi,
maybe I missed it at some point in the discussion (sorry if that is the
case), but what is your use case for the "name?" What are clients
expected to use it for?
The description mentions "similar behaviors", but it is unclear to me
what you are referring to.
Regards,
Philipp
2018-04-10 (火)
Signed-off-by: Drew DeVault
Reviewed-by: Simon Ser
---
This version clarifies the uniqueness constraint, mapping of names to
wl_outputs, and persistence between sessions.
.../xdg-output/xdg-output-unstable-v1.xml | 19 ++-
1 file
14 matches
Mail list logo