--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: tk2: over strict PROG limits
- From: Dan Jacobson <jidanni@jidanni.org>
- Date: Wed, 19 Apr 2006 20:20:42 +0800
- Message-id: <20060419122042.3920.69902.reportbug@jidanni1>
Package: tk2
Version: 1.1-1
Severity: minor
Tags: upstream
Bob, I notice tk2 1.1 says (in a message that the user has no way to
cut and paste into this email message), that e.g., PROG4 lower and/or
upper limits are being adjusted (down or up, it doesn't say either) to
fit the step for PROG4. However, that then prevents the perfectly
legitimate wish of some users to e.g., scan
127.55,127.65,127.75,127.85,127.95
without being forced to go from 100 KHz to a 50 KHz step and also get
127.6 etc.
I recall tk2 1.0 didn't behave like that, but there is no changelog
file to say what decisions were made...
Maybe have a box to click if one wants to enforce alignment.
Also, as 9 KHz versions, at least mine, have no step for the AM band,
one must set it by hand each time or else one will get an error when
saving a .tr2 file after reading from the radio.
(Also, "reading complete, look at the radio to see if it displays a
message": well, by that time the message is already gone and the radio
has gone back to saying "clone".)
P.S., spotted some trailing blanks:
cd /usr/share/tk2/
grep -c ' $' *
api2.tcl:20
gui2.tcl:63
misclib.tcl:0
mylib.tcl:8
tk2.tcl:5
(I use emacs' show-trailing-whitespace)
--- End Message ---