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
I have been using the InkingManager and the LiveCanvas from the @microsoft/live-share-canvas during the hack project. The LiveCanvas is stored in the Fluid Relay in the initialObjects. One of the things I have noticed, when you start inking (in local debug) and close the debugger and do this debugging and stopping over and over the performance is getting worse. It looks like the Fluid remembers every Inking action and when you start a new debug session, it goes through all these actions and in the end you see your previous state of the canvas. When I perform a clean action on the InkingManager, before I close the debugging session, it looks like this is not the case anymore. Is it true that all inking actions are stored in the Fluid and starting the App is going through all these actions? I have had situations, the App became really slow to start and it took really long to show the latest canvas state.
In my opinion it would be good to only have the latest state of the Canvas stored. I doubt this is the case at the moment. Could someone give more insights on this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have been using the InkingManager and the LiveCanvas from the @microsoft/live-share-canvas during the hack project. The LiveCanvas is stored in the Fluid Relay in the initialObjects. One of the things I have noticed, when you start inking (in local debug) and close the debugger and do this debugging and stopping over and over the performance is getting worse. It looks like the Fluid remembers every Inking action and when you start a new debug session, it goes through all these actions and in the end you see your previous state of the canvas. When I perform a clean action on the InkingManager, before I close the debugging session, it looks like this is not the case anymore. Is it true that all inking actions are stored in the Fluid and starting the App is going through all these actions? I have had situations, the App became really slow to start and it took really long to show the latest canvas state.
In my opinion it would be good to only have the latest state of the Canvas stored. I doubt this is the case at the moment. Could someone give more insights on this?
Beta Was this translation helpful? Give feedback.
All reactions