-
Notifications
You must be signed in to change notification settings - Fork 257
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
fix sorting order of location in caller callee view #468
Conversation
huh? how does this fix it? you now only sort by the line which is totally bogus? instead, we should use a QCollator in the proxy model for sorting and enable numeric mode on that |
ab1a309
to
f8b036c
Compare
I didn't know that sorting by filename is required. In that case we can leverage |
f8b036c
to
9520607
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please don't inline the code, as it leads to code bloat
9520607
to
0223069
Compare
0223069
to
760ba4b
Compare
9ada156
to
c2e7728
Compare
Rechecked: I can confirm that the resulting appimage fixe the original issue just fine, sorting first the filename (alphanumeric) then the line numbers (numeric). Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
really minor nits, otherwise lgtm now
add a new sfpm for SourceMapModel that implements lessThen to correctly sort the locations fixes: #466
c2e7728
to
f95b0c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm now, thanks
sort by line not by alphabetic string
fixes: #466