Loading ...
Sorry, an error occurred while loading the content.

Re: using DirectX/DirectWrite for rendering text.

Expand Messages
  • Mike Williams
    ... Looking good here, although I only use it for latin character sets. Makes Source Code Pro font usable but has little effect on most Windows fonts since
    Message 1 of 58 , Mar 29, 2013
    • 0 Attachment
      On 26/03/2013 12:20, Taro MURAOKA wrote:
      > I have fixed a problem which ":set<CR>" is crash.
      >
      >
      > Best.
      >

      Looking good here, although I only use it for latin character sets.
      Makes Source Code Pro font usable but has little effect on most Windows
      fonts since they are designed for the GDI renderer's behaviour.

      One thing that is not controllable is the type of anti-aliasing
      performed - there needs to be a call to SetTextAntialiasMode() to
      specify if grayscale or ClearType anti-aliasing should be done. Perhaps
      this could be option aamode taking 0-3 as
      perhttp://msdn.microsoft.com/en-gb/library/windows/desktop/dd368170%28v=vs.85%29.aspx
      To avoid confusion how about renaming the mode option as geom (since
      it relates to geometry of rgb components of a pixel) and geom as
      positioning as it affects character layout.

      It may be useful to document at least the modes.

      For geom (what was mode):
      0 - RGB components coincident (CRT displays)
      1 - Pixel components in RGB order (most LCD displays)
      2 - Pixel components in BGR order

      For positioning (what was geom):
      0 - Automatic rendering based on font and size.
      1 - No anti-aliasing.
      2 - Horizontal anti-aliasing with GDI Cleartype character positioning.
      3 - Horizontal anti-aliasing with improved GDI Cleartype positioning.
      4 - Horizontal anti-aliasing with natural positioning.
      5 - Horizontal and vertical anti-aliasing with natural positioning.
      6 - Use font outlines directly

      For aamode (if implemented):
      0 - System default.
      1 - ClearType anti-aliasing.
      2 - Grayscale anti-aliasing.
      3 - No anti-aliasing.

      HTH - TTFN

      Mike
      --
      Confession is good for the soul, but bad for your career.

      --
      --
      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 vim_dev+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Peter Prohaska
      Pasting text produces inconstisten screen state. Looks like a mixture of monospaced and proportional font. Resetting rop to empty fixes the problem--and
      Message 58 of 58 , Aug 20 6:26 AM
      • 0 Attachment
        Pasting text produces inconstisten screen state. Looks like a mixture of
        monospaced and proportional font. Resetting rop to empty fixes the
        problem--and reintroduces the missing char glyphs.

        Attached is screenshot with the lines showing
        1) state right after paste (cursor was aligned above the 2nd-row tsu
        2) state after moving one character to the left ("h")
        3) state after moving left till column 1 ("hhh")

        Yank and paste, scroll off screen and back in, all produce state (1).
        Selections mark the full width as in state (3). Moving the cursor over a
        position triggers the update as seen in state (2).

        Test settings:
        rop=type:directx
        guifont=DejaVu_Sans_Mono:h10:cANSI

        Test Build: VC10; Win8; nmake -f Make_mvc.mak GUI=yes DIRECTX=yes


        Aside:
        It should definitely make it into vim.

        Skimmed through the code. Don't know much about the specific job. Looks
        solid enough. Patch currelty produces a rejected hunk against hg due to the
        addition of 'regexpengine' option.

        My user experience: Try a few dozen fonts, find a hadfull that works
        acceptable. Pre patch: rest is unusable. Post patch: rest works good or
        great. Editing terminological datasets often, i hearty recommend this
        pain-killer (or a different OS).

        Regards,
        Peter.

        --
        --
        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 vim_dev+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
      Your message has been successfully submitted and would be delivered to recipients shortly.