rigctl f m order bug

[mdblack98]

I'm not sure how long this has been broken but it is certainly a regression.

C:\build>\test-install\wsjtx-dev\Release64\bin\rigctl-wsjtx.exe -m2 f m
433550000
FM
15000

C:\build>\test-install\wsjtx-dev\Release64\bin\rigctl-wsjtx.exe -m2 m f
FM
15000
0
73
Bill
G4WJS.

Hi all,

relevant debug trace from rigctl;
rigctl_parse.c(1992):rigctl_get_freq entered
rig_get_freq called vfo=currVFO
vfo_fixup: vfo=currVFO, vfo_curr=currVFO
vfo_fixup: Leaving currVFO alone
rig.c(1520):rig_get_cache entered
rig_get_cache: vfo=currVFO, current_vfo=currVFO
rig_get_cache: vfo=VFOA, freq=0
rig.c(1629):rig_get_cache return(0)
rig_get_freq: cache check1 age=161ms
rig_get_freq: currVFO cache hit age=161ms, freq=0
rig.c(1984):rig_get_freq return(0)
0
rigctl_parse.c(2018):rigctl_get_freq return(0)
rigctl_parse: vfo_opt=0
rigctl_parse: retcode=0
rigctl_parse.c(1743):rigctl_parse return(0)
and from rigctld:

icom.c(2095):icom_get_mode return(0)
rig_get_mode: retcode after get_mode=0
rig_get_mode(2326): debug
rig.c(1353):set_cache_mode entered
rig.c(1417):set_cache_mode return(0)
rig.c(2341):rig_get_mode return(0)
rigctl_parse.c(2152):rigctl_get_mode return(0)
rigctl_parse: vfo_opt=0
rigctl_parse: retcode=0
sync_callback: client lock disengaged
rigctl_parse.c(1743):rigctl_parse return(0)
handle_socket: doing rigctl_parse vfo_mode=0
rigctl_parse.c(648):rigctl_parse entered
rigctl_parse: called, interactive=1
rigctl_parse: cmd==0x0a
rigctl_parse: cmd=q(71)
rigctl_parse: cmd==0x71
rigctl_parse: vfo_opt=0
rigctl_parse: quit returning NETRIGCTL_RET 0
rigctl_parse.c(799):rigctl_parse return(1)
handle_socket: rigctl_parse retcode=1
Connection closed from Bills_Lenovo:38553
Note that the frequency request is never passed to the server end.