Draw Objects z-order not honored

[thepianok2FaHSK5xHXU]

Consider the following setups:

Setup 1:

1. At BarsInProgress = 0, CurrentBar = 179
   • DrawDot() is run first.
   • DrawDiamond() next.
2. Conclusion - Correct observation - Diamond overlays Dot (Figure 1)

Setup 2:

1. At BarsInProgress = 0, CurrentBar = 179
   • DrawDot() is run first.
   • DrawDiamond() next.
2. At BarsInProgress = 0, CurrentBar = 180
   • DrawDiamond() is run.
3. Conclusion - Correct observation - Diamond overlays Dot at Bar 179 still. (Figure 2)

Setup 3:

1. At BarsInProgress = 0, CurrentBar = 179
   • DrawDot() is run first.
   • DrawDiamond() next.
2. At BarsInProgress = 0, CurrentBar = 180
   • DrawDiamond() is run.
3. At BarsInProgress = 0, CurrentBar = 182
   • DrawDot() is run.
4. Conclusion - Incorrect observation - Dot overlays Diamond at Bar 179. (Figure 3)

To reproduce this observation:

1. Create a new Indicator
2. In OnBarUpdate(), write the necessary draw statements

I attached the CS file for reference. ADebug.cs

Can anyone explain why is this happening?
Thank you.

[NinjaTrader_Bertrand]

Welcome to the forums and thanks for the detailed report - this would be unfortunately expected since the drawn object types would share the same zorder level, so if you for example later draw another diamond that could change the previous zorder level of the diamonds. You can verify this on your setup be selecting a drawing object, holding Shift pressed and go through availabel zorder levels via your mousewheel. This is on developments list to review for our next major version update.