New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting 2 #104
Comments
Hi cgfan, Your problem is well-known. The column sorting is a nasty issue, however in another way as the one you described. What you need is almost no effort. It has been "sloppy" programming by whoever created that code... Then, where's the "nasty" problem? This really looks not nice at all. In any case, the correct sorting will be included in the next version. The sorting indication would be a separate issue. BTW, this issue might affect also other tables, which I will investigate. Regards, |
Should work in 4.1.1 |
Hi cgfan, many thanks for this quick test. The behavior was (half) intended, as that table was not considered to need a permanent update of the sorting. However, in a dynamic environment this would be at least confusing. Therefore, I put an updated new version 4.1.2 into the "Download" which should fix this. I also considered your comment about showing the sorting triangle only after first user action. The "History" page got a remark about the new version, nothing else. Clem |
Hello Clem, Thanks for 4.1.2. Regards, |
Thanks for feedback. I close this. Clem |
Hi Clem,
By chance, under special DX conditions, I wanted to know how to sort each transmitter site by distance:
What one would expect is this for the ascending case:
This is another sorting problem:
It is the km column of the TII tab.
It is not an issue of QIRX, it is an issue of the control (WPF DataGrid?) because the default sorting algorithm of the control doesn't sort numerically.
Here is a link to a raw file containing this case:
10B-rbb-raw-file
You can check it if you change the OwnPosition line in the qirx4.config file to:
<OwnPosition Latitude="52.131489" Longitude="11.633654" />
Maybe you can think about a custom sorting for the km columns when you work on the other sorting problem (#102).
Regards,
cgfan
The text was updated successfully, but these errors were encountered: