On Friday, June 19, 2015 at 5:37:32 PM UTC-3, Ian Halliday wrote: > You're right that something strange was up. I am running a newer build of > Windows 10 now and I cannot get that wonky fat non-client area to show up > anymore (except when maximized as expected). > > > However, now I am attached to the non-clientedge look. > > > Here's a screenshot with and without the clientedge on the build of Win10 > that I am running now: http://imgur.com/apjJ9Vs > > > Perhaps WS_EX_CLIENTEDGE should be specified only for versions of windows > less than 10? or less than 8? 7? > > > What do you think? Do you like the look with or without? > > > On Sun, Jun 7, 2015 at 8:46 AM, Bram Moolenaar <[email protected]> wrote: > > > > > Ian Halliday wrote: > > > > > Hello vim-dev! > > > > > > My name is Ian Halliday, this is my first time sending mail to > > > [email protected]. Please be kind to me :) > > > > > > I humbly would like to submit a patch to vim to remove the WS_EX_CLIENTEDGE > > > client frame border so that gVim looks super sexy smooth in Windows 10 (and > > > much less antiquated in Windows Vista/7/8/8.1). > > > > > > Attached is the simple patch. I have tested this briefly on Windows 7, > > > 8.1, and 10 and found no glaring issues. This patch also seems to fix a > > > strange dead-space margin issue on Windows 10. > > > > > > To see screenshots of what this looks like please take a look at this imgur > > > album: http://imgur.com/a/lbzEA > > > > > > > > > I considered versioning this or otherwise controlling it by trying to check > > > to see if a classic theme was applied but I decided doing so was more > > > complicated than it was worth. Particularly since even with a classic > > > theme this gVim does not look bad at all with this change (see imgur Win7 > > > with classic theme screenshot). > > > > > > Since Windows XP is no longer supported and Microsoft will be pushing for > > > everyone to upgrade to Windows 10 later this year I figure it is not worth > > > the trouble of trying to allow users to go back to the old WS_EX_CLIENTEDGE > > > look. > > > > > > This is my take though. I am brand new to the vim dev community and > > > certainly would like to hear other opinions and feedback. > > > > > > Let me know what y'all think. > > > > Any reactions? To me it looks like Windows 10 does something strange. > > Is removing WS_EX_CLIENTEDGE the only option? > > > > -- > > From "know your smileys": > > !-| I-am-a-Cylon-Centurian-with-one-red-eye-bouncing-back-and-forth > > > > /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ > > /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > > \\\ an exciting new programming language -- http://www.Zimbu.org /// > > \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
Hi, after patch 7.4.930 when using a maximized screen on Windows 10 I can still see the white border with a dark colorscheme (for example blue) and `set guioptions=ac`: https://cloud.githubusercontent.com/assets/2583971/11301200/e6159f70-8f73-11e5-9ee1-e7bf825f0894.png Is this the expected behavior or the white border should disappear altogether? When the window is not maximized, there is indeed no border: https://cloud.githubusercontent.com/assets/2583971/11301199 /e6100f24-8f73-11e5-9ab8-604239d75d47.png Thanks for any feedback! -- -- 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.
