You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is most likely a few bugs in PlanarImg accessors.
For example: PlanarCursor has a protected int index field that is used and modified in jumpFwd() and fwd() among others. PlanarCursor2D extends PlanarCursor and overrides fwd() such that it does not touch index. So, in subsequent jumpFwd() it would be out-of-sync with the Type's index.
There is a few other instances of similar problems in the net.imglib2.img.planar. I didn't thoroughly investigate, write tests, etc. But something is clearly wrong.
The text was updated successfully, but these errors were encountered:
There is most likely a few bugs in PlanarImg accessors.
For example:
PlanarCursor
has aprotected int index
field that is used and modified injumpFwd()
andfwd()
among others.PlanarCursor2D
extendsPlanarCursor
and overridesfwd()
such that it does not touchindex
. So, in subsequentjumpFwd()
it would be out-of-sync with the Type's index.There is a few other instances of similar problems in the
net.imglib2.img.planar
. I didn't thoroughly investigate, write tests, etc. But something is clearly wrong.The text was updated successfully, but these errors were encountered: