[WT-support] Repeat Message

[I4UFH]

Hi Bob,

Well i had tested several way, including ur suggestions, to strip same length messages between standard Fx and DVR script. And believe me ur solution is still the best one,
even the delays , as u mention are not so flexible as needed. So this solution is the best one.

Even , i still think, that this WT limitation are only a developer philosophy, even i can agree with Dev point of view, the common sense of any user, is that these  keys F1-F7
in SSB are only, or better , the last 20 years of Contest software have inducted into the user mind , for DVK play / Rec. No Matter if this key function can change ( attaching a script )
and so loosing it's properties , as repeat function. 

Just labeling in WT F1-F7 the keys were to apply the CQ repeat properties, is symptom also the Dev Team think that are worldwide defined as CQ Keys, so why not easily continue to applies the
properties of these keys ( allowing Repeat ) independently to the assigning of a script or not ? It will be care of the user, defining the script that IF automatically  didn't create any problem.

It will be care of user, if he assign, the wrong script, to these keys, it doesn't need to be a limitation of the Software.

There are several points in WT that allow, what is not normally allowed, i.e call field characters, or defining a Contest as MIXED, even it's in not really available i.e. CQWW MIXED, or ROVER,
all these selection are care of the user, well why the F1-F7 CQ Message repeat properties can't ??

It could be easy, don't check if any script is assigned, and simply execute the press of the key after the defined time ......

Well this is only a user digression, i can't change the way to think of the Dev, guys .....


About the TS590, could be a good choice, but i prefer to enjoy the radio, that playing with a toy. So thank's for the suggestion, but for now i can still alive with K3, with or without CQ repeat
i  still can press the keys with the fingers !!

Good luck !

73 de Fabio I4UFH


Il giorno 16/set/2013, alle ore 22:31, "Bob Wilson, N6TV" <n6tv at arrl.net> ha scritto:

> I could change the scripts so that they still passed the F1 to Win-Test, but then you would have to program identical messages into the PC (Win-Test) DVK and the K3 DVR, to get the timing right.   You would also have to mute the PC speakers or plug an empty cable into the headphone jack.
> 
> Note however, that the repeated CQ will not call the script again, so it wouldn't be able to issue a command to the K3 again.  Also, when you start typing a callsign, the Win-Test internal keyer would stop, but no script would be called to stop the K3 DVR from repeating. 
> 
> Yes, you could try to assign a different script to every single number and letter on the keyboard, to halt the repeating CQ (37 LUA scripts A-Z, 0-9, /), but there's no way to tell if repeating CQ is active, so it may have to issue a "Halt Repeat" to the K3 every time you press a key, which could have unwanted side-effects.
> 
> In sum, the way I have proposed already is your best alternative.  Anything else requires far more enhancements to Win-Test than you might imagine.
> 
> I do suggest asking the Elecraft developers to provide more granularity to the repeating DVK message timer.  2 seconds is too short and 3 seconds is too long.  You really need about 2.3 to 2.5 seconds.  I've asked Elecraft, but they haven't made it a priority because so far, I think I'm just about the only one who has asked them to enhance the timer.
> 
> Maybe you should sell the K3 and get a TS-590S or similar which includes its own built-in USB Sound card that Win-Test can use like an internal sound card DVK.  Then repeat mode would work OK and RFI issues would be minimal compared to using a normal PC sound card.
> 
> 73,
> Bob, N6TV
> 
> On Mon, Sep 16, 2013 at 12:30 PM, I4UFH <i4ufh at libero.it> wrote:
> Hi Larry,
> 
> I am not buggy .... i am realistic, even i can understand the developer point of view , where if the key lost it's primary function
> all the related function are not more available, i.e.  F1 works as expected and REPEAT MESSAGE too, because F1 has it's
> basic function defined from the developer.
> 
> Otherwise when u assign a script to the F1 all the related functions assigned to this key are not available.
> So i expect that when a Fx key is script assigned it is disabled in the REPEAT MESSAGE menu
> to avoid that the user think, that this function is still available.
> 
> So in this point of view, the REPEAT MESSAGE function must be so flexible to be assigned to any key, ( not only Fx ) where the user
> had defined the DVR script. Generally one user can assign the DVR script to the keypad numbers, and the REPEAT MESSAGE must
> allow to select which key has been defined from the user, in this example the keypad numbers.
> In this overview the Fx REPEAT MESSAGE is only a special case.
> 
> 
> 
> about WAIT, well u know what i mean, the sleep freeze WT so u can't type anything or
> ckick in any windows, because WT didn't execute keyboard and mouse event.
> 
> What i need is to send to the Radio ( K3  )  a sequence of K3 commands, and some time i need
> to wait, the execution of command before sending the other one, all in one script, so sort of wait
> command, that didn't interrupt the WT execution.
> 
> The Timer as u had described,  is a sort of delay before starting the script ... may be can be useful into a chaning
> script, but i am not a guru into LUA dev.
> 
> Thank's for ur time, to take care of these unique needs ..
> 
> 73 de Fabio I4UFH
> 
> 
> Il giorno 16/set/2013, alle ore 20:26, Laurent HAAS - F6FVY <f6fvy at free.fr> ha scritto:
> 
> > Hi Fabio
> >
> > Le 16/09/2013 19:48, I4UFH a écrit :
> >
> >> u mention to use the repeat function of the K3, and is a workaround ,
> >> the reality is that the REPEAT MESSAGE in WT,
> >> is buggy, it's doesn't take care if there a scripts attached to the Fx
> >> keys. It works only properly with it's own sound card
> >> DVK. Really annoying .....
> >
> > Actually, I think _you_ are buggy. ;-)
> >
> > You just don't get that the keys involved for the scripts are totally decorrelated from their former usage in Win-Test. If you choose to attach the F1 key for another customized usage, consequently, the Win-Test core processing for this key will be totally disabled.
> >
> > Regarding the wtApp:Wait function, it does what is expected : It just "waits"...
> >
> > I'll check later if I can include some form of 'timer' to trigger scripts after a certain amount of time, without risking a deadlock.
> >
> > 73
> >
> > Larry - F6FVY
> >
> > --
> > If you're not paying for something, you're not the customer; you're the product being sold.- Andrew Lewis
> >
> >
> >
> > _______________________________________________
> > Support mailing list
> > support at win-test.com
> > http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
> 
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
> 
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20130917/6ebb1a8d/attachment.html>