[DXLog.net - Support] scripts as commands and inside CW messages

Tue Jan 29 14:48:22 CET 2019

Matt,

in Chris' unfortunate absence I will try to help.

On 1 I don't know and would surprised if it was possible. (But Chris
did surprise me the other day...) I don't really see myself typing
commands during a contest but it would be neat when developing
scripts.

On 2 I also do not think it is possible. The Main method of the script
class is only passed three environment objects, FrmMain, ContestData,
and COMMain. A possible workaround would be to do a custom parsing of
the key macro definition (cdata.dalHeader.CWMessage1 etc.) but I doubt
this would work, the built in macro definition parser would probably
throw an error for anything outside the established syntax.

On 3 this indeed seems to be the case. I created a script which puts a
random number in the status bar at the bottom of the DXLog window so I
could tell when it was invoked and when executing the test key macro
"QSL $!EXPERIMENT TU ES GL $MYCALL $!EXPERIMENT" I could see that the
macro was invoked exactly at the end of transmission of "QSL" and then
again at the end of transmission of my call.

Unfortunately I have not been able to figure out how to correctly
insert characters into the CW transmission buffer from a script when
called from a key macro. Using the object browser I found two methods,
frmMain.SendCW(message, TXOnRadio, addSpaceWhenStacking)
and
frmMain._cwKeyer.CWMessageStack.Enqueue(message)
but using either, "message" ends up transmitted last, *after* the
completion of the key macro.

I will keep digging.

My struggles with the CW transmission buffer may not be a problem for
you if you intend to use CAT-command driven CW transmission. Keep in
mind, though, that you have to design/provide a replacement for the
Alt-K CW keyboard function with this approach. (I came across this
same problem in my Win-Test script kit for the KX2, which also uses
CAT-command driven CW transmission. Fortunately Bob N6TV had a neat
solution for it.).

73,

Björn

Den mån 28 jan. 2019 kl 05:55 skrev Matt NQ6N <matt at nq6n.com>:
>
> Thanks much for the helpful information, Chris and Björn!  Chris, I hope
> your health is improving.
>
> Three other quick questions:
>
> 1) Is it possible for me to trigger a script by typing a word into the
> logger window? Suppose I wanted to make a script called qsyup10, would it
> be possible to simply type that in the data entry field and have the script
> be called?
>
> 2) When using $!SCRIPTNAME syntax in a CW message, is there syntax to pass
> in an argument?  For example $!SCRIPTNAME|arg1|arg2|  ... more specifically
> I'd like to write a script called CWX and do something like $!CWX|cq test
> nq6n nq6n|
>
> 3)  Do scripts that are called using $!SCRIPTNAME syntax get called
> synchronously and block until completion?  In other words would $!SCRIPT1
> $!SCRIPT2 wait until SCRIPT1 was finished before calling SCRIPT2?
>
> The reason for #2 is that when operating my Flex transceiver remotely there
> is no CW side tone available when using the Winkeyer emulation, and I would
> like to try the other method available for Flex which is CAT based keying.
>
> 73,
> Matt NQ6N
>
> On Sun, Jan 27, 2019 at 12:45 AM Björn Ekelund <bjorn at ekelund.nu> wrote:
>
> > Chris,
> >
> > I am so sorry to hear. Gall bladder issues can be excruciatingly painful.
> > I hope you are doing OK and you can go home soon.
> >
> > Yes I am very happy with my ICOM script kit. I have honed it over a few
> > contests and it is quite solid now. I am getting requests for it but tell
> > everyone they will have to wait for 2.3.18 for it to work.
> >
> > I am really looking forward to proper IC-7610 support and being able
> > to use "CI-V Transceive". In the current release this works really well
> > with
> > my IC-7300, the user experience is excellent.
> >
> > Thank you for the tip about the $!SCRIPTNAME syntax. It was a very
> > nice surprise.
> > So far I hadn't figured out how to automatically clear RIT at CQ or TU/Log.
> > Now I know. I have already tested it and it works.
> >
> > The only thing that I have not yet figured out how to do is to send a
> > received
> > exchange in a macro (e.g. re-sending a received name in QSO party style
> > contests
> > like CWT). But I think using a custom script together with the
> > $!SCRIPTNAME syntax
> > may actually be the solution to also this.
> >
> > Get well soon.
> >
> > Björn SM7IUN
> >
> >
> > Den sön 27 jan. 2019 kl 07:14 skrev 9A5K <9a5k at 9a5k.com>:
> > >
> > > Great. :-)
> > >
> > > I am in hospital for few days because of issues with gallblader stones,
> > > should be home in few days.
> > > Then we can start clearing last issues with 2.3.18 and finally make
> > public
> > > release.
> > > I saw that you make good progress with scripts and custom forms, that's
> > > really great.
> > >
> > > 73,
> > > Chris - 9A5K
> > >
> > >
> > > On Sun, Jan 27, 2019 at 5:41 AM Björn Ekelund <bjorn at ekelund.nu> wrote:
> > >
> > > > Thanks Chris!
> > > >
> > > > I was not aware of this. Great! Now I can add $!CLEARRIT to my CQ/and
> > TU
> > > > keys!
> > > >
> > > > 73,
> > > >
> > > > Björn SM7IUN
> > > >
> > > > Den lör 26 jan. 2019 kl 22:07 skrev 9A5K <9a5k at 9a5k.com>:
> > > > >
> > > > > Of course.
> > > > > But syntax is $!SCRIPTNAME ...
> > > > >
> > > > > And in the script you can do a lot of things, including sending cat
> > > > > commands etc.
> > > > >
> > > > > Check here a bit for some examples:
> > > > > http://dxlog.net/docs/index.php/Scripting
> > > > >
> > > > >
> > > > >
> > > > > On Sat, Jan 26, 2019 at 9:53 PM Matt NQ6N <matt at nq6n.com> wrote:
> > > > >
> > > > > > I am new to DXLog and am wondering if C# scripts can be used as
> > > > commands
> > > > > > (typing in the name assigned in "script name" into the entry
> > field),
> > > > and if
> > > > > > they can be used in CW messages as in $SCRIPTNAME.
> > > > > >
> > > > > > In addition to wondering about the above items, I am also
> > wondering if
> > > > > > there is a way to trigger CAT commands from within CW messages.
> > > > > >
> > > > > > 73,
> > > > > > Matt NQ6N
> > > > > > _______________________________________________
> > > > > > Support mailing list
> > > > > > Support at dxlog.net
> > > > > > http://www.dxlog.net/mailman/listinfo/support
> > > > > >
> > > > > _______________________________________________
> > > > > Support mailing list
> > > > > Support at dxlog.net
> > > > > http://www.dxlog.net/mailman/listinfo/support
> > > >
> > > > _______________________________________________
> > > > Support mailing list
> > > > Support at dxlog.net
> > > > http://www.dxlog.net/mailman/listinfo/support
> > > >
> > > _______________________________________________
> > > Support mailing list
> > > Support at dxlog.net
> > > http://www.dxlog.net/mailman/listinfo/support
> >
> > _______________________________________________
> > Support mailing list
> > Support at dxlog.net
> > http://www.dxlog.net/mailman/listinfo/support
> >
> _______________________________________________
> Support mailing list
> Support at dxlog.net
> http://www.dxlog.net/mailman/listinfo/support