It sounds like this may be something we can just agree to disagree on and add a checkbox so everyone is happy.
Eric Wachsmann FlexRadio Systems > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, November 07, 2005 3:31 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; 'Tom Thompson'; flexradio@flex-radio.biz > Subject: RE: [Flexradio] Mouse wheel tunning on v1.4.5 pre3 > > > Please see my comments below. > > > [snip] > > > >> The second principle that is not, to my understanding, implemented or > >> planned is that typing a frequency should _only_ take effect when the > >> mouse is over the VFO A _or_ VFO B displays. I have many times wanted > > to > >> directly type something into VFO B. To my knowledge, this can't be > > done > >> without doing the A<>B thing and then A<>B after. Awkward and, in > > some > >> scenarios, counterproductive since you might be listening to A. It > > hurt > >> us a couple of times in the DXpedtion to have the frequency change > > when we > >> happened to have the focus slip from N1MM to the PowerSDR and then > > typed a > >> number. There's workarounds, but it should be harder to make this > > mistake > >> IMHO. Frequencies disappear fast in a contest. For now, I would > > settle > >> for the typing to only matter when the cursor is in VFO A's area of > > the > >> screen. That would help a lot. > > > > > > [Eric Wachsmann] Contrarily, I believe it is useful to be able to key in > > a frequency (in MHz) and hit enter to go there quickly. Having to mouse > > up to the VFO first makes things both more complex and more cumbersome. > > You can still mouse up there and click inside the VFO if you would > > rather have that method of tuning. > > > > Here, my friend, we profoundly disagree. > > 1. I have been hurt by this many times (especially likely, IMHO, when > running 3rd party programs like N1MM and MixW as we increasingly do, but a > problem even before that). It's just too easy to do this by mistake. > > 2. I have _never_ benefitted from it, at least not compared to my > proposal. When making a very gross change in frequency (that's the only > reason I can think of to take the trouble to type a frequency in), moving > up to the VFO A area is not a big added effort, at least not compared to > the number of times I've lost a frequency due to accidently changing it, > thanks to the "type everywhere" of today's design. The added benefit, if > I could get it, of changing VFO B that way would be an even bigger > compensation for the added work. > > > > >> The third principle is that there needs to be an "undo" (perhaps the > > Esc > >> key) that restores the frequency to whatever it was before one started > >> typing. Moreover, the change should not take effect until the typing > > is > >> completed (with, for instance, the enter key). Similarly, an > > incomplete > >> typing (no enter key) should either do nothing or revert after some > > sort > >> of time out, implementor's choice. > > > > > > [Eric Wachsmann] Ask and your wish shall be granted. This was > > implemented in PowerSDR Beta v1.4.5 Preview 1. Try it out. > > > > I gotta catch up, that's for sure. Been hanging back with 1.4.4 and even > 1.4.1 (currently preferred for digial work because it lacks some of the > SSB signal shaping improvements!). > > "Undo" is a big help. Thank you very much for that. But I still don't > want the "type anywhere" functionality for frequency changes. For me, it > is mischief and it doesn't make a lot of intuitive sense to me, either. I > would _expect_ to have to put the cursor into the VFO display to change > frequency anyway. > > Regardless of my intution, I wonder what the collective user community > thinks about this one? Do they like it or do they view (as I do) that the > problems outweigh the benefit? > > > > Larry >
