|
From: James W. <ja...@fr...> - 2007-02-13 23:49:20
|
In the renderers, I'm using a custom element to cache an optimized version of a TriMesh. The element contains an edit index along with the TriMesh reference, so that a stale cache can be detected. That works fine in principle, though there's a bug at the moment. But now suppose I have another similar custom element, say to cache a triangle strip. When I update the triangle strip, it bumps the edit index, so the other cache becomes stale. Which causes the other cache to get updated, bumping the edit index, which makes the triangle cache stale... How can I get out of this infinite loop? The simplest way, I suppose, would be to add a Q3Shared_SetEditIndex function, and use it when setting these cache elements. Is there a more elegant way I haven't thought of? -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |