On Wed, Dec 09, 2015 at 08:17:40AM +0100, Martin Graesslin wrote:
> On Wednesday, December 9, 2015 4:19:12 PM CET Peter Hutterer wrote:
> > On Tue, Dec 08, 2015 at 02:12:01PM +0100, Martin Graesslin wrote:
> > > Hi Wayland-developers,
> > >
> > > at KDE we developed a protocol for our framework ki
On Wednesday, December 9, 2015 4:19:12 PM CET Peter Hutterer wrote:
> On Tue, Dec 08, 2015 at 02:12:01PM +0100, Martin Graesslin wrote:
> > Hi Wayland-developers,
> >
> > at KDE we developed a protocol for our framework kidletime [1]. The idea
> > is to notify Wayland clients when a wl_seat has be
On Tuesday, December 8, 2015 2:59:38 PM CET Bryce Harrington wrote:
> On Tue, Dec 08, 2015 at 02:12:01PM +0100, Martin Graesslin wrote:
> > Hi Wayland-developers,
> >
> > at KDE we developed a protocol for our framework kidletime [1]. The idea
> > is to notify Wayland clients when a wl_seat has be
From: Nobuhiko Tanibata
It shows 2 ivi application in a screen at side-by-side. It moves
additinal application more than 2xN to next screen N+1.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 61 +-
1 f
From: Nobuhiko Tanibata
It shows ivi applications in fullscreen per screen like,
The first screen: Application 1,4,5,6
The seconed screen: Application 2,
The third screen: Application 3
Thie mode assigns one application to each screen at first. And remaind
applications more than screens will
It shows ivi applications at screensa randomly.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 39 ++-
1 file changed, 34 insertions(+), 5 deletions(-)
diff --git a/ivi-shell/hmi-controller.c b/ivi-shell/hmi-con
From: Nobuhiko Tanibata
It shows 8 ivi applications in a screen at tiling. It moves additional
application more than 8xN to next screen N+1.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 38 ++
1 file changed,
From: Nobuhiko Tanibata
It shows 2 ivi application in a screen at side-by-side. It moves
additinal application more than 2xN to next screen N+1.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 61 +-
1 f
From: Nobuhiko Tanibata
To locate surfaces of application on multi screens, multi layers are
created baseod on application-layer-id + base-layer-id-offset x N.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 98 +++-
From: Nobuhiko Tanibata
To locate surfaces of application on multi screens, multi layers are
created baseod on application-layer-id + base-layer-id-offset x N.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 98 +++-
From: Nobuhiko Tanibata
A surface ID for layer of background/panel image is set by key: background-id
or panel-id at weston.ini. To support multi screens, it also support offset,
surface-id-offset, to offset the surface ID to next ID for a layer on next
screen.
According to the above key, hmi-co
- get screens from weston core
- provide screens as internel method
- the iviscn is stored in array inverse order in index.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/hmi-controller.c | 60 --
1 file changed, 47 inserti
From: Nobuhiko Tanibata
A layer ID for screen is set by key: base-layer-id at weston.ini. To
support multi screens. It also support offset to offset the layer ID
to next ID for next screen.
For example,
base-layer-id=1000
base-layer-id-offset=1
Layer id for screen 0: 1000
Layer id for scree
A weston_surface is transformed to multi screen coordinate, global
coordinate by matrix:m now.
Additionally, a mask needs to be calucated, taking account into,
- multi screen coordination: a destination rectangle of layer in the
coordination is easily calcurated by adding weston_output.{x,y} in
In single screen, the coordinates of layer local coordinates are the
same as global coordinates. However, to support multi screens, the
layer-local coordinates shall be transformed to multi screen coordinates,
which is global coordinates. The abosolute coordinates of a screen in global
stored in (x
For multi screen support, ivi_layout_screen to be taken account into
property change in commitChanges.
Property change is now done in update_prop so to consider ivi_screen
property for caluculating transform of weston surface, ivi_layout_screen
is added as a parameter of update_prop.
However, up
Hi,
This proposes multi screen support by ivi-shell. This allow user to
manage a
hierarchy; surface, layer, and screen. Current code expects single
screen so
user can not assign a layer to another display by using ivi-layout
interface.
This patch series also updates a reference code of control
On Tue, Dec 08, 2015 at 02:12:01PM +0100, Martin Graesslin wrote:
> Hi Wayland-developers,
>
> at KDE we developed a protocol for our framework kidletime [1]. The idea is
> to
> notify Wayland clients when a wl_seat has been idle for a specified time. We
> use this for example for power managem
From: Nobuhiko Tanibata
Similar with Desktop shell, set activate to weston surface which is
left-clicked by pointer or touched. This is needed to focus it with a seat.
Without this, a feature who gets activated weston surface by using
weston_surface_get_main_surface doesn't work correctly because
On Tue, Dec 08, 2015 at 05:37:52PM -0800, Jason Gerecke wrote:
> On Sun, Dec 6, 2015 at 8:22 PM, Peter Hutterer
> wrote:
> > On Thu, Dec 03, 2015 at 07:57:30PM -0800, Jason Gerecke wrote:
> >> On Wed, Dec 2, 2015 at 5:03 PM, Peter Hutterer
> >> wrote:
> >> > On Wed, Dec 02, 2015 at 04:21:56PM -
On Sun, Dec 6, 2015 at 8:22 PM, Peter Hutterer wrote:
> On Thu, Dec 03, 2015 at 07:57:30PM -0800, Jason Gerecke wrote:
>> On Wed, Dec 2, 2015 at 5:03 PM, Peter Hutterer
>> wrote:
>> > On Wed, Dec 02, 2015 at 04:21:56PM -0800, Jason Gerecke wrote:
>> >> On Tue, Dec 1, 2015 at 5:46 PM, Peter Hutte
libinput 1.1.2 is now available. Four significant bugfixes:
* the 2-finger scroll threshold was reduced to 1mm which significantly
reduces the delay users experienced when scrolling
* BTN_TOOL_* events are not posted as button events anymore. These aren't
button events anyway, they are signals
On Tue, Dec 08, 2015 at 12:08:29PM -0800, Bill Spitzak wrote:
> On Mon, Dec 7, 2015 at 5:11 PM, Peter Hutterer
> wrote:
>
> >
> > +
> > +
> > + Describes the source types for axis events. This indicates to the
> > + client how an axis event was physically generated; a client
On Tue, Dec 08, 2015 at 02:12:01PM +0100, Martin Graesslin wrote:
> Hi Wayland-developers,
>
> at KDE we developed a protocol for our framework kidletime [1]. The idea is
> to
> notify Wayland clients when a wl_seat has been idle for a specified time. We
> use this for example for power managem
On Tue, Dec 08, 2015 at 11:58:20AM -0800, Bill Spitzak wrote:
> What is the plan for using a tablet in "relative" mode? This is pretty
> common if the tablet is smaller than the screen, as many modern ones are.
I would love to hear where you get this information from, because the one
thing we're s
On 08/12/15 12:33 PM, Daniel Stone wrote:
> Hi,
>
> On 6 November 2015 at 21:56, Derek Foreman wrote:
>> Adds support for touch devices to the wayland backend.
>>
>> Signed-off-by: Derek Foreman
>> ---
>> Changes from v1:
>> should now properly handle both fullscreen and windowed case now
>> sho
Hi,
On 6 November 2015 at 21:56, Derek Foreman wrote:
> Adds support for touch devices to the wayland backend.
>
> Signed-off-by: Derek Foreman
> ---
> Changes from v1:
> should now properly handle both fullscreen and windowed case now
> should also now handle touch cancel
Thanks for the fixups
Le 05/12/2015 02:20, Derek Foreman a écrit :
> From: Sjoerd Simons
>
> Currently the fbdev compositor has its own shadow buffer when rendering
> with pixman, causing the following copies to occur:
>
> [pixman shadow buffer] -> [fbdev shadow buffer] -> [fbdev hardware]
>
> As the pixman render a
Hello,
while playing around with the scaler extension on Weston 1.9 I've
encountered some strange behavior I'd like to get some definitive input
for:
I'm using Weston 1.9 under X11 with the NVidia drivers, in case that
matters. My program does the following:
1) have a surface (SA) which
Hi Wayland-developers,
at KDE we developed a protocol for our framework kidletime [1]. The idea is to
notify Wayland clients when a wl_seat has been idle for a specified time. We
use this for example for power management, screen locking etc. But a common
use case is also setting a user as away
If there was a buffer damage request, this should not damage the entire
buffer, since supposedly the client sent the correct damage rectangle. I
think it would be a good idea to enforce this so that clients changing the
transform don't send incorrect damage regions (in particular *no* damage
region
On Mon, 07 Dec 2015 13:29:02 -0500
and...@acorn.pw wrote:
> From the man page for weston-drm:
>
> >Combining multiple graphics devices are not supported yet.
>
> Is there any plan for implementing this or no interest? What would be
> involved in adding support for multiple output devices?
Hi,
32 matches
Mail list logo
