#43 Use rofi instead because wofi is not on-top in fullscreen mode 14 days ago

Comment by ~scoopta on ~tsdh/swayr

Apologies for the confusion, I don't use swayr(in fact I had never heard of the project till now, looks cool though) I was simply giving the appropriate information for how to configure wofi. The link you're looking at is only intended to provide a sample styling setup. All documentation is in the wofi man pages. All config options are documented in wofi(5) including the layer option.

#43 Use rofi instead because wofi is not on-top in fullscreen mode 14 days ago

on ~tsdh/swayr

Hello. It is reverse for me! For command line I require wofi --show=dmenu -Dlayer=overlay works isolated to the command line.

About the documentation at https://cloudninja.pw/docs/wofi.html I absolutely cannot use it. Clicking on the search bar just does nothing. Thats because its actually an image. But I wanted to search through the docs... Nevermind. man wofi tells me that The config file which defaults to $XDG_CONFIG_HOME/wofi/config. Which is helpful, which also means you did not mean swayr config file. Swayr config file does need -Dlayer=overlay and then it does work as intended.

For swayr team - please integrate the information about overlay into the swayr documentation.

For you - please close the wofi issue.

On 24.09.2024 18:57, ~scoopta wrote:

I mentioned this on the wofi issue that was opened but if you'd like wofi to sit on top of fullscreen apps you can add -Dlayer=overlay to the command line or layer=overlay in its config file.

#43 Use rofi instead because wofi is not on-top in fullscreen mode 14 days ago

Comment by ~scoopta on ~tsdh/swayr

I mentioned this on the wofi issue that was opened but if you'd like wofi to sit on top of fullscreen apps you can add -Dlayer=overlay to the command line or layer=overlay in its config file.

#228 wofi fails to put itself on-top in fullscreen applications 14 days ago

Comment by ~scoopta on ~scoopta/wofi

This is neither, it's a design choice. I deliberately didn't want wofi on the overlay layer as it's used by lockscreens and other things people EXPECT on top, so I chose the next layer down "top" which happens to be below fullscreen apps. If you don't like this you can use -Dlayer=overlay or add layer=overlay to your config file.

REPORTED RESOLVED BY_DESIGN

#27 Building failure at "ninja -C build" 15 days ago

Comment by ~scoopta on ~scoopta/wlrobs

What distro are you on? Screenshot makes me guess mint but what version? I ask because while I can pretty easily fix this error I'm slightly worried about the fact that your build scripts seem to be generated with -Werror which will make any warning fail to compile and is not what meson should output by default according to their documentation. As far as a quick fix goes you should be able disable it by doing meson setup build -Dwerror=false after deleting your build folder.

#190 hide_search doesn't initially hide the search bar 2 months ago

Comment by ~scoopta on ~scoopta/wofi

This was fixed in e59e3f58117b but hasn't been in a versioned release. v1.4.1 has a broken hide_search option but working key_hide_search. What version are you on?

#225 No entries for wofi --dmenu 2 months ago

Comment by ~scoopta on ~scoopta/wofi

REPORTED RESOLVED CLOSED

#196 Is it possible to style (or at least hide) the search bar magnifier icon? 2 months ago

Comment by ~scoopta on ~scoopta/wofi

Added the config option use_search_box which defaults to true in 96bb7a18c2b0. If you set it to false in your config or with -Duse_search_box=false it will use a regular entry.

REPORTED RESOLVED IMPLEMENTED

#196 Is it possible to style (or at least hide) the search bar magnifier icon? 2 months ago

Comment by ~scoopta on ~scoopta/wofi

Hmmmmm, that might be worth adding as an option. I don't LOVE the idea of changing it for everyone but I do like the idea of having an option for it.

#219 [BUG] Blender Failing to launch through wofi 2 months ago

Comment by ~scoopta on ~scoopta/wofi

disable_prime=true causes wofi to ignore prefersNonDefaultGPU, if disable_prime is not set then wofi will abide by prefersNonDefaultGPU which translates to setting the DRI_PRIME=1 environment variable if prefersNonDefaultGPU=True. I'm actually not entirely sure on the semantics of DRI_PRIME=1 as that's handled by the GPU driver, wofi just sets it based on the desktop file. I will do a bit of digging to see if this is actually a wofi bug?