[Dxbase] MMTTY within DXbase code

Wed Nov 4 12:46:56 EST 2009

Eric,
I'd very strongly suggest using the most recent release of AXETTY. Joe got
it pretty well perfect. There's still the problem of the MMTTY engine not
being as tightly integrated as it should, but Joe says that's a licensing
issue. Other than that, click the call on the display (or type it in), use
the function keys that you've programmed yourself and that's it. There is a
macro to log the QSO in DX Base and clear the callsign field and another to
log it and not clear the info (in case you want to continue chatting with
the guy after you've logged the Q). You can create up to 3 sets of 10 macro
files (S&P, Run, Run-split for example), the ESC key now instantly stops
transmission. Joe and I went back and forth a few times and in my opinion he
got it as close to perfect as most operators would need. I think the current
version is 1.12B
-----------------------------------
Regards,
Peter,
W2IRT
-----Original Message-----
From: Eric - VE3GSI [mailto:ve3gsi at sympatico.ca]
Sent: Wednesday, November 04, 2009 10:22 AM
To: 'Joe Glockner'; w2irt at verizon.net; nealk3nc at gmail.com
Cc: dxbase at mailman.qth.net
Subject: RE: [Dxbase] MMTTY within DXbase code
Guys,
As for myself, I have never (knowingly) asked that MMTTY be included with
DxBase, only a more efficient way to interface MMTTY to DxB. As Peter has
mentioned it would be great if the logging programme could more closely
control the MMTTY interface when DxB starts and closes. I also wish to see
less mouse clicking involved to make a RTTY entry.
I have tried Joe's earlier versions of AXETTY and my findings at the time
were that the window sizes could not be controlled so I stopped using it. I
honestly have not followed any of the later versions Joe may have released,
I recall in an e-mail from Joe his intentions were not to make further
changes. So I went back to the original MMD bridge program that at least
allows me to configure screen sizes. Unfortunately, it does require a couple
of mouse clicks to move the call from MMTTY to DxB. The bridge program does
allow me to dabble with PSK using MMVARI which is also an excellent program.
I should mention, with the WriteLog contesting software and an optional free
interface for use with MMTTY it does the following. Simply clicking on an
active call in the MMTTY screen instantly populates the entry window of the
logging software, this way I can see if I need the call or have worked the
call. The size and location of the MMTTY tuning screen can be customized as
well as the many profiles that I have an option to use. WL starts and closes
MMTTY when I choose the option to do so. The F-Key MACROS used in WL are
used with the MMTTY program, I don't have to maintain separate MACROS as I
do when used with DxB. WriteLog is a paid for commercial program that DOES
NOT include MMTTY or the interface but the author does take advantage of
both in his coding.
It is popular knowledge that other available free logging software does take
advantage of Digital modes. In fact my kid brother uses one of them at his
own station. I am impressed with how easy he makes digital entries,
unfortunately the free software he uses sucks when it comes to speed and
logbook and card maintenance.
Neal, I do appreciate any thought you put into streamlining digital entries.
I really don't care for the 'gui' windows other programmers choose to use.
All I want is a efficient TAB-TAB-ENTER and configurable single line input
method as DxB now uses. And when the buro sends me a 'brick of cards' a way
to manage my data.
If you are wondering, yes I am that far behind with my e-mail. We moved to a
new country location and I have yet to set-up my station or station
computer.
>From our new digs,
Eric - VE3GSI
> -----Original Message-----
> From: Joe Glockner
> Sent: October-29-09 11:14 PM
> Subject: Re: [Dxbase] MMTTY within DXbase code
>>> Peter,
>> The MMTTY engine itself "can NEVER" be included in the DXbase
> code - because the MMTTY "author" expressly prohibits this
> for a Not-FREE Logging program ... The "ENGINE" can ONLY be truely
> included with the Logging Program installation, etc -- when
> that logging program is FREE .. which DXbase is not.
>> 73 Joe wa6axe
>>>> > From: w2irt at verizon.net
> > Subject: Re: [Dxbase] DXBase 2006
> >
> > -----Original Message-----
> > Subject: Re: [Dxbase] DXBase 2006
> >
> > I guess you can tell MMTTY is not high on my list of things to do!
> >
> > The reason is that digital mode programs focus on doing a great job
> with
> > digital qsos and have more time to make it great than I do. You will
> notice
> > however that their log capabilities are not that great (and that is
> the
> > focus I have for DXBase).
> >
> > [pjd] While I fully agree with the objectives you set out, I do think
> that
> > integrating MMTTY more fluidly into the program would be a tremendous
> boon
> > to a great number of users. I say this because RTTY is one of the
> modes that
> > virtually all DXpeditions (and certainly those to top-10 entities)
> will
> > operate, and many of us chase DXCC by mode as well as by band. As
> such, this
> > puts RTTY as a unique digital mode, moreso than any "soundcard" mode
> since
> > few if any major DXpeditions use PSK or any digimodes other than FSK
> RTTY.
> >
> > [pjd] Joe's app (AXETTY) is wonderful and I use it daily, though I
> *do* wish
> > the MMTTY engine could be built into the code so you can
> minimize/move the
> > app and all of it moves/closes at the same time. Maybe a compromise
> would be
> > to take everything from Joe's app and build it in natively as a
> separate
> > module to DXB 2010??
> >
> >