[chirp_users] [CHIRP] #105: Bug Setting "default" frequency to last frequency edited..
#105: Bug Setting "default" frequency to last frequency edited.. ----------------------------------------------+----------------------------- Reporter: Robert Terzi <rct+chirp@…> | Type: Bug Status: new | Priority: Cosmetic Milestone: | Component: Memory Editor Version: 0.1.11 | Keywords: Platform: Linux | ----------------------------------------------+----------------------------- I find it confusing that when I start entering a new frequency, by typing the name since it's the left most column, what ever frequency was last in focus gets automatically filled in. If I'm going fast enough I might not realize that I didn't type that frequency in and it isn't the one I want.
I'd really like to see that have an undefined value if I've never set it. Alternatively if I type a name first, and there is no valid frequency yet, force the focus to be the freqency field.
Another manifestation of this problem is if I double click on the name field of a frequency that isn't in use it creates a new frequency memory for me with that seemingly random (last freqency entry that had focus for editing).
#105: Bug Setting "default" frequency to last frequency edited.. -----------------------------------------------+---------------------------- Reporter: Robert Terzi <rct+chirp@…> | Owner: Type: Bug | Status: new Priority: Cosmetic | Milestone: Component: Memory Editor | Version: 0.1.11 Resolution: | Keywords: Platform: Linux | -----------------------------------------------+----------------------------
Comment (by kk7ds):
This was discussed a bit on the list, and it has to do with the behavior of chirp when controlling "live" radios. Such drivers flush the writes to the radio in realtime, and the radio does its own validation of the settings. CHIRP used to just use 0.0000 for the frequency until you set it, but that meant that users of the live radios were *required* to edit the frequency to something valid *first* before doing anything else. Similarly, I've recently been trying to do full validation of all that input against the description each radio driver exports about its attributes (including valid frequency ranges) and accepting 0.0000 means that the user could program that to the radio at some point.
Would it be more suitable if the default was (optionally) something like the native frequency of the radio (i.e. 144.0000) or the like?
#105: Bug Setting "default" frequency to last frequency edited.. -----------------------------------------------+---------------------------- Reporter: Robert Terzi <rct+chirp@…> | Owner: Type: Bug | Status: new Priority: Cosmetic | Milestone: Component: Memory Editor | Version: 0.1.11 Resolution: | Keywords: Platform: Linux | -----------------------------------------------+----------------------------
Comment (by Robert Terzi <rct+chirp@…>):
Yes, it would be better to use a fixed default frequency. However, I'd rather see behavior like it being 0, null, and/or having the whole row be considered invalid/greyed out until the frequency is typed.
For what it's worth both FTBVX8 and RT's ADMS-VX8 put the frequency in the left most column, which avoids some usability issues by making the inclination to type from left to right force the user to enter the frequency first. However, neither let you have an entry without typing in a frequency (one won't let you type, the other pops up an error, after loosing what you type in the name field.)
#105: Bug Setting "default" frequency to last frequency edited.. -----------------------------------------------+---------------------------- Reporter: Robert Terzi <rct+chirp@…> | Owner: Type: Bug | Status: new Priority: Cosmetic | Milestone: Component: Memory Editor | Version: 0.1.11 Resolution: | Keywords: Platform: Linux | -----------------------------------------------+----------------------------
Comment (by Robert Terzi <rct+chirp@…>):
I should mention what I'd really like to have happen that doesn't work now is to be able to type the Name, type tab, and have the frequency field immediately in focus so I can type that.
#105: Bug Setting "default" frequency to last frequency edited.. -----------------------------------------------+---------------------------- Reporter: Robert Terzi <rct+chirp@…> | Owner: Type: Bug | Status: new Priority: Cosmetic | Milestone: Component: Memory Editor | Version: 0.1.11 Resolution: | Keywords: Platform: Linux | -----------------------------------------------+----------------------------
Comment (by kk7ds):
Well, requiring the frequency to be set first was the way it behaved right before I added the take-the-defaults behavior. I heard complaints about it from various users, myself included :) I suppose moving the frequency to the left-most column might help that a bit.
So, how about I: 1. Try to make the tab ordering work the way you would expect 2. Move the frequency column to be first 3. Allow an option to take the last frequency, a default frequency, or none (hence requiring you to do the frequency edit first)
I'll admit that this seems like trivolity to me, but I'll try not to complain :)
#105: Bug Setting "default" frequency to last frequency edited.. -----------------------------------------------+---------------------------- Reporter: Robert Terzi <rct+chirp@…> | Owner: kk7ds Type: Bug | Status: accepted Priority: Cosmetic | Milestone: Component: Memory Editor | Version: 0.1.11 Resolution: | Keywords: Platform: Linux | -----------------------------------------------+---------------------------- Changes (by kk7ds):
* owner: => kk7ds * status: new => accepted
Comment:
I've been unsuccessful in beating PyGTK into submission around the tab ordering thing. I have, however, made the frequency column default to be first (after the location) and now allow persistent user-reordering of the columns, which I hope will help a little.
participants (1)
-
CHIRP Tracker