On 07/19/2016 07:40 PM, Jonas Ådahl wrote:
> I think as far as API's go, we should use D-Bus API that provides a
> screen record session where the actual video frames are passed using
> pinos. That API shoulda definitely be per monitor to minimize any
> processing done in the compositor process.
On Tue, Jul 19, 2016 at 01:09:15PM -0700, Christian Hergert wrote:
> On 07/19/2016 12:21 PM, Ray Strode wrote:
> > On Tue, Jul 19, 2016 at 11:04 AM Jonas Ådahl wrote:
> >> > 2) Represent each monitor separately, generating one file for each
> > This makes the most sense to me.
On 07/19/2016 12:21 PM, Ray Strode wrote:
> On Tue, Jul 19, 2016 at 11:04 AM Jonas Ådahl wrote:
>> > 2) Represent each monitor separately, generating one file for each
> This makes the most sense to me. Or even only do the active monitor.
>
> Of course for screen recording
hi,
On Tue, Jul 19, 2016 at 11:04 AM Jonas Ådahl wrote:
> 2) Represent each monitor separately, generating one file for each
This makes the most sense to me. Or even only do the active monitor.
Of course for screen recording (versus screenshoting), only doing the
active
On tis, 2016-07-19 at 23:03 +0800, Jonas Ådahl wrote:
> [...]
> Any opinions on in what way we should deal with this? What user
> interface do we want?
>
I always found it weird that taking a screenshot or making a screencast
took the data from both screens and put them together.
I'd suggest
On Tue, 2016-07-19 at 23:03 +0800, Jonas Ådahl wrote:
> Hi,
>
> Over at mutter we've been working towards supporting proper multi DPI
> setups when running GNOME using Wayland. Proper multi DPI means to
> support having multiple monitors where two or more monitors have
> significantly different
Hi,
Over at mutter we've been working towards supporting proper multi DPI
setups when running GNOME using Wayland. Proper multi DPI means to
support having multiple monitors where two or more monitors have
significantly different DPI but applications showing correctly on both
monitors at all