Zoom to Segment -- make it configurable

Al_NN4ZZ

Background -- currently the 'zoom to segment" feature displays the entire frequency range for a given segment.  For example on 20M CW the range is from 14.000 to 14.150.   I have found that the current full range display is not as useful as I expected.  The signals are closely cramped together and the full range is more than I am interested in displaying.  I like the zoom to segment idea but don't use it much in the current configuration.  

Idea - Provide an option to configure a sub-segment for a given band/mode.  For example on 20M CW a segment of 14.000 to 14.060 would spread out the signals better, (more than twice as wide compared to the current display).   It would allow us to focus on the part of the segment we are interested in and the panadapter display would be expanded.  

Implementation - There are a number of ways this could be implemented, menu options, tables by band and segment, etc.  Here is a mock up showing a simple and friendly graphical implementation.  The user would only need to configure the bands and modes of interest.  Access to the configuration would be a "right click" on the "segment" icon.  The settings would be saved for any segments that the user has configured.




While there would be tables for the bands and modes behind the scenes, the user interface would be simple, friendly and intuitive.   Would you be more likely to use the zoom to segment feature if you could configure it?  If you think this would be of interest, please add you comments and a vote.  


Al / NN4ZZ  
al (at) nn4zz (dot) com
6700 & SSDR-W  V 2.4.9
Win10


  

David-N5PSM

(YES VOTE)I definitely think there needs to be a change,  I would like to see the "Segment" configurable withing the selected band and mode as you suggest, additionally I believe it would be very helpful to have a "U" "user" button that can be configured as well to anywhere in the selected band limits so out favorite places for a given mode can be just a click away.

Frank Kirschner

Burt Fisher

It is configurable on the Icom-7300

Bill -VA3WTB

that is no help as he is not using a 7300

Al_NN4ZZ

Hi Bill, The IC 7300 provides the user with the capability to configure the segment range. Burt is just pointing it out to confirm that this is a reasonable request and a feature that another vendor also implemented. We were discussing this idea on another forum. I haven’t seen the IC 7300 user interface for this feature so I don’t know if they are using a similar method. But IMHO a graphical “slider” would be a good fit for SSDR . Regards, Al / NN4ZZ

K1UO Larry

hans weijers

Burt Fisher

Exactly Al, exactly. 

Al_NN4ZZ

Hi Larry,
Thanks, a few of them have but you are right, there are a lot of good and popular ideas that have been on the list for 2, 3, 4 or even 5 years now.   

IMHO, there hasn't been a development focus on the SSDR UI.  While there have been some fixes and new features the focus has been on other (more profitable) areas. 

Maybe now that the new hardware and SmartLink are almost behind them, they will be able to look at some of the other enhancements.   

Al / NN4ZZ 
al (at) nn4zz (dot) com
6700 & SSDR-W  V 2.4.9
Win10  

  

Al_NN4ZZ

Hi Hans,
I agree with your  comments on support for other countries and regions.  It seems like some (too many?) features are lacking that last 10% to make them complete and be the best they can be.   I could list examples from the idea list but you probably can think of them too. 

*** Soap box starts here, ignore this section if you prefer ***

One hard lessons I learned when leading a software development team was the importance of design reviews before writing the first line of code.  And the key was to include more than just the IT team.   We included users, marketing, sales, and management.  The IT team didn't like this at first but eventually came to realize that it was easier to get their input before coding than it is to hear about the issues later and try to fix/code for the changes.   Or release a product that doesn't meet their needs and expectations. BTW, it took me many years to figure out that including the wider user community was a good idea.  We initially thought they wouldn't understand the complexity and just confuse  and delay the process.  We were wrong.  

The design reviews had to include mockups of the screens, details on how the feature was implemented, etc.  We would ask the team to tell us what we missed, what would or wouldn't work well, what could be improved.  And we often had to go back and rework the design and review it again.  And often at the meeting the user community would get a better understanding of why something was done the way it was, agree  and not be surprised when it was delivered.   Hans, for example if you were on the review team for the band segment review I'm sure you would have brought up your concerns and they could have coded for it initially.  

I'm not saying that FRS doesn't do design reviews before coding, in fact I'd be very surprised if they didn't.   But I don't know who they include and haven't seen any design docs circulated so it's not the general user population.  Maybe the Alpha testers are also part of the design review team but often testers don't get to see a product until it is coded and delivered.  Changes at that point are more expensive.  Developers are ready to move on, and may resist changes that are more difficult to make at that point. Also testers are often focused more on testing what they get and less on what it could have been.  This is not to say they don't bring up issues and we know changes do get made.  

Why not expand the design review team? -- There is always the concern that competition may see the designs but it is really just a matter of timing, they will see the result eventually anyway.  And NDA's address this concern about releasing detailed information.  There is a concern that design documents and meetings are too costly and take too long.  But the benefit is a better product, fewer user issues, and less cost overall when you consider fixes.   

Anyway this is just my perspective and friendly / constructive comments are welcome. 

**** Soap box ends here ****



Al / NN4ZZ  
al (at) nn4zz (dot) com
6700 & SSDR-W  V 2.4.9
Win10

Rich McCabe

[Deleted User]

W9HH - Steve

snet0311

Same here (think that should be a basic setting, like a simple clock for the Maestro), but i have the feeling nothing moves in any direction from the flex side. Obviously they have other priorities. Just the prices go up ;-(

Karl

Great Idea... And i fully support and Vote a solid YES for this feature.

It would at least be great IF the TURF file would match the country band plan. Being from Canada and using the [S] and [B] and it not showing my band plan is rather inconvenient to say the least.

Karl.

gerryk

+1
Segments will differ based on location and usage pattern