HI Edson,
some comments in line below.
On 09/03/2017 16:54, Edson W. R. Pereira wrote:
1. The band selector can go up to the menu before the mode menu.
This will be difficult, on Mac and some Linux Desktops the menu is not
rendered by Qt and cannot contain non-traditional UI components like
line edits and combo boxes. What is the reasoning for moving this
control onto the menu?
1. The rig status light can be turned into a QLabel and should go to
the status bar with the text "Rig" in it. Colors should be the
same as the current light indicator. Plus grey if no rig is
currently selected.
This is a good idea. The current button, yes it is click-able, takes up
more UI space than is necessary. If it were changed to a simple
indicator in the status bar then I would suggest adding a menu action to
reset the rig control.
The input level slider can be eliminated
This has had some recent discussion. Keeping it does have some merit but
perhaps not with the current functionality which is a master level
control for the waterfalls. It could be come an adjuster for the o/s
audio device level although adjusting that level away from 0dB FS has no
advantage. Maybe remove it and add the o/s audio device fader level in
dB to the status bar -- this is not totally straightforward as there is
no notification of changes available.
The level meter can be flipped horizontally with the same width as the
frequency indicator, replacing where the DX Call and DX Grid labels
and text inputs are currently located.
Due to the decodes windows requiring as much vertical space as possible
we must be careful not to add extra height to the bottom sections. Are
you proposing to drop the Call and grid labels from the UI?
The DX info widgets and log buttons should be moved to the bottom of
the center area in dedicated widget group (next to the QSO area).
What are the "log buttons"? It should be noted that the lower centre
area is very full, this does not become apparent until a a mode like
fast JT9 is selected. This change would probably reduce the space
available for decodes.
The frequency label, horizontal level meter, and time label should be
moved to the right border of the main window.
This would be reasonably intuitive if the band selector/frequency input
was there too but I believe this will increase the horizontal width with
no obvious advantage.
The QSO TabWidget should be replaced by a StackedWidget. The selection
of which QSO interface to use will be in the general settings window.
This will free up the space currently being occupied by the TabWidget
"ears".
I would suggest that if this were done then a pair of checked actions in
the "View" menu should be used to select rather than burying the option
in the settings. I would also suggest that the tab one "Generate Std
Msgs" button does not really earn its place on the UI and I have
wondered several times if it could be dropped in favour of automatically
regenerating the messages when the "DX Call" line edit changes.
The time bar graph in the status bar seems redundant and should be
removed as it looks strange to have a bar graph in the status bar. Or
it can be replaced by a QLabel indicating that audio is being recorded.
Progress bars in the status bar are not that uncommon, in fact the Mac
OS X native progress bar is particularly narrow making this usage
compatible with their UI guidelines. It is a stretchable element so does
not take up much space.
A label indicating that audio is being recorded is almost to implement
due to the way WSJT-X deals with saving .WAV files, they are always
recorded but are discarded later if there is no reason to keep them.
This decision is made around 3/4 through the next T/R period.
Not trying to shoot down you suggestions, just adding some
implementation constraints that would effect them.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
