On Wed, 4 May 2016 17:44:51 +0200 Alberto Salvia Novella <[email protected]> wrote:
> As a result of the conversation had at > (https://developer.blender.org/T48292) Hi, too bad the discussion does not explain why you need the ppi, or what it would be used for. There are many uses for ppi that people think are proper, but fall apart very quickly in practice. > I would like to propose having a standard way of advertising Pixels Per > Inch, so applications can know its value independently of the desktop > environment in use. Seems like this would call for lots of standard things: - creating a representation of an output - signalling which output a window is showing on, and updating it dynamically as the window moves and outputs are plugged in and out - delivering output ppi every time it changes permanently (video mode change) Assuming you had all that, what will you then do, when your window is shown on more than one output with differing ppis? All this assuming the issues Jasper mentioned were already solved. Or, how would a DE know which ppi it needs to advertise at a time? Should there only one ppi per window at a time? Thanks, pq
pgpnGHfN6UNvG.pgp
Description: OpenPGP digital signature
_______________________________________________ xdg mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/xdg
