Coder Social home page Coder Social logo

Comments (12)

appcreatorguy avatar appcreatorguy commented on August 17, 2024 1

Ok, i was having the same issue and found that due to my device name in KDE Connect having single quotes in it, the name getting passed to the script to bring up the rofi menu was being escaped, causing an error.
Changing the device name in KDE Connect settings to remove the single quotes fixed this for me

from polybar-kdeconnect.

haideralipunjabi avatar haideralipunjabi commented on August 17, 2024

It should only show up if the device is connected. What is the color of the icon you are clicking?

from polybar-kdeconnect.

Kabouik avatar Kabouik commented on August 17, 2024

Oh, I see, so I need to add my devices using kdeconnect-cli first I suppose. There is probably an issue with my phone because it is not listed when I run kdeconnect-cli -l on the computer. I'll report back here if the click action works when this other issue is fixed.

I changed the colours in your script but the icon shown is the icon corresponding to no device connected, indeed.

from polybar-kdeconnect.

haideralipunjabi avatar haideralipunjabi commented on August 17, 2024

An unpaired device is shown in Yellow Color (default colours). You can pair using that icon as well. A device has two boolean values associated with it, isReachable and isTrusted. An unpaired device will have isReachable = true and isTrusted = false.

from polybar-kdeconnect.

octal-illumination avatar octal-illumination commented on August 17, 2024

Hi I am having a similar issue here, and in my case, the device is connected. I have black icons shaped as circle square and triangle when device is paired and not reachable, red colored icons when the device is paired and reachable. events from kdeconnect app is working on either direction, but unfortunately no rofi menu as experienced by the OP. AM i doing something wrong?

red_threeshapes

black_threeshapes

My Polybar-kdeconnect config:

[module/kdeconnect]
type = custom/script
exec = "~/.config/polybar/scripts/kdeconnect/polybar-kdeconnect.sh -d"
tail = true

I can't figure out what I am doing wrong here. Please let me know if you need any other information.

from polybar-kdeconnect.

haideralipunjabi avatar haideralipunjabi commented on August 17, 2024

What happens when you execute the following in terminal:

rofi -sep "|" -dmenu -i -p DEMO -location 0 <<< "Row1|Row2"

from polybar-kdeconnect.

octal-illumination avatar octal-illumination commented on August 17, 2024

rofi -sep "|" -dmenu -i -p DEMO -location 0 <<< "Row1|Row2"

I get the rofi demo menu with Row1 and Row2

from polybar-kdeconnect.

octal-illumination avatar octal-illumination commented on August 17, 2024

Additionally i get grey icons once in a while when the device is paired and reachable, verified when i check with kdeconnect-cli -l, i get

- Device name: Device ID (paired and reachable)
1 device found

This is the same result i get when i have red icons.
grey_threeshapes

Not sure why different colors for the same state. May be something else is wrong with my set up?

Update: okay, going through the script, i can see it indicates the battery level, which is 79% now. But still no menu or mobile icons though.

from polybar-kdeconnect.

haideralipunjabi avatar haideralipunjabi commented on August 17, 2024

Yeah, the colours change with the battery level of the device. But I still can't figure out why clicking isn't working for you

from polybar-kdeconnect.

octal-illumination avatar octal-illumination commented on August 17, 2024

Okay cool. I will try to play around and if i find something, I will post here, thanks

from polybar-kdeconnect.

 avatar commented on August 17, 2024

I'm having the same issue. Clicking does nothing. Icon is white, and kdeconnect-cli -l shows the device as paired and reachable. rofi -sep "|" -dmenu -i -p DEMO -location 0 <<< "Row1|Row2 brings up the rofi demo menu.

Has anyone found a solution?

from polybar-kdeconnect.

k1ake avatar k1ake commented on August 17, 2024

Have the same problem, but i found an issue: script does not assign properly DEV_ID and DEV_NAME, so you have to manually put it inside script or into your polybar config. So i solved that with adding that string in script: DEV_ID="$(kdeconnect-cli -a --id-only)"

from polybar-kdeconnect.

Related Issues (17)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.