On Sat, Sep 08, 2012 at 12:08:06AM -0700, Henri Verbeet wrote:
> On 8 September 2012 01:22, Andy Ritger wrote:
> > In any case, there is an enthusiast community around immersive gaming; e.g.,
> >
> > http://www.nvidia.com/object/3d-vision-surround-technology.html
> &
On Thu, Sep 06, 2012 at 01:05:42AM -0700, Henri Verbeet wrote:
> On 5 September 2012 22:45, Andy Ritger wrote:
> > On Wed, Sep 05, 2012 at 11:26:23AM -0700, Henri Verbeet wrote:
> >> From Wine's point of view, we'd just get a bunch of extra code to maintain
>
On Wed, Sep 05, 2012 at 11:26:23AM -0700, Henri Verbeet wrote:
> On 5 September 2012 18:52, Andy Ritger wrote:
> > At first glance, I agree that would be easier for applications, but that
> > approach has some drawbacks:
> >
> > * lies to the user/application about what
Thanks, Henri.
On Wed, Sep 05, 2012 at 01:34:47AM -0700, Henri Verbeet wrote:
> On 5 September 2012 08:07, Andy Ritger wrote:
> > Questions:
> >
> > * Looking at dlls/winex11.drv/xrandr.c, the first RandR CRTC/output's
> > modelist is used to populate Wine&#x
figuration)
they want on each monitor, and then RandR 1.1 chooses the MetaMode.
Would it make sense for the user to be able to specify to Wine the
RandR configuration (spanning all of the RandR outputs on the X screen)?
I guess that depends on what runtime configuration mechanisms are
possible.
I'm curious what you guys think, before I code up any patches to propose.
Thanks,
- Andy Ritger
