On 09/08/2011 05:40 PM, w1hkj wrote:
http://www.w1hkj.com/alpha/fldigi/
Version 3.22.0AL Alpha release
Log Server lookup
* Added cty.dat search when connect to log server
- cty.dat must be installed in the current fldigi
files directory
Delayed Tags
* Added queued tags
- <!GOHOME
- <!GOFREQ
- <!IDLE
- <!WAIT
Remember that the Inline macro tags
- <DTMF - dual tones
- <!WPM - CW words per minute
- <!POST - CW post delay
- <!PRE - CW pre delay
- <!RISE - CW rise/decay time
- <!MODEM: - change to specified modem
- <!GOHOME
- <!GOFREQ
- <!IDLE
- <!WAIT
are not listed in the macro editor. You select the immediate mode
equivalent and then manually insert the ! character.
Each delayed tag shows as "<!" in the TX transmit buffer. As it is
executed it is displayed in the RX buffer using the full string and
highlighted with the control coloring.
Dave
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
Dave,
I had some fun playing with the new AL version with Ubuntu 8.04 and
11.04 last night. Here is what I have found.
I am running fllog remote on a separate server and two connected
desktops both imputing log info over the network to the logbook.
- The cty.dat seems to be working fine now.
- The dupe color is not working correctly. I am not sure how to
narrow this down yet. The symptoms I am getting indicate it may be a
timing issue, because my older/slower computer (on wifi) seems to be
working fine with dupes, but the faster computer (on wired connection)
is not indicating dupe by changing color unless the callsign is only one
character long, anything like a normal call does not seem to work.
Timing/race issues always make me scratch my head.
- On the remote server (Ubuntu 8.04) running fllog, the update and
delete buttons are both greyed out when I do a VNC into that server, so
I can not work with that log. That may have been an intended feature,
but I was not able to clean up mistakes there. I also noticed the
actual log entry seems to be sorting, because two entries in the same
minute time span are not showing up in the same sequence they were
entered. Again that may be intentional, just something I noticed.
- With the <! delayed tag changes. I had some fun playing last night,
but there seems to still be a small problem, and it looks like something
to do with the transmit buffer not being cleared before going to the
next tag, or not being cleared when <RX> is sent. The symptom is that
it will sometimes get stuck without ending, if I cascade more than two
or three different modems, and I noticed it best when using the MFSK16
modem as the last one in the sequence. The other symptom is after the
sequence is ended or stopped, the next time I press the same macro
button, it starts off with what ever the last modem was, for a few
characters, and then shifts to the first modem requested in the macro
line. The good part is that it did not crash my computer.
73,
Al W6HGF
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
