Makes sense. Good catch! Andrew Wetmore Assistant VP, Marketing and Publicity, The ASF <https://apache.org> Editor-Writer, Infra team, The ASF
Editor, moosehousepress.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sun, Feb 15, 2026 at 9:12 AM Harbs <[email protected]> wrote: > I checked all classes. All classes which support MXML have the > initialization check with the exception of these three: > > UIItemRendererBase > StyledUIItemRendererBase > GraphicsItemRenderer > > I changed UIItemRendererBase already. Unless someone had an objection, > I’ll do the other two as well. > > My assumption is that UIItemRendererBase was an oversight and the other > two were copied from that. > > Harbs > > > On Feb 15, 2026, at 2:38 PM, Harbs <[email protected]> wrote: > > > > I was just tearing my hair out trying to figure out why I was getting > double elements when moving the position of an item renderer. > > > > It seem like UIItemRendererBase is missing an “_initialized” check. > > > > I’m assuming that was an oversight. If there’s a reason that it should > be initialized more than once, please correct me… > > > > Harbs > >
