The Goat isn't listing for QSY-Requests

[int2001]

when working with Wavelog one could trigger a QSY by clicking at the cluster.
That click triggers a http-GET-call to localhost, which is catched by WLGate (or the goat).

See here.
Not sexy - but works.

Just a suggestion to make the mighty goat feature-complete for SSB/CW

[johnsonm]

I'm not sure how I missed this before. [Edit: somehow it didn't occur to me that I had to watch activity on my own repositories...]

I think this would require implementing #1

Now that WavelogGate is a Go binary rather than a massive Electron app, it probably makes more sense for most folks with limited resources who want all the features.

[johnsonm]

And now I see your PR #2 so I'll look! ☺

[johnsonm]

So... I don't run WaveLogGoat on the same network as my rig computer, so I don't think that I can test this if I implement it.

[johnsonm]

I'm now subscribed to notifications from my own project (thanks, GitHub!) so I should actually notice now if anyone wants to take this on. 🤣

That said, WavelogGate now being a Go binary that uses the local browser probably meets 90% of users' needs; my preference for having no UI at all, just a configuration file and a systemd user unit, is probably weird.

[johnsonm]

OK, I was confused. I can look at this more.

[johnsonm]

The hardest part was finding the CAT control icon in Wavelog. I keep trying to find it in the hardware configuration.

[johnsonm]

Works on my machine. Released as v0.2.0.

Sorry this took so long. I'm now subscribed to updates for my own project (thanks, GitHub!) so I'll actually see any new issues that are filed. 🙄

[int2001]

Have a look at my fork. Possible that I made other adjustments. Too long ago. Didn't want to claim your project. But I like it :)

[johnsonm]

Ah. I didn't realize that there was more there. Thanks! I'll work out what to cherry-pick, but I'll expect to broadly reach parity.

[johnsonm]

@int2001 OK, I had to cherry-pick by hand because I'd diverged a bit. But I think that everything other than the "no support here" banner on the README is now represented in my v0.3.0 release.