Problem with IBar on Windows 10

[webframp]

I've been using windawesome for some time now after switching from bug.n. It's been really great to help recreate an Xmonad like experience on Windows.

Something just changed with Windows 10 Creators Update (not Fall version) and I'm not sure how to debug the exact issue. Windawesome appears to start fine and responds to configured keybindings, but the IBar does not display. Instead there is just the space the bar would take up padding the top of the screen.

Any suggestions would be much appreciated!

[boris-petrov]

Hi, I'm glad you like Windawesome! :)

I haven't been using Windows for quite a few years now and I don't even have one to debug the issue. If you have Visual Studio (you could even get the free version, it should work fine), you could try debugging the issue yourself. The Bar class which implements IBar is using Windows Forms so maybe something there changed in Windows 10. Perhaps you have a newer .NET which works differently than before?

I'm sorry I cannot help more. Feel free to ask any questions about the code and I'll answer as best I can! And I'll be glad to accept any pull-requests that fix the issue. :)

[webframp]

That's at least a starting point thanks! I'll see what I can find out. My current suspicion is actually related to the HighDPI changes discussed here: https://msdn.microsoft.com/library/windows/desktop/mt843498%28v=vs.85%29.aspx%28d=robot%29?f=255&MSPPError=-2147217396

I'll see how far I can get

[boris-petrov]

It is possible to be connected with this, yes. Hope you can manage! Did it run fine in VS?

[webframp]

Yea! After moving the IronPython and IronRuby dlls into place it did. I don't think I've found the real source of the problem yet but this branchs runs in VS for me now: https://github.com/webframp/windawesome/tree/modernize

[boris-petrov]

Glad to hear it. :) I guess the fix is EnableWindowsFormsHighDpiAutoResizing if that really was the problem. Once you're done, be sure to create a pull-request. :)