On Wed, Jun 16, 2010 at 05:56:51PM -0400, Jim Pryor wrote: > That sounds like the source of the problem. And indeed, git bisecting reports: > > > 38edc5809755b4623b30bcb1838360d29d86b789 is the first bad commit > > commit 38edc5809755b4623b30bcb1838360d29d86b789 > > Author: Julien Danjou <[email protected]> > > Date: Mon Oct 5 17:13:29 2009 +0200 > > > client: implements maximized and fullscreen requests with Lua > > > > Signed-off-by: Julien Danjou <[email protected]>
On Thu, Jun 17, 2010 at 10:11:41PM +0200, Adrian C. wrote: > I'm running the latest from 3.4 branch, and don't see this problem. > Fullscreen on tile layouts works right. You are running the master > branch? Btw it doesn't even have titlebars. Hi Adrian, thanks for trying to verify. The reference to titlebars is just because when one searches for "fullscreen"-related problems in the mailing lists and bugtracker, the main recent results that come up have to do with titlebars. I realize that titlebars have been disabled at some recent point. I was just trying to distinguish this issue from the existing discussions. The only branch I've been pulling is the master branch; is there another I should be using? If I build against the latest commit, as well as the commit listed above, and then restart using the default rc.lua file, fullscreening fails with the strange behavior I've described on just about every layout. The only layout where it works properly is awful.layour.suit.floating. Uli said he could reproduce. If you can't, I guess there's some difference in our systems that's a necessary element, too. -- Jim Pryor [email protected] -- To unsubscribe, send mail to [email protected].
