serjts

warning: vibe-coded (hope this isn't cringe to say anymore), IMO it is coming out okay!

Didn't like the original java app, so told LLM to rewrite it in rust.

Feel free to throw yer pull request at me.

If you have interesting ideas feel free to open an issue and i'll try and look at it.

Only tested it (lightly!) on macOS & Linux. Would be cool for others to add support for their own digital scopes if possible, cuz I only got this cheap owon one I bought a number of years ago.

Also! I haven't actually used an oscilloscope seriously in over 10y, so I'd appreciate feedback if anyone familiar with one can test drive this, maybe there are blatant issues with it's functionality.mm

TL;DR - The major difference is that while Shortcat uses the accessibility API, KayZeer uses image processing. My idea is that you can use it whether your apps support that API, or even if you are working in a VM.

Shortcat does have the advantage that you can fuzzy search. KayZeer at the moment does no OCR or any of the sort.

On the other hand KayZeer (sorry for the bad name, Kay was my labs name, and "seer") had stuff like "." repeats the last command, and it has a LRU of the last "point" you clicked on. You can also manually add points which is useful for instance for each monitor I add 3 points across the screen which normally tie to a file/project view and 2 editor tabs.

But I do accept (and welcome!) suggestions.

I tried going the ML route but boy.. I just couldn't get it to be accurate and/or fast. Maybe I'll retry someday.

KayZeer also seems much faster (I am not surprised because I tried using the accessibility API and gave up because while is sounds efficient in practice it felt very heavy).

Wow you had me spooked. I'd never seen shortcat before and it just so happens it has the same default key bindings as KayZeer, it is also a "cat" while mine is a "dog". So the moment I trigerred the key binding I got spooked because it did exactly what KayZeer.

Ah, we are from the same tribes! Let's go talk to the the bazel and to the vcpkg tribes. But what about the fact that cmake isn't a build system, also conan 2.0 was a bit rough the last I saw.. maybe thats why clion/intellij dropped support for it out of the box and now uses vcpkg?

The real, everpresent and probably future nail in the coffin of C++ is the lack of a standard apckage manager and build system. The rest is just what happened to be picked up by social/news as it is easier and flashier to talk about.