Graph::Anchor suggestion
#1
Apost 
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.
Reply
#2
Apost 
(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
Reply
#3
Apost 
(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?
Reply


Forum Jump:


Copyright © 2011-2017 Spraylight GmbH.