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.
Currently the block to scroll an image with negative parameter does not work in the board, but works on make code simulator.
Seems the underlying source code has a fourth parameter that needs to be used to specify the starting position when the scrolling is negative, as mentioned here: lancaster-university/microbit-dal#351
Would be nice to get those folks to wake up a review a couple of PRs dangling there.
Describe the solution you'd like
I would like the scrolling image block to either support the negative scrolling automatically or allow providing the starting position.
Describe alternatives you've considered
The alternatives are to use custom functions and implement loops to do the same
Additional context
None, rather than the fact the simulator works perfectly but in the physical board it doesn't
This was already reported here: #3485
The text was updated successfully, but these errors were encountered:
Feature request template
Is your feature request related to a problem? Please describe.
Currently the block to scroll an image with negative parameter does not work in the board, but works on make code simulator.
Seems the underlying source code has a fourth parameter that needs to be used to specify the starting position when the scrolling is negative, as mentioned here: lancaster-university/microbit-dal#351
Better support is currently pending on microbit-dal PR opened here since 2022:
lancaster-university/microbit-dal#485
Would be nice to get those folks to wake up a review a couple of PRs dangling there.
Describe the solution you'd like
I would like the scrolling image block to either support the negative scrolling automatically or allow providing the starting position.
Describe alternatives you've considered
The alternatives are to use custom functions and implement loops to do the same
Additional context
None, rather than the fact the simulator works perfectly but in the physical board it doesn't
This was already reported here:
#3485
The text was updated successfully, but these errors were encountered: