On 11 May 2011 20:25, Bill Spitzak spit...@gmail.com wrote:
Michal Suchanek wrote:
Moves and resizes implemented in the client can't work well.
Any resize solution that does not allow an atomic on-screen update of a
window to it's new size, with the resized decorations and contents, is
microcai wrote:
They can't care how big a windows is in the pixel, but in the inch.
People should have different monitors with different DPI. Windows should
stay same size regardless the DPI.
Force DPI==96 on every monitor is a stupid idea, and we should avoid it
on the protocol side.
The
On 12 May 2011 19:47, Bill Spitzak spit...@gmail.com wrote:
microcai wrote:
They can't care how big a windows is in the pixel, but in the inch.
People should have different monitors with different DPI. Windows should
stay same size regardless the DPI.
Force DPI==96 on every monitor is a
Considering the changes made in the latest version of EGL, released on
April 6, I'd like to point out that OpenGL-proper is now one of the
official EGL client APIs. Revisions to the FAQ, anyone?
http://www.khronos.org/registry/egl/
___
wayland-devel
mccrocai wrote:
That's not true.
DPI is not only used by font size, but also by image size and ther
things
You don't want you 300DPI screen display *tiny tiny font*, will you?
By designing the protocol *DPI aware*, and force the application deal
with the DPI natively, we get better user
I see no changes regarding client API's in the updated EGL spec.
OpenGL was already an offical Client API before, and indeed we're
using that for the
wayland-demos clients, since cairo supported only opengl, not gles2,
until recently.
The FAQ doesnt need to be updated, nothing in there says
