-
Notifications
You must be signed in to change notification settings - Fork 22
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
New channel type scaling setting diffes from ViewBox scaling display #266
Comments
@mscheltienne I'm not sure what you mean by this |
grad (ft/cm) in the settings shows 400; mark on the viewbox shows 800 fT/cm. |
ah I see. but that is also controlled by the independent
The scale factor is adjusted by the eyeglass icons at the top of the browser. We can remove those and the user will have to control the scaling of each channel type manually. Or add a checkbox for whether to use the scale factor or purely use manual adjustment |
One option would be to get rid of But that's a bit of a separate issue from whether or not the magenta scale bar matches the chosen scale factor. I think it probably should. In other words, it's twice as large as it should be at the moment, so we can just make it half the size (it could extend upward from the baseline/zero, or extend halfway above and halfway below the baseline). |
Should this be fixed in #268 or a separate PR? |
Could go either way... I would probably keep them separate until we converge on how to harmonize. In the meantime we can know that there should be a factor of 2x difference between the two when testing interactions in #268 |
I would do 2 separate PRs |
I fixed this in commit ee2d1ab . It was an issue with how I was calculating scale. I wasn't using complete formula. It's now synchronized. I did find another error. When butterfly mode is toggled scale bar text isn't updated. I'll make a commit for that |
Describe the problem
The added channel type scaling in #263 is half of the display channel type.
It would be nice to harmonize and choose which one to display.
@larsoner @nmarkowitz Any strong opinion here?
The text was updated successfully, but these errors were encountered: