BROWSER - When Previewing Samples In Browser Accidental Sending Of Samples To B+B Editor
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Hello Everyone,
If no one else experiences this I apologize, but I was wondering if anyone does.
I find rather often when previewing audio samples in the BROWSER, especially when trying to listen to a sample more than once by clicking on it again, because the some samples are a little longer and haven't finished decaying, when you click again LMMS takes this as a double click sending the sample over to the B+B Editor. Don't get me wrong it is kind of nice to be able to double click on samples to achieve this but it seems to cause some minor issues for me anyways.
It might be just me being a little spazzy with it but it kind of prevents you from being able to quickly listen to samples more than once without then having to go into the B+B Editor and remove them.
Sort of relating to this topic of the BROWSER, there are some great ideas found in this discussion here, where members speak of also being able to use the arrow keys as well as being able to stop samples that are long, if anyone is interested.
https://github.com/LMMS/lmms/issues/871
Again most of the things I bring up aren't huge deals, just possible things to be added in the future to refine minor things a little bit if desired.
If anyone experiences this often and has any ideas or if anyone has any opinions please share.
Thank You
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing repeated sample clicks in the BROWSER and observe when a sample is sent to the B+B Editor. Review related issue #871 for browser behavior context. The issue needs an agreed expected interaction before completion can be verified: repeated previewing should not accidentally open or add the sample to the editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100