Replies: 6 comments
-
it looks good at first glance. However, I have to wonder if it can be implemented with regard to the IARU regions and their bandplans. QLog is starting to be used around the world and I'm just waiting for someone to write that the QLog's internal bandplan is incorrect because he/she is from a different region than Europe. Briefly I have seen, there are no big differences in the bandplans, but I have to look at it in more detail. Thanks for the your idea. |
Beta Was this translation helpful? Give feedback.
-
Yes, that is generally a problem. It's also something that many people don't need. It only makes sense if I actually work via the QLog bandmap. From my point of view, you can also do without an automatic system here and use a manual frequency table, similar to CQRLog, for the few standard modes in the shortwave band plan. Everyone can then enter the specific ranges they need in the table. Otherwise you would generally have to store all band plans in the database, which in my view would be too time-consuming in relation to the benefits. I have no overview of what operating modes are required for the higher frequency ranges. I have also not looked to see whether and how this is implemented in the bandmap in other logbook programs. It would be visually clear if only the area that is actually selected as a mode was marked discreetly. But this is not an urgent feature, so you have any time to think about it. |
Beta Was this translation helpful? Give feedback.
-
Hi, I enclose a screenshot of the bandmap widget and of the band plan set up screen, where the user, among other values, can define the color shown in the band map. 73 de LB2EG Richard |
Beta Was this translation helpful? Give feedback.
-
I like your first image (bandmap). Not so much the second image, because that's exactly what I wouldn't want QLog to be - the settings of each parameter of application. The bad thing is that without the second image I am not able to accurately implement the beautiful bandmap in the first image - see the reasons above. Another question is what about the segments that are "shared" - multiple mods are allowed. This discussion is definitely worth noting |
Beta Was this translation helpful? Give feedback.
-
I have tested both coloring variants, and I think the variant below is more noticeable. What do you think? If the color was all over the bandmap, it affected the readability of the callsigns. |
Beta Was this translation helpful? Give feedback.
-
From my point of view, the design of the bandmap should fit into the overall GUI. I like the clear design of the QLog interface, without the usual overload of colors in the Windows world. These usually make the interfaces rather confusing and restless. The GUI design of QLog is therefore more oriented towards the habits of Linux users and therefore differs pleasantly from some Windows programs. The complete coloring of the bandmap, as shown in Figure 1, goes in this direction. If this is implemented, it should be possible to switch it off individually in the settings. The narrow strip, as in the last two pictures, is very clear and easier to recognize. It is also not necessary to color all the strip segments, as you only need the segment that you have selected as the mode. This reduces the coloring to just one color, as in the last two pictures. It also significantly reduces the effort required to set individual band segments depending on the region. All in all, I am a fan of clear and uncluttered user interfaces with as little color design as possible. Hence this individual opinion of mine. I think the wishes of many Windows users go in a different direction. If you also want to develop the GUI in this direction, you should make it possible to select the previous GUI design in the settings. |
Beta Was this translation helpful? Give feedback.
-
The bandmap displays the band range that is specified under "Settings, Bands".
In this area, the Spots are displayed according to the DX cluster filter setting. It often happens that stations are displayed in the bandmap that are outside the selected mode section (here CW).
One idea would be to leave the display as it is, another would be to mark the band sections visually to make orientation easier. You could mark all band sections in the display area of the bandmap, or just the section for the selected mode, which I personally think is the better solution.
In my opinion, the display should be unobtrusive so as not to visually overload the GUI of the bandmap and also so as not to increase the dimensions of the bandmap window. I have created some examples of this, but I don't particularly like all of them.
In my view, these examples seem too overloaded. It is also sufficient to only select the section for the selected mode.
I would like the small gray / or colored stripes and especially the last example.
But perhaps there are other, better-looking variants.
It is just an idea for an inconspicuous addition to the bandmap and is not necessary for the function. As with everything, it's a matter of opinion. So you don't have to implement it.
Beta Was this translation helpful? Give feedback.
All reactions