Replies: 2 comments 2 replies
-
I'm still optimizing it, so it's not the final form. But the changes will be only about an optimization of algorithm. I just have one note. In general, testing branches are used for development. The database model can be changed and the code in them is intended only for "development". It is not a beta version, it is actually an integration version. That's why I don't recommend to use it as "main log". it may happen that QSOs in the database may be corrupted. I'm trying to prevent this from happening, but testing breach goes through a long test in the end of development phase and the final version is already the version in the main branch.
I will think about it. I would like to ask you. When I say "Confirmed QSO". Do you accept also eQSL as a confirmation? From my perspective, "confirmed QSO" is QSO that is confirmed only by paper QSL and LoTW, but I would like to ask you how you see it. |
Beta Was this translation helpful? Give feedback.
-
Ok, as long as you do NOT include eQSL by default :) Richard |
Beta Was this translation helpful? Give feedback.
-
Hi @foldynl,
I have looked at your testing_0.18 on Linux. The adjustment to the matrix under the DXCC TAP is very good.
I suggest you alter the QSO detail window, including the DXCC Tab also there. This gives the user an easy access to the DXCC status for the entity the call belongs to.
73 de LB2EG Richard
Beta Was this translation helpful? Give feedback.
All reactions