-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doesn't support useless gaps #2
Comments
Hi @DanielFGray , I should be no problems. I will add it as soon as possible |
in awesome 4.0 the variable is |
Any news on this one? |
I've just created a pull request for this. After a long while of playing around with it, I was able to get |
I think that has something to do with the tag's padding/border property. I noticed the issue before but it doesn't appear to be related to the |
I quickly looked into it and changed the two lines (507, 643) where useless_gap = useless_gap * 2.0 + beautiful.border_width * 2 This seems to deliver correct gaps between the clients, but the outer border extends to the right/bottom respectively. local area = p.workarea
area.width = area.width - beautiful.border_width * 2;
area.height = area.height - beautiful.border_width * 2; |
I think |
Well, it's the border drawn around clients. If that still doesn't help, try setting it to a higher value to make it more noticable. |
Aha. That's it. It doesn't look like |
I stand corrected. Using the attached code I was able to get |
I've also been fiddling around with it for a bit and got it mostly working using the code modifications I mentioned earlier. Unfortunetly removing clients doesn't always work as it should. But I found out how to consistently reproduce it:
The bottom two windows on the right side should now overlap. Unfortunetly my understanding of the treetile code is rather limited, so I have no idea how to fix that. Maybe you have an idea. Here's the code I used: init.lua.txt |
treesome added it with RobSis@256250d
hopefully wouldn't be too much trouble to add support for treetile?
The text was updated successfully, but these errors were encountered: