I have added to my MGRX Wayland videodriver (mgrx.fgrim.com) support for the
XDG_decoration protocol to have server side window decorations.
After doing the wayland-scanner magic to generate the .h include and the
.c glue code
Adding the include:
#include "xdg-decoration-client-protocol.h
On quarta-feira, 3 de abril de 2013 12.43.35, Kristian Høgsberg wrote:
> > But the client may still want to popup a grabbing window (e.g. system-tray
> > menu) in response to other event (e.g. dbus event) indirectly caused
> > (handler in another process) by the user input.
>
> I can't think of any
On Wed, Apr 3, 2013 at 1:18 PM, Daniel Stone wrote:
> Hi,
>
> On 3 April 2013 18:01, Yichao Yu wrote:
> > Yes I am talking about menu not notification (sorry the name is status
> > notifier[1] instead of status notification), which is the system tray
> > protocol.
>
> Ah OK, I see. In this case
Hi,
On 3 April 2013 18:01, Yichao Yu wrote:
> Yes I am talking about menu not notification (sorry the name is status
> notifier[1] instead of status notification), which is the system tray
> protocol.
Ah OK, I see. In this case though, there's still a user input event
which triggers it, so I do
On Wed, Apr 3, 2013 at 12:56 PM, Daniel Stone wrote:
> Hi Yichao,
>
> On 3 April 2013 17:50, Yichao Yu wrote:
> > On Wed, Apr 3, 2013 at 12:43 PM, Kristian Høgsberg
> > wrote:
> >> I can't think of anything that does this in any desktop environment
> >> I've ever seen. If as usecase for this c
Hi Yichao,
On 3 April 2013 17:50, Yichao Yu wrote:
> On Wed, Apr 3, 2013 at 12:43 PM, Kristian Høgsberg
> wrote:
>> I can't think of anything that does this in any desktop environment
>> I've ever seen. If as usecase for this comes up we can certainly add
>> it, or any desktop environment can d
On Wed, Apr 3, 2013 at 12:43 PM, Kristian Høgsberg wrote:
> On Wed, Apr 03, 2013 at 12:04:46PM -0400, Yichao Yu wrote:
> > On Wed, Apr 3, 2013 at 11:16 AM, Kristian Høgsberg >wrote:
> >
> > > On Wed, Apr 3, 2013 at 10:59 AM, Yichao Yu wrote:
> > > >
> > > >
> > > >
> > > > On Wed, Apr 3, 2013 at
On Wed, Apr 03, 2013 at 12:04:46PM -0400, Yichao Yu wrote:
> On Wed, Apr 3, 2013 at 11:16 AM, Kristian Høgsberg wrote:
>
> > On Wed, Apr 3, 2013 at 10:59 AM, Yichao Yu wrote:
> > >
> > >
> > >
> > > On Wed, Apr 3, 2013 at 12:00 AM, Daniel Stone
> > wrote:
> > >>
> > >> Hi,
> > >>
> > >> On 3 Apr
On Wed, Apr 3, 2013 at 11:16 AM, Kristian Høgsberg wrote:
> On Wed, Apr 3, 2013 at 10:59 AM, Yichao Yu wrote:
> >
> >
> >
> > On Wed, Apr 3, 2013 at 12:00 AM, Daniel Stone
> wrote:
> >>
> >> Hi,
> >>
> >> On 3 April 2013 03:09, Kristian Høgsberg wrote:
> >> > On Sat, Mar 30, 2013 at 01:31:34AM
On Wed, Apr 3, 2013 at 10:59 AM, Yichao Yu wrote:
>
>
>
> On Wed, Apr 3, 2013 at 12:00 AM, Daniel Stone wrote:
>>
>> Hi,
>>
>> On 3 April 2013 03:09, Kristian Høgsberg wrote:
>> > On Sat, Mar 30, 2013 at 01:31:34AM -0400, Matthias Clasen wrote:
>> >> - It looks like I can't trigger a popup from
On Wed, Apr 3, 2013 at 12:00 AM, Daniel Stone wrote:
> Hi,
>
> On 3 April 2013 03:09, Kristian Høgsberg wrote:
> > On Sat, Mar 30, 2013 at 01:31:34AM -0400, Matthias Clasen wrote:
> >> - It looks like I can't trigger a popup from a key or touch event,
> >> because set_popup requires a serial tha
Hi,
On 3 April 2013 03:09, Kristian Høgsberg wrote:
> On Sat, Mar 30, 2013 at 01:31:34AM -0400, Matthias Clasen wrote:
>> - It looks like I can't trigger a popup from a key or touch event,
>> because set_popup requires a serial that corresponds to an implicit
>> pointer grab. That is sad, I like
On Sat, Mar 30, 2013 at 01:31:34AM -0400, Matthias Clasen wrote:
> Here are a few questions/observations I had while studying the protocol docs:
Most of these have been covered in responses, but let me sum up.
> - The use of serials in events seems a bit inconsistent. Most
> wl_pointer events hav
On Sat, Mar 30, 2013 at 06:17:30PM -0700, Thiago Macieira wrote:
> On sábado, 30 de março de 2013 17.52.33, Nick Kisialiou wrote:
> > What about "long int" type to store the time stamps? Even in microseconds
> > it will take longer than 100 years to overflow 2^63.
>
> That requires changing the pr
On Sat, Mar 30, 2013 at 8:44 PM, Daniel Stone wrote:
> Hi,
>
> On 30 March 2013 16:55, Thiago Macieira wrote:
>>
>> On sábado, 30 de março de 2013 09.34.24, Matthias Clasen wrote:
>> > > Monotonic (ideally) time in an undefined domain, i.e. they're only
>> > > meaningful on relation to each other
Hi,
On 30 March 2013 16:55, Thiago Macieira wrote:
> On sábado, 30 de março de 2013 09.34.24, Matthias Clasen wrote:
> > > Monotonic (ideally) time in an undefined domain, i.e. they're only
> > > meaningful on relation to each other.
> >
> > What can you do with them ? For the use case that Giul
On sábado, 30 de março de 2013 17.52.33, Nick Kisialiou wrote:
> What about "long int" type to store the time stamps? Even in microseconds
> it will take longer than 100 years to overflow 2^63.
That requires changing the protocol.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Arch
What about "long int" type to store the time stamps? Even in microseconds
it will take longer than 100 years to overflow 2^63.
NK
On Sat, Mar 30, 2013 at 9:55 AM, Thiago Macieira
wrote:
> On sábado, 30 de março de 2013 09.34.24, Matthias Clasen wrote:
> > >> - Various input events have a time f
On sábado, 30 de março de 2013 09.34.24, Matthias Clasen wrote:
> >> - Various input events have a time field. The spec doesn't really say
> >> anything about this. What is it good for, and what units are these -
> >> monotonic time ?
> >
> > Monotonic (ideally) time in an undefined domain, i.e. th
Hi,
On 30 March 2013 13:34, Matthias Clasen wrote:
> On Sat, Mar 30, 2013 at 7:56 AM, Daniel Stone wrote:
>
>> - Various input events have a time field. The spec doesn't really say
>>> anything about this. What is it good for, and what units are these -
>>> monotonic time ?
>>>
>>
>> Monotonic (
On Sat, Mar 30, 2013 at 7:56 AM, Daniel Stone wrote:
>
>
>
>> - Various input events have a time field. The spec doesn't really say
>> anything about this. What is it good for, and what units are these -
>> monotonic time ?
>>
>
> Monotonic (ideally) time in an undefined domain, i.e. they're only
Hi,
On 30 March 2013 05:31, Matthias Clasen wrote:
> Here are a few questions/observations I had while studying the protocol
> docs:
>
> - The use of serials in events seems a bit inconsistent. Most
> wl_pointer events have serials, but axis doesn't. wl_keyboard
> enter/leave events do. wl_data_
2013/3/30 Matthias Clasen
> Here are a few questions/observations I had while studying the protocol
> docs:
>
> - The use of serials in events seems a bit inconsistent. Most
> wl_pointer events have serials, but axis doesn't. wl_keyboard
> enter/leave events do. wl_data_offer.enter does, but the
Here are a few questions/observations I had while studying the protocol docs:
- The use of serials in events seems a bit inconsistent. Most
wl_pointer events have serials, but axis doesn't. wl_keyboard
enter/leave events do. wl_data_offer.enter does, but the corresponding
leave/motion events don't
On Mon, Feb 18, 2013 at 10:35:55PM +0100, Peter Hultqvist wrote:
> I've been reading the
> http://wayland.freedesktop.org/docs/html/sect-Protocol-Wire-Format.html
> and done some testing with the wayland socket.
>
> From the docs I got the package sender object id, packet size and opcode.
> I also
I've been reading the
http://wayland.freedesktop.org/docs/html/sect-Protocol-Wire-Format.html
and done some testing with the wayland socket.
>From the docs I got the package sender object id, packet size and opcode.
I also understand the argument formats.
>From looking at the initial packets sent
26 matches
Mail list logo
