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
Is your feature request related to a problem? Please describe.
Given a Domain Story that is larger than the screen. When I use the replay mode and the next sentence is off-screen, I have to scroll the canvas manually so that the sentence becomes visisble. Often it is not obvious where to scroll, so I have to zoom out, find the new sentence, scroll there and zoom in again. This is tedious.
Describe the solution you'd like
When I click the "next" button in replay mode, and the sentence goes off-screen, the canvas should be scrolled automatically so that the sentence is visible. The solution should take into account that unnecessary scrolling might lead to disturbing user experience. The canvas should not just "jump around" every time I click the "next" button.
The text was updated successfully, but these errors were encountered:
If the Step extends downwards or to the left and the whole story upto this point is higher / wider than the canvas, the ocus is not yet working as intended -> See TODOs
Is your feature request related to a problem? Please describe.
Given a Domain Story that is larger than the screen. When I use the replay mode and the next sentence is off-screen, I have to scroll the canvas manually so that the sentence becomes visisble. Often it is not obvious where to scroll, so I have to zoom out, find the new sentence, scroll there and zoom in again. This is tedious.
Describe the solution you'd like
When I click the "next" button in replay mode, and the sentence goes off-screen, the canvas should be scrolled automatically so that the sentence is visible. The solution should take into account that unnecessary scrolling might lead to disturbing user experience. The canvas should not just "jump around" every time I click the "next" button.
The text was updated successfully, but these errors were encountered: