[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: migrating to GitLab
From: |
Han-Wen Nienhuys |
Subject: |
Re: migrating to GitLab |
Date: |
Sun, 10 May 2020 12:08:06 +0200 |
On Sun, May 10, 2020 at 11:57 AM David Kastrup <address@hidden> wrote:
> output-distance: set device properties in batch driver file
>
> This fixes the output quality of the regtest results.
>
> Previously, the code sets a device by doing
>
> (png16m) finddevice
>
> this put a default device on the stack, ignoring the command-line
> arguments. To fix this, specify these settings (HWResolution,
> TextAlphaBits, GraphicsAlphaBits) as arguments to the putdeviceprops
> call.
>
> https://codereview.appspot.com/560020043/
> https://sourceforge.net/p/testlilyissues/issues/5967/
>
> How do you expect that commit you just now pushed to proceed if not via
> Patchy?
I'd push it again, I guess? IIRC I pushed this before reading Jonas
request for comments.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
- Re: migrating to GitLab, (continued)
- Re: migrating to GitLab, Dan Eble, 2020/05/09
- Re: migrating to GitLab, Jonas Hahnfeld, 2020/05/10
- Re: migrating to GitLab, Han-Wen Nienhuys, 2020/05/10
- Re: migrating to GitLab, Jonas Hahnfeld, 2020/05/10
- Re: migrating to GitLab, David Kastrup, 2020/05/10
- Re: migrating to GitLab, Han-Wen Nienhuys, 2020/05/10
- Re: migrating to GitLab, David Kastrup, 2020/05/10
- Re: migrating to GitLab, David Kastrup, 2020/05/10
- Re: migrating to GitLab, David Kastrup, 2020/05/10
- Re: migrating to GitLab, Jonas Hahnfeld, 2020/05/10
- Re: migrating to GitLab,
Han-Wen Nienhuys <=
- Re: migrating to GitLab, David Kastrup, 2020/05/10
- Re: migrating to GitLab, David Kastrup, 2020/05/10
- Re: migrating to GitLab, Jean-Charles Malahieude, 2020/05/10
- Re: migrating to GitLab, Werner LEMBERG, 2020/05/10
- Re: migrating to GitLab, Jonas Hahnfeld, 2020/05/09
README.md (was: migrating to GitLab), Urs Liska, 2020/05/17