07-20-2016, 08:44 PM
After finding many, many ways not to use iterators to step through ArtVectors (the kind returned by matchingArt, etc.), I'm really curious what the correct way is. Or any way that produces fewer than three build-stopping errors in one simple for statement (I'm not kidding). It's easy to get ArtVectors and even access the Art objects they reference by index number, but I can't for the life of me access the vectors as vectors rather than simple arrays. Several of my plugins will make extensive use of them, iterating though the objects to narrow down a search, for which I sure hope CORE's ArtVectors support the erase function. -- rj