[Beepmp-users] DoubleSize removal

[Chong K. X. <des...@ph...>]

Hi.

I answered this question in the forum. It's now gone so I'll reiterate
the reason for this decision here. The short reason is that the code
used to support doublesize is clunky and doesn't work correctly with
window snapping and shading. Making doublesize a compile time option
solves the second issue but compound the first.=20

Also, we didn't think it was used often enough to keep the maintenance
overhead and could afford to drop it to make the window management and
rendering code easier to work with.=20

Someone pointed out that some laptop TFT displays run at extremely high
native resolutions (as in DPI, not screen dimension in pixels) which are
fixed. We had clearly overlooked this.

However, if anyone writes a clean replacement for doublesize (or even
better, for an arbitrary scale), we'll put it right back in.

> Message: 1
> Date: Tue, 8 Mar 2005 19:52:51 +0100
> From: Mads Martin Joergensen <mm...@mm...>
> To: bee...@li...
> Subject: [Beepmp-users] DoubleSize removed ... why?
>=20
> Hey BMP users,
>=20
> I've just recently started using this nice xmms replacement. Why is it
> that the DoubleSize option was removed? Wouldn't it have been enough to
> make it a compiletime option?

--=20
Chong Kai Xiong (Descender)

GPG public key: 1024D/83EC297C
Key fingerprint =3D 51D6 1C5F 36C9 4428 6933  5239 6A45 502B 83EC 297C