Patch updated, made against v7.4.1345. With this patch, I addressed the cursor issue, aiming at smooth cursor draw and low cpu usage.
Hopefully, this resolves all the known issues since the first patch was posted, and eventually allows us to go further to address other unknown issues. If you find an issue, it would be very helpful if you could report it with the result of `vim -g -u NONE`, just like other bug reports. 2016-02-18 1:27 GMT+09:00 Marius Gedminas <[email protected]>: > One curious thing: when I press Ctrl-L to redraw (especially if I hold > it down to cause continuous redraws), the vim window flashes white > before being redrawn. I'd hope that with GTK+'s double-buffering only > the finished image would be actually shown on screen? IIUC, the buffering starts when GTK+ calls a draw signal handler and finishes when the handler returns, so that the whole result of draw operations that were carried out in the handler will appear on the window in one shot. But that's a > quality of implementation issue, not a bug, and perhaps too difficult to > do right with vim's generic architecture? > So, if the redraws caused by Ctrl-L happened within the handler, the buffering could prevent the flushes... Best regards, Kazunobu Kuriyama > Regards, > Marius Gedminas > -- > In fact, liking [C++] is a strong indicator that you're not an expert in > it. > -- ssylvan on reddit > -- -- 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.
gtk3-v7.4.1345.patch.gz
Description: GNU Zip compressed data
