Official Murl Engine Forum
Graph::Anchor suggestion - Printable Version

+- Official Murl Engine Forum (https://murlengine.com/forum)
+-- Forum: Murl Engine (https://murlengine.com/forum/forumdisplay.php?fid=5)
+--- Forum: General (https://murlengine.com/forum/forumdisplay.php?fid=8)
+--- Thread: Graph::Anchor suggestion (/showthread.php?tid=223)



Graph::Anchor suggestion - Stefan - 04 Feb 2015

Hi again,

I wonder if it would be safer to initialize the variables mRecentLogicTickNumber and mRecentFrameNumber in the implementation of Graph::Anchor with Math::Limits<UInt32>::Max() instead of zero. With zero, the update will always be skipped during the first traversal (0) because of the WasTraversed... query.


RE: Graph::Anchor suggestion - dizzy - 23 Feb 2015

(04 Feb 2015, 11:39)Stefan Wrote: Hi again,

I wonder if it would be safer to initialize the variables mRecentLogicTickNumber and mRecentFrameNumber in the implementation of Graph::Anchor with Math::Limits<UInt32>::Max() instead of zero. With zero, the update will always be skipped during the first traversal (0) because of the WasTraversed... query.

Will be fixed in the next update!

Best regards,

dizzy


RE: Graph::Anchor suggestion - Barkley - 22 Jul 2017

(23 Feb 2015, 15:37)dizzy Wrote:
(04 Feb 2015, 11:39)Stefan Wrote: Hi again,

I wonder if it would be safer to initialize the variables mRecentLogicTickNumber and mRecentFrameNumber in the implementation of Graph::Anchor with Math::Limits<UInt32>::Max() instead of zero. With zero, the update will always be skipped during the first traversal (0) because of the WasTraversed... query.

Will be fixed in the next update!

Best regards,

dizzy

Was this fixed?