Skip to content

Rounded corners. #17

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

Closed
agonzal opened this issue Feb 19, 2021 · 15 comments
Closed

Rounded corners. #17

agonzal opened this issue Feb 19, 2021 · 15 comments

Comments

@agonzal
Copy link

agonzal commented Feb 19, 2021

How did you get your corners to be rounded? In my setup they are straight corners and would love to have them rounded like in your screenshots. please advise thanks!

@morenoled
Copy link

your picom effects are working fine? like transparency and shadowing? If not, try to change the spawnOnce "picom ?" in xmonad.hs (in my case, line 331), to spawnOnce "picom -f".
Then, run xmonad --recompile and reboot.
This is how I made it happen.

@morenoled
Copy link

By the way, I'm using jonaburg-picom-git.

@Axarva
Copy link
Owner

Axarva commented Feb 20, 2021

It's exactly as @morenoled described, although I don't see where the line spawnOncwe "picom ?" occurs in the file. And yes, the specific fork of picom, (picom-jonaburg-git on the AUR) is needed for the transitions. A link to the picom fork repository is here.

@morenoled
Copy link

morenoled commented Feb 20, 2021

sorry, it's because I don't remember the rest of the script. The ? means, "Whatever is there", =].
I forgot to specify that =/.

@agonzal
Copy link
Author

agonzal commented Feb 20, 2021

I have literally been running Xmonad for 2 days now. My spawnOnce line already had picom -f and I went ahead and compiled jonaburg-picom from source and installed that on my system (as well as removed the existing rpm providing picom). One thing I did notice was the fact that the corresponding picom.conf was in ~/.config/picom.conf and not ~/.config/picom/ so I have made that change, but I still do not see any transparency or shadows or round corners.

image

I am running v8 of picom from that repo you directed me too.

here is the corresponding section you brought up from my xmonad.hs

myStartupHook = do
spawnOnce "exec ~/bin/bartoggle"
spawnOnce "exec ~/bin/eww daemon"
spawn "xsetroot -cursor_name left_ptr"
spawn "exec ~/bin/lock.sh"
spawnOnce "feh --bg-scale ~/Pictures/wallpapers/lovelace.png"
spawnOnce "/usr/local/bin/picom -f"
spawnOnce "greenclip daemon"
spawnOnce "dunst"

The install also came with a picom-trans but that seems to be a shell script, and I don't know what to really do it with it.

@agonzal
Copy link
Author

agonzal commented Feb 20, 2021

I guess I can run picom-trans and it does indeed make a window that I click on transparent. So apparently that is working.

@Axarva
Copy link
Owner

Axarva commented Feb 21, 2021

Did you issue xmonad - -recompile after making changes to your config file? Did you then log out of xmonad and then log in? And what happens when you issue picom -f directly in your terminal?

@agonzal
Copy link
Author

agonzal commented Feb 21, 2021

I did recompile after saving the changes to xmonad.hs and took things a step further and rebooted the system. There appears to be an error (level WARN) in the config file Unfortunately the error message does not give me further input beyond the following:

[ 02/20/2021 21:14:38.760 parse_config_libconfig WARN ] Invalid blur method dual_kawase, ignoring.

That message followed by "FATAL_ERROR another compositor manager is already running.

picom -f

[ 02/20/2021 21:14:38.760 parse_config_libconfig WARN ] Invalid blur method dual_kawase, ignoring.
[ 02/20/2021 21:14:38.764 session_init FATAL ERROR ] Another composite manager is already running

This is what I get when running picom with the f switch from the terminal. I can attach the config I am using but I did not make any modifications to the one you provided. it currently resides at ~/.config/picom/picom.conf

@agonzal
Copy link
Author

agonzal commented Feb 21, 2021

Based on yshui/picom#361 dual_kawase blur is exactly what I need to get the rounded corners, and for some reason it says it is not an accepted blur. I compiled that repo from source, but maybe I did something wrong? Will try again shortly.

@Axarva
Copy link
Owner

Axarva commented Feb 21, 2021

That pull request is still not merged completely, so it seems that it won’t work. The fork that the current config file in this repository is tried and tested on, is picom-jonaburg-git. Please try the binary from that specific fork and compare results.

@agonzal
Copy link
Author

agonzal commented Feb 21, 2021

That is what I am running. It was mentioned yesterday so I went and compiled it following the instructions. It installed a binary to /usr/local/bin/picom and a shell script to /usr/bin/picom. I can use the picom-trans script to make windows transparent. On another note, I just ran into the workspaces.tint2rc losing color, the fix you mention worked once, but upon reboot, the issue came back even though your fix is still present.

Is it against the release v8 or a clone of the current repo state? That could be where I messed up as I downloaded v8 release. let me clone the repo and build again.

@agonzal
Copy link
Author

agonzal commented Feb 21, 2021

That was the issue. I built the v8 release instead of cloning the repo and building the branch next. Rounded corners have been enabled. My bad. Now to fix this damn workspaces.tint2rc losing colors, lol. Thanks for being patient with me, much appreciated.

@agonzal agonzal closed this as completed Feb 21, 2021
@agonzal
Copy link
Author

agonzal commented Feb 21, 2021

cloning the repo, and building the code in the 'next' branch worked. Rounded corners have been achieved. Thank you for your assistance and patience. I should have noticed that you put -git in your version! I have made quite a few customizations to the layout, but overall you provided the foundation, thanks!

@Axarva
Copy link
Owner

Axarva commented Feb 22, 2021

Ah, glad you got everything fixed! About the workspace panel... could you perhaps show me where exactly did you add the line?

@Axarva
Copy link
Owner

Axarva commented Feb 22, 2021

444bd53 has solved the bar issue. Just updated my tint2 fork to fix the bug. It should be fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants