Re: XASTIR cross-port digipeating?

Re: XASTIR cross-port digipeating?

[Wilbert Knol]

Thanks, Lance, for the background on XASTIR digipeating.
I'll have a look at aprsd.

> > What I meant was: a work-around to give me right-click functionality :-)
> > (which worked in earlier versions of XASTIR). I'll have a play with a
> > PS/2 full-size external keyboard.
>
> That's beyond my knowledge of Xastir. Are you saying your computer doesn't
> have a right-click mouse button?

It has, but it won't work under XASTIR.

> If you turn off the warning and still cannot right-click to bring up the
> context menu, then I guess your computer thinks NumLock or ScrollLock is on.

Neither are present on this notebook keyboard. Maybe that's why XASTIR
gets confused.

I guess I should report it as a bug. Otherwise, XASTIR 1.2.1 works well.
Great program.


Wilbert, ZL2BSJ

Re: XASTIR cross-port digipeating?

[Curt Mills, WE7U]

On Sun, 20 Jul 2003, Wilbert Knol wrote:

> > If you turn off the warning and still cannot right-click to bring up the
> > context menu, then I guess your computer thinks NumLock or ScrollLock is on.
>
> Neither are present on this notebook keyboard. Maybe that's why XASTIR
> gets confused.

It would be that the codes getting passed to Xastir from X11 have
modifiers set.  Xastir thinks you have NumLock, ScrollLock or
CapsLock on because X11 is telling it that you do.

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

Re: XASTIR cross-port digipeating?

[Wilbert Knol]

On Mon, 21 Jul 2003, Curt Mills, WE7U wrote:
>
> It would be that the codes getting passed to Xastir from X11 have
> modifiers set.  Xastir thinks you have NumLock, ScrollLock or
> CapsLock on because X11 is telling it that you do.

I changed in the file /etc/sysconfig/keyboard:

   KBD_NUMLOCK="bios"

into

   KDB_NUMLOCK="no"

...and right-clicking now works! Apologies for the mis-directed 'bug'
comment :-)


Wilbert, ZL2BSJ

Re: XASTIR cross-port digipeating?

[Curt Mills, WE7U]

On Mon, 21 Jul 2003, Wilbert Knol wrote:

>
> I changed in the file /etc/sysconfig/keyboard:
>
>    KBD_NUMLOCK="bios"
>
> into
>
>    KDB_NUMLOCK="no"
>
> ...and right-clicking now works!

That probably means that going into your CMOS BIOS and selecting
"Boot with NumLock On = NO" would have also solved the problem,
right?

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

Re: XASTIR cross-port digipeating?

[Wilbert Knol]

>
> That probably means that going into your CMOS BIOS and selecting
> "Boot with NumLock On = NO" would have also solved the problem,
> right?

No...It is a laptop computer.

There is no NumLock key on the keyboard, and, as a result, no BIOS 
option for it.

Anyway, it's all sorted....I am a happy camper.

Wilbert, ZL2BSJ

XASTIR cross-port digipeating?

[Wilbert Knol]

Thanks for reading this message. I am running (amongst other things)
XASTIR on a small, two-port packet system. Is it possible to get XASTIR to
digipeat on one port APRS broadcasts heard on another? Or do I need the
separate 'aprsdigi' mentioned recently? (I have same-port digipeating
working successfully)

Similarly, are there any Internet based APRS servers (preferably in
VK/ZL). Will XASTIR re-transmit on any of the RF ports broadcasts heard on
the Internet interface, and vice versa?

A separate question: XASTIR 1.2.1 complains about NUM/SCROLL/CAPSLOCK
being engaged when I right-click the desktop. My notebook keyboard only
has a CAPSLOCK, and it is off. Is there a work-around for this?

Wilbert, ZL2BSJ

Re: XASTIR cross-port digipeating?

[J. Lance Cotton]

On Saturday 19 July 2003 01:35, Wilbert Knol wrote:
> Thanks for reading this message. I am running (amongst other things)
> XASTIR on a small, two-port packet system. Is it possible to get XASTIR to
> digipeat on one port APRS broadcasts heard on another? Or do I need the
> separate 'aprsdigi' mentioned recently? (I have same-port digipeating
> working successfully)

Xastir doesn't digipeat, except for RELAY digipeating that home stations 
should do. You would need aprsdigi or digi_ned to do any further digipeating.

