Closed shahrilnet closed 5 years ago
Does this take into account my refactor that I push a little bit ago?
Yes, I've merged your commits (little while ago) with mine.
OK, cool. I'll review it in a little bit and give @10110111 a chance to comment too! :-)
Thanks again, this stuff is looking great.
You're welcome, happy to contribute a little bit. :)
Some comments on the whole changeset including the previous (merged) one follow.
The following screenshot demonstrates both above mentioned problems:
The arrows in the following screenshot look confusing:
The arrows for untaken branches are asymmetric with respect to their path line:
The following display is misleading: I've actually come to this state by stepping from 0xf7fd7817 (skipping the conditional jump), but the red arrow hints as if I have just jumped here from 0xf7fd77fb. Maybe the arrow from the origin shouldn't be painted red.
1)
Arrow there is red highlighted because there is a direct jump from 0xf7fd77fb, the reason why I do highlight it is to give a clarification that this jump to this address is always taken
Edit: Fixed. Now arrow will not be red highlighted if arrow destination is EIP
2)
I've fixed this by adding more horizontal length to one of the jump blocks if it is overlap at the edge.
3)
Fixed where jump now points to the middle of instruction (see screenshot above)
4)
I have removed anti-aliasing code. If @eteran has other to say I will add it back.
Thank you for all the comments, really appreciated it. :)
I have removed anti-aliasing code.
I think the arrow tips could benefit from antialiasing. It just has to be enabled in QPainter
right before that code and disabled afterwards. Just be sure to make them still look symmetric (note that in antialiased case the samples are offset by 0.5 px).
@10110111
As per your suggestion, I've enabled anti-aliasing when only it is time to draw arrows. Arrow tips also now drawn in full area (using QPainter's fillpath)
I'm OK with these changes now. I was thinking of some pixel-hunting tweaks, but I suppose I'll simply make a follow-up PR when I finalize my ideas.
@10110111 's review has proven to be very worth having! Thanks to both of you. This PR looks great to me. I'll probably merge later today.
Previously, some jump arrows might be overlapped or being so close together (which makes it not to look nice).
This PR attempted to fix that, and now all jump arrows fit nicely. :)