LFO speed-settings lost when a window-component is moved
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
OS : winXP sp3
LMMS: 1.1.90-g33d8v44 & LMMS 1.1.3 off. rel. on Windows 7 (Service Pack 1)
**Issue description:** In reference to this post: http://lmms.io/forum/viewtopic.php?f=7&t=6170 I found out that the behaviour was caused by the export-window itself, and not a export-fail.
**Example :** I managed to make a video of the fail: https://youtu.be/DELqt1p0eW8
**Recreate :** You need this file
[Unity Paradox - Breaking Point.zip](https://github.com/LMMS/lmms/files/671043/Unity.Paradox.-.Breaking.Point.zip)
witch is the oop orr project and then you need to move various windows around, like i do in the video. The fail does not occur in predictable fashion.
The question is : Can this be reproduced in current Master?
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 opening the attached Unity Paradox project in current Master on Windows and following the linked video while moving the export and other windows. Check whether LFO speed settings are lost and whether the behavior can be reproduced; done means confirming the current status with reproducible steps or establishing that it no longer occurs.
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