On Fri, Apr 29, 2011 at 04:58:24PM -0400, Kristian Høgsberg wrote: > Apps shouldn't generally change the *default* resolution. Games and > such may want to show their window at the native resolution and that's > part of the fullscreen plan: > > > http://lists.freedesktop.org/archives/wayland-devel/2010-November/000117.html >
Ah, that does make sense? > Of course, the DE config tool will want to be able to change the > default mode and placement of monitors. In that case we're talking > about a specific DE with it's own display configuration tool, and > perhaps the tool can just update the underlying config (GConf or so) > and the compositor picks up the change from there. As a first step > I'd rather just add the extra info to wl_output (list of available > modes, refresh rates, sub pixel layout, connector name etc), and punt > on how to change it for now. > Would it make sense for the demo compositor to grow some sort of config backend then? Obviously it wouldn't be directly useful to anyone else but it would at least let us test the functionality that should be exposed "elsewhere." --CJD _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
