[MPlayer-dev-eng] Re: [PATCH] Automatic monitor aspect for X11

[Alban Bedel]

On Fri, 14 Apr 2006 16:27:57 +0200
Reimar Döffinger <Reimar.Doeffinger at stud.uni-karlsruhe.de> wrote:

> Hi,
> On Fri, Apr 14, 2006 at 04:08:43PM +0200, Alban Bedel wrote:
> > after seeing Reimar patch i looked a bit at how the monitor size can be
> > queried from X11. As i expect it's pretty trivial, here is the
> > (preliminary) patch.
> 
> Unless there are plans to implement it for anything besides X11, I'm
> against the parts in aspect.[c|h].

That doesn't sound very logical to me. I'm pretty sure it should be
possible to implement such thing for win32 and osx and cluttering
such trival stuff under some #ifdef sound quiet lame to me.

> > IMHO it should probably be enabled by default as i expect most ppl have
> > DCC working nowadays, and if not they probably already have the right
> 
> I don't know why, but I once had a monitor that didn't know its own
> size correctly...
> The values weren't enough off to make it look wrong, but it still was
> wrong...
> 
> > size in their config file for other stuff (like displaying postscript,
> > etc). But let's test a bit first :)
> 
> Hmm.. which are the applications that really use this? I am only aware
> of applications using the dpi value, and that has only created headaches
> for me so far - so much that I always make sure that the X server always
> gets passed -dpi 100 (it's really fun when programs really believe it's
> 99 dpi and scale fixed fonts down by 1%).

Well afaiu dpy is computed from the screen size and resolution, so basically
it's the same. And yes some other app use it, for ex. to display ps and pdf
in real size. Also with the advent of vector graphics and scalable fonts
in desktop environements having correct settings (will) become more
important.

Now if you like to incorrectly configure your server (ie set some arbitrary
dpy instead of setting the correct monitor size), that's your problem after
all, here everything is displayed as it should.

> In other words, I just hate features that work "behind the back", esp.
> when I got bitten by them once. So I am against ever making this the
> default..

I don't really care if it's on by default or not, my point was more that it
will work fine for 99% of the user and perhaps bit 1%. As it can be disabled
anyway imho enabling it sound better (assuming it play well with xinerama).

	Albeu