[Xastir] Change to RELAY digipeat function

Troy M Campbell troymc at epicalliance.com
Mon May 2 23:27:26 EDT 2005


Wow.

Need to cut down on the caffine some.

As a software developer (of other kinds of software)
I'd usually try to make new changes NOT break old
configurations.   And behavior modification is for customer
support, not ususally (I did say _usually_) the developer.

I'd be just has happy having to enter it as not if it were
clearly documented that I must do so and why.   The
default just keeps me from trying to guess why the thing
doesn't work the first time I install it.  Curt does have a point
about Xasitr not being a U.S. specific piece of software.

Xastir is about the coolest application I've come across,
so I'm just as glad to have it like it is as opposed to not
having it at all.

My $.02.


Troy M. Campbell
Epic Alliance, Inc.


------ Original Message ------
From: James Ewen <jewen at shaw.ca>
Date: Monday, May 2nd, 2005 6:23 PM CDT
To: xastir at xastir.org
Subject: Re: [Xastir] Change to RELAY digipeat function

While we are on this subject, where the #!^&*@ is the command/switch/menu 
item to enable RELAY/WIDE1-1 support?

> Considering how much bandwidth has been devoted to that
> subject,  would it be difficult to make it a 'config file' entry
> that defaults to RELAY if you didn't put anything in there ?

If Xastir defaults to acting as a fill-in digi automatically, I vote for 
having NO default entry, but making the user consciously have to enter the 
alias to use. Defaulting to enabling a poor choice of alias is a bad 
thing...

James
VE6SRV 


_______________________________________________
Xastir mailing list
Xastir at xastir.org
https://lists.xastir.org/mailman/listinfo/xastir




More information about the Xastir mailing list