Re: handling unknown messages (pt 2 of TODO)

2011-04-11 Thread Iskren Chernev
2011/4/11 Kristian Høgsberg k...@bitplanet.net On Sun, Apr 10, 2011 at 1:47 PM, Iskren Chernev iskren.cher...@gmail.com wrote: Hello, I think I can do the second point in the TODO file: The message format has to include information about number of fds in the message so we can skip a

Mode setting from application

2011-04-11 Thread Magnus Wendt
Hi, I was just thinking of a use case and wondering if it has been considered in Wayland. A full screen video player would like to match the refresh rate of the display to the refresh rate of the video to get smooth playback. (e.g. XBMC playing a 24Hz movie on your TV.) I was thinking that the

Re: Mode setting from application

2011-04-11 Thread Kristian Høgsberg
On Mon, Apr 11, 2011 at 10:50 AM, Magnus Wendt magnus.we...@gmail.com wrote: Hi, I was just thinking of a use case and wondering if it has been considered in Wayland. A full screen video player would like to match the refresh rate of the display to the refresh rate of the video to get

Re: handling unknown messages (pt 2 of TODO)

2011-04-11 Thread Bill Spitzak
Are you talking about Wayland messages between the client and compositor? I don't understand why you need to identify fd's in unknown message in order to skip them. Isn't there a total length of the message and the fd's are just embedded in this block of bytes? I'm probably missing something