Ynglaur

Join Date 05/2006

+11

WindowBlinds 7.9 cuts off half of "End" button

WindowBlinds 7.90 (008 - Windows 8 Edition)

If you snap an MS Office application window to the side of a screen (full height, half-screen width), then the "End" button (top right, red) is only half-displayed. Clicking on the invisible portion does close the window, however.

DxDiag can be found at the link below. Note that I'm running two monitors with different resolutions (1920 x 1080 and 1920 x 1200).

http://pastebin.com/embed_js.php?i=qyCk2FbK

windowblinds

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

ZubaZ

Join Date 11/2001

+917

Every skin or just some?

What version of Office?

Successfully updated karma reason!

Neil Banfield

Join Date 04/2001

+1104

Do you have a screenshot of this?

Successfully updated karma reason!

gmc2

Join Date 11/2003

+296

If it's a skin then the frame button position settings would control button placement. The placement is the same for un-maxed and half screen windows. So if this problem actually exists (don't have version 7.9) it would seem to be a WB issue.

Wish people would post pictures along with these type of posts.

spoiler's not working

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

Every skin. Office 2013 64-bit. I can only reproduce it after I change WindowBlinds several times.

Poking around some more, the cut off seems to be specific to new or opened email messages in Outlook. Oddly, messages opened prior to changing skins don't seem to be affected.
http://screencast.com/t/3Nn7bMeem8w

However, snapping Pidgin to the left-hand side also produces strange results: it doesn't fill the left-half as expected. This may or may not be related to the issue above.
http://screencast.com/t/2TnW38sJq6ms

Sorry I don't have time to conduct a more detailed analysis. Hopefully this information and the dxdiag dump give you enough to work with, without sending you on a wild goose chase. Let me know if I can help in terms of "try this" or "go here to get logs" etc.

Successfully updated karma reason!