solved for the next version ... which is still in its testing phase. as long as you're using version 2.8.6, the problem is just a display bug. in 3.0 (maybe 2.9?) the display will be fixed also.