Thank you all for the feedbacks. It looks a major outstanding issue is the “visual quarks”.
Although the patch attached to this email doesn’t directly address the issue, now the patched source should be compiled without any warnings from GTK+ 3. Thanks to that, I hope we can concentrate on the visual quarks, not being distracted by other port-to-GTK+ 3 issues. To Marius Gedminas, Thank you for your report with pictures. They are very helpful. Although I understand the problems, I can’t reproduce your first five issues: 1. There's a strange black area around the window: http://imgur.com/ZGzwLyV 2. It's even worse if I start vim as gvim instead of using :gui: http://imgur.com/UuMbfaS 3. Try opening a text file, then use :help, then close the :help file. Bits of help text will show through the actual text you're editing: http://imgur.com/a/YCiow 4. In the status line: old text is not cleared away when you press : and start entering a new command. 5. Scrolling with PageUp doesn’t clears the screen correctly before drawing. So, frankly speaking, I have no idea on how to fix them in a logical way. In the new patch, I elaborated scroll and window clear functions a little bit. So, I’d be happy if you would try it and report the result here. That said, the sixth issue: 6. The missing scrollbar in the :help split -- it shows up when you switch to it, but is just a black rectangle initially. looks crucial to me. I’m feeling fixing that fixes the rest of the issue (this view may be too optimistic :-) ). I’m thinking of looking into our custom widget GtkForm in detail in hope of fixing the sixth isssue. Note that the attached patch was made against 7.4.1190, not against my previous patch. Best regards, Kazunobu Kuriyama 2016-01-27 10:14 GMT+09:00 SungHyun Nam <[email protected]>: > 2016-01-26 오후 8:04에 Christian Brabandt 이(가) 쓴 글: > > Hi Marius! > > > > I can confirm the redraw glitches. Those look a little bit like issue > > #91 (https://github.com/vim/vim/issues/91). Yes, if I modify the source > > and force some additional redraws, it works. However as noted in the > > issue, this is not the correct solution, since this will make redrawing > > a lot slower. > > When I noticed redraw problem with vim-gtk2, I found that issue #91. > I don't remember details but your patch didn't help me. > But, from the issue #91, I found about the '--sync' option. > And because the option also worked for me, I used this alias 'g="gvim > --sync"' nowadays. > > Yesterday, I tested the gtk3 with the 'g' alias command. > Now, I re-tested vim-gtk2 and vim-gtk3 without '--sync' option. > And they shows a same redraw issue. > So that, it seems --sync option does not work for gtk3. > > Thanks, > namsh > > -- > -- > 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. > -- -- 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-update00.patch.gz
Description: GNU Zip compressed data
