Re: [RFC krh/wayland/next 2/2] protocol: try to clarify wl_buffer doc

2012-10-16 Thread Pekka Paalanen
On Tue, 16 Oct 2012 11:05:44 -0400 Kristian Høgsberg wrote: > On Fri, Oct 12, 2012 at 02:29:01PM +0300, Pekka Paalanen wrote: > > Fix few typos in wl_buffer description. > > > > Mention backing storage in wl_buffer.destroy. > > > > Try to clarify the wl_buffer.release semantics by not explainin

Re: [RFC krh/wayland/next 2/2] protocol: try to clarify wl_buffer doc

2012-10-16 Thread Kristian Høgsberg
On Fri, Oct 12, 2012 at 02:29:01PM +0300, Pekka Paalanen wrote: > Fix few typos in wl_buffer description. > > Mention backing storage in wl_buffer.destroy. > > Try to clarify the wl_buffer.release semantics by not explaining what > *might* happen. It is important to not suggest, that if release d

Re: [RFC krh/wayland/next 2/2] protocol: try to clarify wl_buffer doc

2012-10-16 Thread Pekka Paalanen
On Fri, 12 Oct 2012 14:29:01 +0300 Pekka Paalanen wrote: > Fix few typos in wl_buffer description. > > Mention backing storage in wl_buffer.destroy. > > Try to clarify the wl_buffer.release semantics by not explaining what > *might* happen. It is important to not suggest, that if release does n

[RFC krh/wayland/next 2/2] protocol: try to clarify wl_buffer doc

2012-10-12 Thread Pekka Paalanen
Fix few typos in wl_buffer description. Mention backing storage in wl_buffer.destroy. Try to clarify the wl_buffer.release semantics by not explaining what *might* happen. It is important to not suggest, that if release does not come before frame callback, it will not come before attaching a new