search

nobletoll / powersdr-if-stage

Automatically exported from code.google.com/p/powersdr-if-stage
Other
0 stars 0 forks source link

Disable all hardware types (Demo, Flex-5000,etc) except for SDR-1000, so that no other hardware can be selected. #173

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Disable all hardware types (Demo, Flex-5000,etc) except for SDR-1000, so
that no other hardware can be selected.

This is the biggest problem area because people who do not read the manual
do not select the right hardware type - ever.

Original issue reported on code.google.com by mccleme...@gmail.com on 25 May 2010 at 2:51

GoogleCodeExporter commented 9 years ago 
The PSDR ui is less than optimal for non-Flex hardware.
PSDR/IF needs a ui more attuned to the transceivers it attempts to support; 
even then the idiosyncrasies of the K3, for example, must be reconciled with 
those of Kenwood et al.
I have been removing unused, unwanted code to optimise my PSDR/IF + K3 
experience and looking through my source I have an early version without the 
Flex hardware options, not even SDR1000 - it uses only 'this.hw is RigHW'.
Might that be a head start?

Original comment by f5...@orange.fr on 17 Jun 2010 at 11:04

GoogleCodeExporter commented 9 years ago 
I agree that the UI isn't optimal for non-Flex hardware. And as a developer, we 
certainly have the benefit of understanding how things work "under the covers", 
so we (developers) aren't likely to have a misunderstanding of what a 
particular button/control might do. 

That being said, I realize that for some people, they would be overwhelmed by 
the UI. But, its not currently a goal to refactor the entire UI to make sense 
for every radio it connects to. Not because its not possible, or not useful, 
but we have many other areas we could attend to first, including features that 
we would find more useful. 

The point of this particular defect was to disable hardware selections and 
check the RX only box in the setup menu, because this always causes problems 
that cause PowerSDR/IF Stage to flat out not work. Some of the other controls 
that aren't useful (like BCI Rejection) at least do no harm when they are 
toggled. 

I am sure many people would find it easier if we stripped away stuff, but hey, 
I would rather people play around, experiment, kick the tires and get to 
understand why things work the way they do. Even though some people didn't 
develop PowerSDR/IF Stage, I think one can learn alot from it thinking about 
why something works or doesn't.

Original comment by mccleme...@gmail.com on 17 Jun 2010 at 12:57

GoogleCodeExporter commented 9 years ago 
Scott, not to mention the extreme pain it would be to merge latest PowerSDR 
code to PowerSDR/IF Stage if all that code was stripped and modified heavily.

Original comment by cgates...@gmail.com on 17 Jun 2010 at 1:30

GoogleCodeExporter commented 9 years ago 
I think what Chad did with the collapsed view is really good and hides all 
(most?) of the unused controls as well.  I know I only use collapsed view these 
days.

I would love to redesign out the whole console, like the IC-7800, where the 
S-Meter (which also needs work to look good) is directly under/inline with the 
VFO frequency.

Original comment by mccleme...@gmail.com on 17 Jun 2010 at 2:55