Peter Sobolewski

> That's a very interesting suggestion. I wished I had thought about that years ago in ImageJ. > I only thought of it because this is what napari-pyclesperanto-assistant does so...

So you want to estimate the extra points when (nr points) > (nr of pixels)? So essentially you want to upscale the data (pixels) to match the number of points...

Regarding your first question, you mean when our lovely Shape vector line overlaps multiple pixels because it's at an angle and doesn't obey the pixel grid? So this is indeed...

You're always thinking big! Yes, of course if your "channels" are physically the same but with different scales so different pixel sizes then you need could something about that too...

Not sure if it's the QTimer or what, but the live refresh seems quite slow on my end. The updating is slow and my line adjustment is laggy, like it...

I'm not sure how `def add_plane(self, *args, **kwargs) -> None:` should be properly annotated. My google-fu was weak? So I just added the `type: ignore`, advice welcome.

I think if I dropped the `->None:` then mypy would also skip it? So maybe that's better?

Boo, dropping the None didn't work: https://github.com/napari/napari/actions/runs/9165440649/job/25198887475?pr=6921#step:5:16

Thanks @Czaki ❤️

Yeah I can reproduce. Not sure what we changed napari side, will try to take a look!