What questions? It's trying to explain the abstraction being made inside
hamlib. If you look at the new caching code it implements this and so do the
satellite mode rigs
For some software the RX/TX VFOs should serve their purpose (like WSJT-X which
only cares about RX/TX and not specific VFOs).Only software that wants to
display or manipulate all the VFOS needs to pay attention to what they are
asking for.
There's a couple of new function in the current github and what will Hamlib 4.2
very soon.
get_vfo_list -- dummy device example here...Rig command: \get_vfo_listVFOs: RX
TX VFOA VFOB VFOC SubA SubB MainA MainB Sub Main MEM
get_vfo_info -- single call to retrieve freq mode width and split status for
any VFO -- come to think of it should probably add satmode status too.Rig
command: \get_vfo_info VFOAFreq: 145000000Mode: FMWidth: 15000Split: 0
Mike W9MDB
On Tuesday, April 6, 2021, 04:56:28 AM CDT, G8DQX (WSJT developers on SF)
<[email protected]> wrote:
Au contraire,
Claude was reading fresh code, to be found at
https://github.com/Hamlib/Hamlib/blob/master/VFOs.txt. That code, in and of
itself, raises quite a few questions!
73, 88, Stay Safe,
Robin, G8DQX (who's never quite believed that Read the Code, Luke is the full
answer)
On 04/04/2021 19:59, Jim Brown wrote:
On 4/4/2021 5:47 AM, Claude Frantz wrote:
Please explain me: What is the difference between VFO-A, VFO-B, VFO-C, etc. and
the subVFO's.
RTFM!
73, Jim K9YC
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
