Skip to content
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

Do not highlight last bug path message if not absolutely last #1395

Closed
whisperity opened this issue Feb 23, 2018 · 1 comment
Closed

Do not highlight last bug path message if not absolutely last #1395

whisperity opened this issue Feb 23, 2018 · 1 comment
Assignees
Milestone

Comments

@whisperity
Copy link
Contributor

Currently, the last bug path message is highlighted in red colour even if the bug path continues later on in another file. This is true for every file if the bug path jumps back and forth. The red colour makes the user believe it is the reason for the bug report, but sometimes it's just an "Entered call from..." line, sometimes along with many others directly before it, those written in blue.

@gyorb
Copy link
Contributor

gyorb commented Apr 5, 2018

On the long term it would be good to think about coloring based on the "main" section in the report plist as an alternative. The data from there is used at the report listing.
It is possible that the last bug event and the main section point to a slightly different locations, however when the bug paths are shown we just render the event/control nodes from the path and the "main" section is not rendered.

@csordasmarton csordasmarton modified the milestones: release 6.6.1, release 6.7 Apr 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants