[DXLog.net - Support] Shift Binds to Opposit Radio (when using two keyboards)
Martin LU5DX
lu5dx at lucg.com.ar
Wed Oct 19 17:35:33 CEST 2016
Actually, when you do that DXlog.net is smart enough to ping-pong the
focus between the two callsign entry fields.
Not sure how it's done though, but even if Chris, is not giving each of
the callsign entry fields focus explicitly, that is what's happening in
the background.
I mean that's the way Windows controls work.
73,
Martin LU5DX
El 19/10/2016 a las 12:12 p.m., José Nunes CT1BOH escribió:
> You can do the following exercise:
>
> In keyboard1 select letter A
> In keyboard2 elect letter L
>
> Not push both letter at the same time
>
> What do you see?
> radio1 log field will be populated with AAAAAAAAAAAAAA
> radio2 log field will be populated with LLLLLLLLLLLLLLLLLL
>
> This is focus to both log fields at the same time
>
>
> 73
>
>
> On Wed, Oct 19, 2016 at 3:56 PM, Martin LU5DX <lu5dx at lucg.com.ar
> <mailto:lu5dx at lucg.com.ar>> wrote:
>
> Hi José,
>
> I think keyboards still do have focus, despite the fact that
> DXlog.net knows where to route key presses.
>
> Not knowing the details of the code, to me, it seems as though the
> focus is on the keyboard of the last key pressed.
>
>
> 73,
> Martin LU5DX
>
>
> El 19/10/2016 a las 11:46 a.m., José Nunes CT1BOH escribió:
>
> Luca
>
> With two keyboards development in Dxlog.net, your comment ----
> "* command
> does not work anymore" does not apply because the two
> keyboards have focus
> all the time. Everytime you type something in keyboard1 or
> keyboard2 it
> goes correctly to the respective radio1 or radio2 log field.
>
> In 2BSIQ (Two bands synchronised interleaved QSO) mode, with
> two keyboards,
> you loose log field focus (because of the reason I told above)
> but you
> still have Audio focus and next action focus:
>
> Log field focus - not needed with two keyboards
> Audio focus - what you are listening (R1R1; R1R2; R2R2)
> Next Action focus - What radio will get next decision (F1;
> Insert; Plus) in
> the two QSO synchronised moment.
>
>
> Remember 9A5K promised to develop a two QSO field box with
> information to
> what radio has next action focus.
> Right now we know what the next action focus is by looking at
> the blinking
> cursor (that poses problems when we want to edit oposite radio
> log field)
>
> 73 José
> CT1BOH
>
>
>
>
>
>
>
> On Wed, Oct 19, 2016 at 1:27 PM, Luca NCJ <ik2ncj at gmail.com
> <mailto:ik2ncj at gmail.com>> wrote:
>
> Another situation is that * command does not work anymore
> properly with 2
> keybs if you want to move focus from r1 to r2
> All this is caused by focus handling that now is
> controlled by the keys you
> are pressing skipping regoular focus routine for 1 keyb
> setting.
>
> **** Luca IK2NCJ ****
>
>
>
> 2016-10-19 14:04 GMT+02:00 Martin LU5DX <lu5dx at lucg.com.ar
> <mailto:lu5dx at lucg.com.ar>>:
>
> Hello Chris,
>
> I've been trying to use my keyboard with Macro Keys to
> send messages in
> the opposite radio when using two keyboards, but I was
> not able to do it.
>
> There are times, depending on the CW speed of the
> caller, when two hands
> are needed to type fast enough and come back to the
> caller with no delay,
> at the same time you may need to finish a QSO on the
> opposite radio or
>
> hit
>
> F1 to call CQ Test.
>
> Having the ability to send messages on the opposite
> radio without any of
> your hands having to go to the other keyboard would be
> really great and
> would help reduce the fatigue induced by the increased
> auditory and
>
> visual
>
> spatial awareness needed when changing from keboard to
> keyboard in the
> middle of QSOs (beyond what's expected to help
> increase auditory spatial
> awareness, that is: typing callsigns).
>
> In other words. Two keyboards have pros and cons.
>
> On one hand you have more flexibility and it helps
> increase the auditory
> spatial awareness.
>
> When it comes to typing callsigns it helps the brain
> correlate what's
> being typed with what's being heard on each audio
> channel (headphone).
>
> Now, if you are typing a call, with your vision
> focused on a keyboard and
> in the middle of the typing you have to change your
> visual focus from
>
> one
>
> keyboard to another to just press Enter, Plus, F1 or
> whatever, that
>
> reduces
>
> your capability of focusing what you are hearing and
> typing a lot more
>
> than
>
> if you could press a key on the same keyboard your are
> typing the
>
> callsign
>
> to achieve the same result.
>
> Hope you can implement some exceptions to the keyboard
> assignment so that
> this feature can be used when using two keyboards.
>
> Of course there are mutant intergalactic lids like Dan
> N6MJ that may not
> even need this feature, but for humans, it may really
> help.
>
>
> Tnx much!
>
>
> 73,
>
>
> Martin LU5DX
>
> _______________________________________________
> Support mailing list
> Support at dxlog.net <mailto:Support at dxlog.net>
> http://www.dxlog.net/mailman/listinfo/support
> <http://www.dxlog.net/mailman/listinfo/support>
>
> _______________________________________________
> Support mailing list
> Support at dxlog.net <mailto:Support at dxlog.net>
> http://www.dxlog.net/mailman/listinfo/support
> <http://www.dxlog.net/mailman/listinfo/support>
>
>
>
>
>
>
>
> --
> José Nunes
> CONTEST CT1BOH - http://www.qsl.net/ct1boh
More information about the Support
mailing list