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
This is happening because rotoscope tries to keep information from the stack based by pushing a frame to this stack on call events and popping a stack from on a return event.
except that it doesn't keep track of calls to blocks.
Unlike that issue, this one is easier to fix with the current approach by also tracing block calls and returns so they can be included in the rotoscope stack.
The text was updated successfully, but these errors were encountered:
This is happening for a similar reason as #57
except that it doesn't keep track of calls to blocks.
Unlike that issue, this one is easier to fix with the current approach by also tracing block calls and returns so they can be included in the rotoscope stack.
The text was updated successfully, but these errors were encountered: