Live data from Hacker News

Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

github.com

71–80 of 274 posts

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#71

Earlier quoted context omitted.

reprogrammable buttons, adjustable dpi, customizeable lights, etc

All of those should be state changes in the mouse.. IE. the software should run to make the settings then exit. There should be no reason for it to keep running.

Their best feature - and the one thing that I have most missed for years after moving to Linux - is automatically changing the active mouse profile based on the focused application.

It's so powerful. Any custom buttons for any program, without ever having to think about it. On Linux, without it, I'm stuck manually cycling through the 3 on-board profiles.

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#72
post #52

Earlier quoted context omitted.

My one gripe with Logitech mice is that none of their "office" mice support high refresh rate polling.

Also they've been very slow to adopt optical switches compared to other brands, a handful of their high end gaming mice have them, but the vast majority of their range still uses the same old mechanical switches that tend to start erroneously double clicking after a while.

If your mouse starts double clicking, play a game of Quake 3 for an hour, or just click a bit more aggressively for the next hour. It clears the problem, per my experience.

What I understood is, the switches on these mice (I have G700) are practically abuse-proof. However, they don’t like to be used lightly and start to glitch possibly from fine dust. Using the switches more aggressively cleans them up.

My first generation G700 still works great.

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#73

Earlier quoted context omitted.

Logitech's might be a large download, but their Windows software still seems far more optimized than Corsair's. After a few days of uptime, Corsair's processes would have nearly an hour of CPU time. Logitech's would have a couple minutes at most. I replaced all my Corsair equipment with Logitech or others after seeing that.

Why does a mouse need an app, again?

To be able to program all the configurable buttons, and upload the macros and settings to the profiles present on the mouse itself, so you can use all the features of your mouse, tailored to you, even if you don’t have the software on the target device you’re using your mouse.

Yes, Logitech’s high end mice store settings themselves. The app is just a programming interface. It sometimes does per program profile switch, too, IIRC.

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#74

Been using this for years on my Debian 12 install and it’s been very solid. Why it’s on the homepage though is perplexing.

Lightweight software that does one thing well always makes for a great casual conversation topic here. You learn how widespread knowledge of it it is or isn't. And, often adjacent tools that might be of interest are mentioned. Admittedly not "news".

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#75

Earlier quoted context omitted.

I think it's implicit that a switch has to be on/off. Do you mean opt-in rather than opt-out?

That would imply there’s a third, indeterminate state prior to opting one way or another (which is the ideal situation - ask on install with a non defaulted option)

No, prior to opting the state is off. This is what opt-in means.

Asking on install just gives room to implement a dark pattern and trick people into opting in undesiredly anyway.

Or you can just use Solaar :) and don’t feel bad about it, you already gave Logitech money for the freaking mouse.

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#76

Earlier quoted context omitted.

I think it's implicit that a switch has to be on/off. Do you mean opt-in rather than opt-out?

That would imply there’s a third, indeterminate state prior to opting one way or another (which is the ideal situation - ask on install with a non defaulted option)

A reasonable third, and default, state could be collect diagnostic data locally. The user can choose to send the diagnostic data if they have issues with the device. After all, the term diagnostic data implies that it is being used for troubleshooting.

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#77

Earlier quoted context omitted.

I think it's implicit that a switch has to be on/off. Do you mean opt-in rather than opt-out?

That would imply there’s a third, indeterminate state prior to opting one way or another (which is the ideal situation - ask on install with a non defaulted option)

A master programmer passed a novice programmer one day. The master noted the novice’s preoccupation with a hand‐held computer game. “Excuse me”, he said, “may I examine it?”

The novice bolted to attention and handed the device to the master. “I see that the device claims to have three levels of play: Easy, Medium and Hard”, said the master. “Yet every such device has another level of play, where the device seeks not to conquer the human, nor to be conquered by the human.”

“Pray, great master”, implored the novice, “how does one find this mysterious setting?”

The master dropped the device to the ground and crushed it underfoot.

And suddenly the novice was enlightened.

The Tao of Programming, Geoffrey James

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#79

Earlier quoted context omitted.

I think it's implicit that a switch has to be on/off. Do you mean opt-in rather than opt-out?

That would imply there’s a third, indeterminate state prior to opting one way or another (which is the ideal situation - ask on install with a non defaulted option)

I think, today, that state is the "Remind me later' button state.

Re: Solaar is a Linux manager for many Logitech keyboards, mice, and other devices

#80
For Linux pros here, can anyone explain how is this, in my understanding, driver implementation for Linux to be completely written in Python?

My understanding is most for driver code is written in C or C++. The 'new' way of developing - the kernel development is in Rust.

How can this work that is written in pure Python?

Post reply on HN