Talley Lambert

> If you drag the slider from 0 to 511 it does not draw all the slices from 0 to 511, that would be horrific. It will skip through drawing...


I'm not sure I agree here. It's an AttributeError to try to set an unsettable attribute with a regular layer too (`layer.ndim` is a [computed property](https://github.com/napari/napari/blob/7b6a9a5e75f9efcf947b88dd9a6fb066dd775636/napari/layers/base/base.py#L725-L728) without a setter), so...

oh right, I forgot that points takes an `ndim` parameter in the init. Honestly, I feel like that's the issue here. I would vote for using a different name in...

> But even if one renamed init_ndim would that fix the issue here? good point. no it wouldn't. I guess Points is just a little unique in that regard in...

thanks @penguinpee! i would be happy to include that change. @Czaki, what do you think?

It's true, the range slider (which comes from [superqt](https://pyapp-kit.github.io/superqt/widgets/qrangeslider/)) doesn't let the slider handles sit on top of each other. Your use case is a good/common one. I have a...

Definitely 👍 Rather than passing through all the methods though, maybe we follow the same thing that complex qt widgets do (like QComboBox.lineedit https://doc.qt.io/qt-6/qcombobox.html#lineEdit) and add a method that returns...

Ahh I see. Ok so the pass through would update all of them?

In any case, I’m supportive of the general goal of making that publicly accessible and open to whatever PR you come up with!