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
TAxis::GetTicks and TAxis::SetTicks are inconsistent. Significantly so. #14256
Comments
I proposed a fix, see link above. |
Code looks good. |
Thanks, I just fixed the explanation. |
guitargeek
pushed a commit
that referenced
this issue
Dec 18, 2023
guitargeek
pushed a commit
to guitargeek/root
that referenced
this issue
Dec 18, 2023
guitargeek
pushed a commit
that referenced
this issue
Dec 19, 2023
maksgraczyk
pushed a commit
to maksgraczyk/root
that referenced
this issue
Jan 12, 2024
vgvassilev
pushed a commit
to vgvassilev/root
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check duplicate issues.
Description
When creating a modified version of a histogram/graph it's useful to have the axis of the new variation emulate those of the original. Something like target.SetXXX( original.GetXXX()) should do the trick. And it does for almost everything. The exception are the Ticks. Where if idol has bits 9 & 10 (kTickPlus and kTickMinus) both false, GetTicks returns '+' which SetTicks encodes as bit 9 on and bit 10 off. This not only messes up the display of the ticks, but also the location of the tick labels and the axis' main title.
I'm working around that by manually called SetBit, so it's no longer a problem for me. But it just seems like an API bug.
Reproducer
ROOT version
Installation method
Built from source
Operating system
Linux
Additional context
No response
The text was updated successfully, but these errors were encountered: