.
That means patch "winecfg: Fix overflow in the DPI field at the
Graphics tab for DPI value bigger than 127" is incorrect too.
I think I will write today better patch myself from scratch for this
bug
(after reading some docs about MultiByteToWideChar).
After Austin
"L. Rahyen" <[EMAIL PROTECTED]> wrote:
> This problem was already solved in this patch [1] by Nigel Liang.
> Unfortunately, it wasn't accepted and Nigel didn't tried to ask why it was
> rejected or to resend it.
> I think I will go ahead and resend his patch.
>
> [1] http://www.winehq.org/piper
On Tue, Mar 4, 2008 at 1:52 PM, L. Rahyen <[EMAIL PROTECTED]> wrote:
> Your patch isn't correct. Just try this:
>
> rm -rf ~/.wine
> wineprefixcreate
> winecfg
>
> Go to Graphics tab and set any resolution more than 127 DPI (for
> example,
> 150). Close winecfg. Run it again. N
Your patch isn't correct. Just try this:
rm -rf ~/.wine
wineprefixcreate
winecfg
Go to Graphics tab and set any resolution more than 127 DPI (for
example,
150). Close winecfg. Run it again. Now you have 63 DPI (instead of 150; in
fact anything bigger than 127 DPI will not be di
