I’m sorry, I see it now. There is definitely a bug here, probably with the figure definition. We’ll investigate and get back to you.
thank you very much
As a workaround for now, you can redefined the “Ring” figure with this code:
go.Shape.defineFigureGenerator("Ring", function(shape, w, h) {
var param1 = shape ? shape.parameter1 : NaN;
if (isNaN(param1) || param1 < 0) param1 = 8;
var rad = w / 2;
var geo = new go.Geometry();
var fig = new go.PathFigure(w, w / 2, true); // clockwise
geo.add(fig);
fig.add(new go.PathSegment(go.PathSegment.Arc, 0.1, 360, rad, rad, rad, rad).close());
var rad2 = Math.max(rad - param1, 0);
if (rad2 > 0) { // counter-clockwise
fig.add(new go.PathSegment(go.PathSegment.Move, w / 2 + rad2, w / 2))
fig.add(new go.PathSegment(go.PathSegment.Arc, 0, -360, rad, rad, rad2, rad2).close());
}
geo.spot1 = GeneratorEllipseSpot1;
geo.spot2 = GeneratorEllipseSpot2;
geo.defaultStretch = go.GraphObject.Uniform;
return geo;
});
And it should fix the problem.
thank you very much ( walter , simon ). the bug now is gone