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.

Sign up for GitHub

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

Jump to bottom

Re-entrancy numbers should be consistent #6

Closed
GoogleCodeExporter opened this issue Sep 3, 2015 · 1 comment
Closed

Re-entrancy numbers should be consistent #6

GoogleCodeExporter opened this issue Sep 3, 2015 · 1 comment
Labels
auto-migrated Component-Hooks Priority-Low Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Should find a way to keep re-entrancy numbers in FS display as consistent
as possible across steps. Currently, they often change wildly, which is
confusing for the user. Possible strategy: per rule application, assign
numbers used to specific paths of specific FSs (the mother or a specific
daughter).

Original issue reported on code.google.com by kilian.e...@gmail.com on 21 Jun 2009 at 11:37
@GoogleCodeExporter
Copy link
Author

Original comment by kilian.e...@gmail.com on 5 Jan 2010 at 2:19

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Hooks Priority-Low Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter