LMMS / LMMS/lmms

'override' auto-scrolling

Open
#2,236 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug gui
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

sure most has done this:
A track is playing
you want to inspect something in the track, perhaps it was just something you heard, or diddent :p
You mouse-grab the slider, and drag it, but to no avail
Auto-scroll forces the focus to be at play-head.
What i thought was that is would be reasonable that any manual drag of the slider, would indicate that user want to 'over-ride' the current view-position, and let the view change even if auto-scroll was on.

> When user then release the slider, the view would jump to auto-scroll pos. again.

NO i have done re-thinking on this. The reason the user want to move the view, is that he actually like to focus a _different_, than part, where the playhead is at _that_ moment. This fact makes this feature very simple to implement. The correct behavior is to simply **stop** playback, and then the user can freely scroll the view to any position of his choice. So the only thing that is needed is that user-scrolling of the view, should stop playback! Its as easy as that.

This feature should be for all editor-windows (curent lmms only have play-head-controlled scroll in P-R and S-E, but Automation-editor should hopefully soon(ish) be scrolling too)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the play-head-controlled scrolling in the P-R and S-E editor windows, then check how the Automation-editor is expected to behave as scrolling is added there. Confirm the existing playback and view-scrolling interaction before defining the change; done means user-scrolling stops playback consistently in all editor windows that support this behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.