> Similarly, are there any Internet based APRS servers (preferably in
> VK/ZL). Will XASTIR re-transmit on any of the RF ports broadcasts heard on
> the Internet interface, and vice versa?

What is meant by "broadcasts"? Right now, Xastir will only dump from INET->RF 
messages intended for stations heard locally, their related position packets, 
and any NWS (US National Weather Service) packets that match callsigns listed 
in ~/.xastir/data/nws-stations.txt (only NWS weather report packets are gated 
to RF, so putting any callsign in nws-stations.txt won't cause Xastir to gate 
any matching packet).

> A separate question: XASTIR 1.2.1 complains about NUM/SCROLL/CAPSLOCK
> being engaged when I right-click the desktop. My notebook keyboard only
> has a CAPSLOCK, and it is off. Is there a work-around for this?

Xastir doesn't yet do the right filtering to determine if key modifiers like 
those listed above are enabled, which in some cases (with LessTif, I think) 
causes Xastir not to process those clicks. Look in the menu 
File->Configure->Defaults and un-check "Warn if modifier keys". That will 
disable the message.

> Wilbert, ZL2BSJ

-- 
J. Lance Cotton, KJ5O
joe@lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the 
cookies.

Re: XASTIR cross-port digipeating?

[Wilbert Knol]

Thanks, Lance, for the info.

> Xastir doesn't digipeat, except for RELAY digipeating that home stations
> should do.

That's what I want: relay something I have heard on 2 m on the 70 cm port.
Maybe an idea for a new feature.

> > Similarly, are there any Internet based APRS servers (preferably in
> > VK/ZL). Will XASTIR re-transmit on any of the RF ports broadcasts heard on
> > the Internet interface, and vice versa?
>
> What is meant by "broadcasts"?

A UI frame announcing someone's position.

I have ticked the box that says  "enable Inet->RF and RF->Inet
traffic". This looks like a nice feature. It would be good to make some
meaningful use of this.

Any local Inet gates, in this part of the woods? I don't want to
antagonise the locals by re-transmitting US summer-time WX data :-)

> > A separate question: XASTIR 1.2.1 complains about NUM/SCROLL/CAPSLOCK
> > being engaged when I right-click the desktop. My notebook keyboard only
> > has a CAPSLOCK, and it is off. Is there a work-around for this?
>
> Xastir doesn't yet do the right filtering to determine if key modifiers like
> those listed above are enabled, which in some cases (with LessTif, I think)
> causes Xastir not to process those clicks. Look in the menu
> File->Configure->Defaults and un-check "Warn if modifier keys". That will
> disable the message.

What I meant was: a work-around to give me right-click functionality :-)
(which worked in earlier versions of XASTIR). I'll have a play with a
PS/2 full-size external keyboard.


Wilbert, ZL2BSJ

Re: XASTIR cross-port digipeating?

[Curt Mills, WE7U]

On Sat, 19 Jul 2003, Wilbert Knol wrote:

>
> Thanks, Lance, for the info.
>
> > Xastir doesn't digipeat, except for RELAY digipeating that home stations
> > should do.
>
> That's what I want: relay something I have heard on 2 m on the 70 cm port.
> Maybe an idea for a new feature.

It's on our feature request list, but it's unlikely that we'll get
to that anytime soon.


> > > A separate question: XASTIR 1.2.1 complains about NUM/SCROLL/CAPSLOCK
> > > being engaged when I right-click the desktop. My notebook keyboard only
> > > has a CAPSLOCK, and it is off. Is there a work-around for this?
> >
> > Xastir doesn't yet do the right filtering to determine if key modifiers like
> > those listed above are enabled, which in some cases (with LessTif, I think)
> > causes Xastir not to process those clicks. Look in the menu
> > File->Configure->Defaults and un-check "Warn if modifier keys". That will
> > disable the message.
>
> What I meant was: a work-around to give me right-click functionality :-)
> (which worked in earlier versions of XASTIR). I'll have a play with a
> PS/2 full-size external keyboard.

I believe that depends on your version of Lesstif/Motif/OpenMotif.
They behave differently with respect to the mouse/keyboard
modifiers.  Other people in the past have had trouble getting the
right mouse button to function properly.  That was a while back
though.  Perhaps you're running an old distribution where the
problem showed up?

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"