Quote from: Crimson Wizard on Fri 06/01/2023 10:08:59But warnings regarding missing sprites should be added of course, imo that's an oversight that there was none at least printed to warnings log.
I'm not convinced. Consider something like:
In other words, a button displays a dynamic sprite, and this sprite is updated to do some animation (by switching the pointer to a new dynamic sprite rather than by redrawing onto its drawing surface). In this case, the old dynamic sprite no longer "exists" (refcount==0) as soon as dsFluid is reassigned, and so btnDisplay.NormalGraphic is invalid at that point. Of course, we're just about to update it in the next line.
Should AGS throw a warning (or actually, simulationSteps warnings) about that? Seems like it would clutter up the logs.