You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when MainLoop.start() is called, draw() is called to render the initial state before any updates occur. This behavior could lead to users writing buggy code based on the reasonable expectation that begin() and end() are called before and after draw(), respectively.
I think it would be fine to call begin() and end() before and after draw() when MainLoop.start() is called, but this might be considered a backwards-incompatible change. The alternative would be to document this behavior so that people know to manually call begin() and end() if needed.
The text was updated successfully, but these errors were encountered:
Currently, when
MainLoop.start()
is called,draw()
is called to render the initial state before any updates occur. This behavior could lead to users writing buggy code based on the reasonable expectation thatbegin()
andend()
are called before and afterdraw()
, respectively.I think it would be fine to call
begin()
andend()
before and afterdraw()
whenMainLoop.start()
is called, but this might be considered a backwards-incompatible change. The alternative would be to document this behavior so that people know to manually callbegin()
andend()
if needed.The text was updated successfully, but these errors were encountered: