[chirp_users] [CHIRP] #115: duplex setting getting automatically overwritten when frequency gets focus.
CHIRP Tracker
Wed May 18 11:55:01 PDT 2011
#115: duplex setting getting automatically overwritten when frequency gets focus.
-------------------------------+--------------------------------------------
Reporter: rct+chirp@… | Type: Bug
Status: new | Priority: Stability
Milestone: | Component: Memory Editor
Version: (tip) | Keywords:
Platform: Linux |
-------------------------------+--------------------------------------------
If the frequency field gets focus, the duplex setting gets overwritten
with the band plan duplex for that frequency, even if the frequency
doesn't change.
I first noticed this with 6 meter frequencies. they would loose their
duplex setting if the frequency field gets focus. Note: the frequency
actually hasn't changed, I just double clicked on it. There are no
STD_6M_OFFSETS defined so the duplex settings all got changed to none.
On a 2M frequency that had an offset that doesn't match the standard
offsets, touching the frequency would cause the duplex setting to be
silently changed.
To reproduce:
1. Enter a 6m frequency, 52.500, + offset by 0.500
2. Double click the frequency, observer the + duplex has changed to none.
Alternatively.
1. Enter 147.375, notice that + and .600 get set automatically.
2. Change to - shift.
3. Double click on 147.375 so it gets & looses focus, note the shift
(duplex0 has changed back to +.
First if the frequency doesn't actually get changed, no other automatic
changes should be applied.
Second, I think automatically setting the shift/direction should only
occur the first time the frequency is set. Subsequent changes to the
frequency shouldn't cause automatic defaults to be applied.
Aren't the current set of standard 2m/70cm offsets somewhat US specific?
--
Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/115>
CHIRP <http://trac.chirp.danplanet.com/trac>
CHIRP Development
More information about the chirp_users
mailing list