On 30/03/2013 15:32, Mike Williams wrote:
On 29/03/2013 12:55, Taro MURAOKA wrote:
I updated the patch which attached. I have changed these:
* Add document which describe enum values.
* Rename "mode" to "renmode".
* Add "taamode" for text antialising mode.
there needs to be a call to SetTextAntialiasMode() to specify if
grayscale or ClearType anti-aliasing should be done.
I have implemented this. But I don't know is it correct or not. If it
is not work as you expected, please check and fix source code and send a
patch.
At the moment I can see no no effect on the rendered output. I don't
know if this is an issue with the implementation or the Windows
documentation. I will investigate further.
There is a bug in gui_mch_set_rendering_options() when setting
param.textAntialiasMode, the test is on dx_taamode instead of dx_flags.
However, fixing this does not result in any changes when changing taamode.
Going deeper into the new code, I wonder if the useGdiNatural param to
CreateGdiCompatibleTextLayout() needs to be conditional on the font
created by vim. VIM creates fonts with PROOF_QUALITY so may not be
producing the best output. Still reading through the code.
Mike
--
The Road to Enlightenment is long and difficult, so bring lots of snacks.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
