orenshatz

This explanation only accounts for a single voxel gap in a fixed 128-wide grid. Take a look at the image, the gap is more than a single voxel, and is...

Okay I see what happens here. The gaps indeed _begin_ at cube borders, but for some reason the border does not resume immediately after them. That's to say, one actually...

 Okay, the reason for the straight one is that the cell continues outside the movement area but only in that position. Looks a bit strange, but it's your decision...

I can do such plugin easily. But there is a general concern, namely we currently don't have a mechanism of notifying python code on events in knossos, I have to...

I didn't check at the time, so I can only check next time it happens. Shouldn't reload, experiment name is the same throughout my usage.

Maybe we should also have an node-independent arbitrary two-point/cumulative distance measurement. It can easily be implemented with a plugin.

Regardlessly - I wonder about diagonal (arbitrary angle) scale bar. In principle this would be ideal for dynamic-bar measurements, but in the Z viewports the anisotropy is a problem. What...

It depends on how many users we have complaining about crashes. I predict this number to be much bigger as knossos features are used, compared with the conservative node-placing standard...

Do we want this to be true by default, but stored to the NML when negative?

Maybe we should also optionally store it where positive to allow explicit override of visibility when merging from an NML? In short, please define this feature more explicitly.