Notes From Jam 2

[lavinrp]

• Look into state transition / action system for GB
  • Would be useful for cut scenes / Animation synchronization (what we wanted to do for RE)
• Look into making AnimatedSprite more ergonomic
  • Perhaps Builder pattern to make creating animation sets better
  • X, Y axis for uniform animation set caused some trouble
  • isAnimating is true even after ANIMATING_STOP
  • there is no way to query the animation type (ANIMATING_STOP vs other end types)
  • null pointer crash possible
    • something to do with improperly setup animation set.
    • getCurrentFrame without a current animation
  • allow chaining of addAnimation calls
    • may not be required if we use builder pattern
• Non shared_ptr GameRegion was actually really easy to use even though its unsafe
• switch to enum class over enum
• Strongly type update type
  • switch to std::chrono
• Animation demo things are shared_ptr when they dont need to be.
• Better docs
  • cmake settings grid in docs
  • put the docs in the headers
    • Mini demos
      • Are compiled
      • Extracted and put into sphinx

[lavinrp]

On SFML time vs std::chrono:

Windows:

• https://github.com/microsoft/STL/blob/3b0a1c9cfa607840519e49e8589815c25078c3df/stl/inc/chrono#L605
  • https://github.com/SFML/SFML/blob/master/src/SFML/System/Win32/ClockImpl.cpp#L74

Linux

• https://github.com/llvm-mirror/libcxx/blob/a0f5b3a6e323385fc29c8f6087f8b665fa6e7d4d/src/chrono.cpp#L158

• https://github.com/SFML/SFML/blob/master/src/SFML/System/Unix/ClockImpl.cpp#L49

sf::Clock and std::chrono have the same underlying system calls. The forum posts about sf::Clock having higher precision are just flat wrong