On Sun, 20 Oct 2013, Christophe wrote:
----- Rodolfo García Peñas (kix) <[email protected]> a écrit :
[...]

The second problem is the icon images. The icon should be screen independent, but sometimes is not possible.

My personal feeling is that they *have* to be screen dependant. Icons are meant to be displayed on a screen, so they need to be. Keeping a screen independent version looks like a memory overuse for me (and images are already the biggest memory consuming things)

I had the same feeling about this.

[...]

Without these ideas, is very difficult (IMO impossible) implement XRandR, Multiheader, ... configurations.

I think the problem is not taken for the right angle. It is not the image loading and icon creation that should be split, it is the WScreen information: The legacy X screen info (basically: depth, the infos to convert the image into X specific format) should be separated from physical screen info (as returned by Xinerama and Xrandr, info like size of the screen and the likes).

I agree as I wrote previously. Wasn't the split of some info into the global structure a step into this direction? I think there's some ambiguity in the terms or functions of some objects that needs to be sorted but I don't know where or what exactly.

Regards,
BALATON Zoltan

Reply via email to