User interface
Posted: 14 Nov 2020, 08:32
Hello
what disturbs me and which bothers me the most is the fact of not knowing if I have already contacted this call in this band and this mode
For example : for me in the top left part, as I entered a call, we can think that this will display everything related to this call
we see "WKD BEFORE" but it is not true, I never contacted 7Q7RU on 17M in USB as you can see it in the window "WORKED BEFORE" at the bottom of the screen
well, I understood that in fact the display made here corresponds not to the call but to the DXCC
it is not really ergonomic or coherent...
The example shows that I have already contacted Malawi on 17M in USB but never this call, but it is an expedition, the "challenge" is to try to contact this new expedition, and therefore it is not easy to know if we have already contacted him
I propose an idea based on Logger32
In a single view we have all the necessary information
characters in red = QSO confirmed
blue characters = unconfirmed QSO
Green background = this is the call that validates this band and this mode
for example :
on 17M in CW it is indeed the entered call (here T6AA) which confirmed the QSO (Green background AND CW in red) on the other hand on 12m CW this DXCC was indeed confirmed but the entered call was not contacted and on 30M CW a qso has been carried out AND has not been confirmed AND it is not the entered call that has been contacted.
of course if I click in one case I see the detail of the corresponding qsos
For me this is the biggest problem of Log4OM (With the management of alerts)
of course I am not asking to do exactly the same as in L32 but to think of something similar
So I would like to have your opinion, if you plan to review this part ...
Thanks and 73
what disturbs me and which bothers me the most is the fact of not knowing if I have already contacted this call in this band and this mode
For example : for me in the top left part, as I entered a call, we can think that this will display everything related to this call
we see "WKD BEFORE" but it is not true, I never contacted 7Q7RU on 17M in USB as you can see it in the window "WORKED BEFORE" at the bottom of the screen
well, I understood that in fact the display made here corresponds not to the call but to the DXCC
it is not really ergonomic or coherent...
The example shows that I have already contacted Malawi on 17M in USB but never this call, but it is an expedition, the "challenge" is to try to contact this new expedition, and therefore it is not easy to know if we have already contacted him
I propose an idea based on Logger32
In a single view we have all the necessary information
characters in red = QSO confirmed
blue characters = unconfirmed QSO
Green background = this is the call that validates this band and this mode
for example :
on 17M in CW it is indeed the entered call (here T6AA) which confirmed the QSO (Green background AND CW in red) on the other hand on 12m CW this DXCC was indeed confirmed but the entered call was not contacted and on 30M CW a qso has been carried out AND has not been confirmed AND it is not the entered call that has been contacted.
of course if I click in one case I see the detail of the corresponding qsos
For me this is the biggest problem of Log4OM (With the management of alerts)
of course I am not asking to do exactly the same as in L32 but to think of something similar
So I would like to have your opinion, if you plan to review this part ...
Thanks and 73