Comment 34 for bug 455378

Sam, thank you for your detailed response! I can see what you are saying about fullsizing something to multiple monitors. However, in the use case I have I'm using multiple portrait-oriented monitors to display a single desktop so that creates some weirdness as the fullscreen window is tall and narrow.

More particularly, the new problem I've noticed is restricted to resize. Thinking back, I don't think the behavior of fullscreen has changed - it is as you describe it. I simply noticed the blender issue after the resize issue but I've seen this behavior with other apps. It never mattered because before I could resize the window to take up 90% of the two screens, which was my preferred pattern anyway. The behavior of No Machine is actually a bit comical with resize, even using the Alt-F8 trick, as it will appear to size correctly, wriggle itself a bit, then shake the new size off. I'm sorry I sounded so frustrated in my earlier email but since No Machine doesn't do it all the time - just 95% of the time - I got bitten when a window I thought was stably resized suddenly, making the machine on the other end effectively unusable through No Machine.

Jeff, if I get it working I'll let you know. I've looked at the code changes and it *seemed* relatively straighforward but I had build issues on the machines I have available to me. Since this is a problem I have on my work machine, if I can use a workaround (e.g., running No Machine on my laptop's monitor screen) I have to prioritize doing normal work to working with Compiz. However, if I get it running I will definitely send it to you.