Page 1 of 1
Timeline Scrolling
Posted:
Tue Aug 22, 2017 12:40 am
by Jim Simon
I notice a new issue has cropped up with 14.0.0B.061 on Windows 10. If the timeline scroll bar is at Home position, the mouse wheel will not scroll the timeline. Once the scroll bar is moved away from the left most position, timeline scrolling works normally.
Re: Timeline Scrolling
Posted:
Mon Sep 04, 2017 10:02 pm
by Jim Simon
I just want to report that this bug is still present in version 17.0.0B.072. If the timeline scroll bar is at Home position, mouse wheel scrolling is disabled. Once the scroll bar is moved from the far left, mouse wheel scrolling works normally.
Love to get this corrected in the next beta. I scroll the timeline a LOT, and being stuck at Home is...frustrating.
Re: Timeline Scrolling
Posted:
Tue Sep 05, 2017 11:20 am
by Danilo Coelho
I noticed this on this last version too.
Re: Timeline Scrolling
Posted:
Wed Sep 06, 2017 10:06 am
by Peter Chamberlain
We haven't been able to repo this. Can u post a phone video of normal scroll and the issue?
Re: Timeline Scrolling
Posted:
Wed Sep 06, 2017 12:13 pm
by John Paines
Peter, I see it as well. Once the bottom scroll bar is at its leftmost position -- aligned with the start of the timeline -- mouse scrolling (the wheel) won't work. It won't matter where the playhead is.
Re: Timeline Scrolling
Posted:
Mon Sep 11, 2017 4:46 pm
by Jim Simon
Glad it's not just me. Here's more detail:
viewtopic.php?f=21&t=64200
Re: Timeline Scrolling
Posted:
Mon Sep 11, 2017 5:03 pm
by Jean Claude
On my PC:
EDIT tab: whether the playhead is at the beginning or somewhere else:
- ALT + mouse wheel scrool => zoom horizontally
FAIRLIGHT tab: whether the playhead is at the beginning or somewhere else:
- ALT + mouse wheel scrool => zoom horizontally
- SHIFT + mouse wheel scrool => vertically
Try?
Re: Timeline Scrolling
Posted:
Mon Oct 16, 2017 12:58 pm
by KevKlopper
definitely an issue, scrolling (NOT zooming) doesnt work when in the bar indicator is in home position, please fix
Re: Timeline Scrolling
Posted:
Mon Oct 16, 2017 7:10 pm
by Jim Simon
The issue does seem to be resolved (pun intended) in version 14.0.1.