Hi David, 2017/12/12 Tue 23:46:20 UTC+9 Ken Takata wrote: > Hi, > > 2017/12/12 Tue 13:44:19 UTC+9 David Kotchan wrote: > > On Monday, December 11, 2017 at 7:06:37 AM UTC-8, Ken Takata wrote: > > > > > I'm also aware the cursor behavior. > > > I have updated the "optimize-directx" branch in the vim-jp/vim repository. > > > gui_mch_flush() was called unnecessarily several times, and it caused the > > > behavior. > > > I think it is now fixed, but need more tests. > > > > Hi Ken > > > > Thanks for your work! However, I find that pulling code from the latest > > branch (https://github.com/vim-jp/) does not help my problem. I tried > > compiling it (under VS2017) with several different options: > > Hmm, did you use the commit 0e7d0764cc24d7563a9eb8c97f3020274a52d09c on > the optimize-directx branch? > I still have no idea why it becomes slow on your environment. > > Maybe we need to measure where the slow part is. > Or do we need to add an option to back to the old behavior?
I created an experimental branch 'gdi-cursor' in the vim-jp/vim repository. This adds 'gdicursor' suboption to the 'rop' option. If you do `:set rop=type:directx,gdicursor:1`, the old drawing method (which was used before 8.0.1369) will be used. Could you try this and check if the speed is same as before 8.0.1369? Regards, Ken Takata -- -- 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/d/optout.
