feat: Better histogram control (plus pygfx histogram overhaul)

[gselzer]

This PR adds:

• A button to toggle the logarithmic base for the histogram. Originally, I was thinking that a slider would be nice (as I remembered @tlambert03 showing me some similar sort of functionality in Elements) but I couldn't get it to work nicely so for now the button will accomplish our goals.
• A button to reset the histogram view, because I got tired of losing it.
• A retained histogram frustum when setting the data. I find it frustrating when you pan/zoom to have a nice view of the data for that to be reset when you update the data.

To accomplish these features, some serious TLC was required to accomodate the new histogram features using pygfx. The way that we were calculating the margins was becoming increasingly complicated, so I developed a new strategy where the plot, x-axis, and y-axis are all rendered separately. This enables us to easily:

• Create one scene for canvas elements that should not move in response to user input, like the x-axis.
• Provide margins with far less computation.
  The downside here is more complication in the rendering pipeline, but I think it's better than it was.

Recording.2025-02-28.213811.mp4

These controls should be ready for opinions (cc @tlambert03, @fdrgsp), but also still need to:

• Resolve all FIXMEs
• Clean
• Test

[codecov]

Codecov Report

Attention: Patch coverage is 67.32955% with 115 lines in your changes missing coverage. Please review.

Project coverage is 79.73%. Comparing base (384e1d7) to head (28fb2a2).

Files with missing lines	Patch %	Lines
src/ndv/views/_pygfx/_histogram.py	53.75%	37 Missing ⚠️
src/ndv/views/_vispy/_histogram.py	41.86%	25 Missing ⚠️
src/ndv/views/_wx/_array_view.py	86.25%	11 Missing ⚠️
src/ndv/views/_jupyter/_app.py	0.00%	8 Missing ⚠️
src/ndv/views/_jupyter/_array_view.py	75.00%	8 Missing ⚠️
src/ndv/views/_vispy/_plot_widget.py	68.00%	8 Missing ⚠️
src/ndv/views/_qt/_array_view.py	89.28%	6 Missing ⚠️
src/ndv/views/_qt/_app.py	0.00%	5 Missing ⚠️
src/ndv/views/_wx/_app.py	44.44%	5 Missing ⚠️
src/ndv/views/bases/_graphics/_mouseable.py	66.66%	1 Missing ⚠️
... and 1 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
- Coverage   80.68%   79.73%   -0.95%     
==========================================
  Files          44       44              
  Lines        4209     4417     +208     
==========================================
+ Hits         3396     3522     +126     
- Misses        813      895      +82     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tlambert03]

also great stuff here. if implementing the slider was problematic, i'm fine with a button for now. I was recently playing with histograms as well, and trying to apply range limits (so that the thing doesn't scroll past, for example, 0-65,535). I think it's pretty straightforward using the 1DPanZoom camera, and updating the rect.setter so that you can never set the rect larger than the full range. (we should probably only do it for integer dtypes though)

I'll have a closer look at the changes required here soon. thanks!

[gselzer]

I was recently playing with histograms as well, and trying to apply range limits (so that the thing doesn't scroll past, for example, 0-65,535).

Let me know what you think of 5bf0f1e - could use a little polish but I think it works pretty well.

[gselzer]

Particular review going to acedb6e would be worthwhile, as it adds a new field clim_bounds to the LutModel. The problem I was trying to solve here is "how do we notify each LutView (specifically the clims sliders and the histograms) about the maximum allowed clim?", which is both needed to solve this:

I was recently playing with histograms as well, and trying to apply range limits (so that the thing doesn't scroll past, for example, 0-65,535)

as well as #152, which this PR would now close. However there may be a better place to store this state...