On segunda-feira, 30 de dezembro de 2013 17:09:16, Carsten Haitzler wrote: > this will require some negotiation before the first buffer is rendered. ie > surface created but not SHOWN... then ask wayland "given this surface, if i > showed it, should i draw frames or not?". this kind of negotiation will be > needed for many other things - like requesting what possible screen it may > end up on - or what profile to use. imagine a phone WITH a desktop monitor > attached. does the app display on the desktop monitor in "desktop mode" > with frames etc. and work with kbd+mouse, or does it display on the mobile > screen with no mouse and fill the screen etc.?
That negotiation is part of the xdg_shell extension to Wayland. We're not using it in Tizen. If the compositor only supports wl_shell, then the toolkit decides whether it should show anything or not, opting to showing something in case of doubt. You should probably make it a system-wide or compile-time setting. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
