Closed hanslovsky closed 5 years ago
The fix makes sense to me -- can't come up with a case when committing these values would be needed
This breaks the BackgroundCanvasIterableTest
. Maybe #294 is not actually a bug. It depends on what "erase" means: Does it erase from the canvas or does it erase from the background?
On current master: erase from background
On this PR: erase from canvas
It may be useful to actually erase from background, e.g. when no valid foreground or background label is applicable. There are two ways forward here:
Currently I am in favor of (2) but I'll let this sit for a while.
For this discussion it would probably best to hear @wangyuhan01's opinion: When you erase,
Do you
Thanks so much @hanslovsky for looking into this issue. Option (1) will suffice, for us each voxel is either background or foreground with id.
I updated the test to not fail under the assumption that erasing means erasing from the canvas (option (1) above). If, in the future, it may become desirable to actually erase in the background, this should be revisited.
@wangyuhan01 Paintera 0.19.2 with this bug fix is now availble through conda and PyPI.
Fixes #294
We currently have special values
@axtimwalde @igorpisarev do you see any use case where we should actually paint a special value? In that case, this check would be to aggressive.