Appearance's Min/Max boundaries shouldn't use column's estimator · Issue #2621 · gephi/gephi · GitHub
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

Appearance's Min/Max boundaries shouldn't use column's estimator #2621

Closed
mbastian opened this issue Sep 9, 2022 · 0 comments
Closed

Appearance's Min/Max boundaries shouldn't use column's estimator #2621

mbastian opened this issue Sep 9, 2022 · 0 comments

Comments

@mbastian
Copy link
Member

mbastian commented Sep 9, 2022

When using Appearance's ranking on a dynamic column the min/max values used for the boundaries are using the column's estimator. That can be the expected behavior in some cases but is probably not the main one. What we rather want is take the min/max within the dynamic attribute (i.e. reviewing each value).

Expected Behavior

Min and Max values within dynamic attributes are used, instead of estimators.

Current Behavior

Ranking min/max always use the column estimator.

Possible Solution

It could be an extra configuration we display for dynamic columns. Estimator selection is anyway buried in the timeline component so it would be handy to display it there, to make it clear what is used to compute the values.

Steps to Reproduce

  1. Open 2node.gephi.zip
  2. Select Size > Ranking > metric in Appearance
  3. Apply at different timeline slices.
  4. Size doesn't change even though the values change.

Context

Reported on FB group by Andy B.

Your Environment

  • Version used: Gephi 0.9.7
  • Operating System: Mac OS
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

1 participant