#25 new

New user interface

Reported by Mike | August 29th, 2010 @ 11:38 AM

I heard on teamspeak that you want to rearrange the GUI a little.
Here are some suggestions if you do not mind:

-there is really no need for the HUD frequency displays. -the frequency and smeter information can be an additional layer on the main window waterfall/scope display -band selection can be done with band markers on the bandscope layer -use of selectable colors for background and data representation layers

With one integrated window per band, it becomes easier to manage multiple windows for the future 8 receiver fpga code.

Comments and changes to this ticket

  • mcdermj (at xenotropic)

    mcdermj (at xenotropic) August 30th, 2010 @ 05:49 AM

    The UI change that I was mentioning on TS was regarding the Main/Sub receivers. It occurs to me that having a Main/Sub distinction is a throwback to analog radios which only have the circuitry for a couple of receivers on board. That assumption is thrown out when using an SDR like OpenHPSDR. What I want to do is get rid of the Main/Sub, and just have Receiver 1, Receiver 2, etc. You will be able to put as many receivers in a passband as you like (and that you have CPU in your computer for). Currently, the main receiver is always in the center of the display and determines the location of the passband. I want to break this dependency and have the passband move separately. So, the main receiver will act like the subreceiver does now when you drag it around and such. When you drag outside of either of the filters, you'll actually scroll the passband.

    Additionally, while I'm doing all of this CoreAudio stuff, I'm thinking that I want to make each receiver have an individual output device control. This way you could have receiver 1 going to the on-board audio, and receiver 2 into a set of headphones. Or, more usefully, receiver 1 going into cocoaModem, receiver 2 going into your FLDigi, etc.

    So, that was what I was opining about on TS. That being said, I don't mind suggestions at all.

    As far as the HUD frequency displays, they serve a purpose because they not only display current frequency, but they allow you to type in new frequencies for direct tuning. You seem to really not like the HUD displays in general because pretty much all the functionality on them can be done in the main window. This is part of the reason they are able to be closed. If you want to run all in the main window, you can just close up the HUDs and they'll be out of your way. This setting probably isn't remembered in the preferences, so maybe I have to make that sticky.

    Frequency selection is already possible on the bandscope by clicking anywhere in it. It will tune you to the frequency on which you click. The shades parts are the ham bands.

    I'm hesitant to throw frequency and smeter on the main display because I'm loathe to make it a busy place. One of the things I didn't like about PowerSDR and many other apps I've seen is that their displays are so busy and have tons of buttons all over the place. The trend seems to be to emulate a Yaesu FT-5000 and have every knob and switch available. The other problem is that if I do implement the many receivers paradigm, there would need to be an smeter and frequency display for each one, which is going to get really cluttered really quickly.

    For the frequency, how would you feel about having some sort of hover-over that displays when you are over the filter of a receiver that displays the carrier frequency of the receiver?

    Things to think about.

  • Mike

    Mike August 30th, 2010 @ 02:41 PM

    I hear you. Many receivers in the same passband sounds good.
    I was thinking a frequency display a la QtRadio. That is also a form of HUD, but within the main window itself.

    Anyway, the audio routing sounds excellent. Will you integrate some cocoaModem modules into MacHPSDR or just send audio to cocoaModem?
    Regarding the smeter, it can be color represented within the scope itself. No need for a standalone meter.
    Hover-over frequency information works for additional receivers, however the main RX / TX Frequency should always be visible.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

An open source software project implementing an amateur radio receiver for the OpenHPSDR hardware.

Shared Ticket Bins

People watching this ticket