Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2 "Beat+Bassline Editor" GUI bugs. #3584

Closed
husamalhomsi opened this issue May 28, 2017 · 8 comments · Fixed by #3589
Closed

2 "Beat+Bassline Editor" GUI bugs. #3584

husamalhomsi opened this issue May 28, 2017 · 8 comments · Fixed by #3589
Assignees

Comments

@husamalhomsi
Copy link
Member

husamalhomsi commented May 28, 2017

There are 2 bugs with the "Beat+Bassline Editor".

(1) The first bug: the right side of the "B+B E" near the last 2 steps of the fourth beat gets cropped when the "B+B E" opens.

An example:
Opening LMMS then opening the "B+B E":
beat bassline editor 1

(2) The second bug: when the "B+B E" is moved, the first bug disappears, but the "B+B E" takes a piece of the windows that is behind it and put it in its window near the last 2 steps of the fourth beat.

The first example:
Opening LMMS with the "Song-Editor" in view (this happens by default) then opening the "B+B E" then moving the "B+B E":
beat bassline editor 2

The second example:
Opening LMMS with the "Song-Editor" in view (this happens by default) then opening the "B+B E" then closing the "Song-Editor" (so the "B+B E" is over the "Automation Editor") then moving the "B+B E":
beat bassline editor 3

The third example:
Opening LMMS with the "Song-Editor" in view (this happens by default) then opening the "B+B E" then closing the "Song-Editor" then closing the "Automation editor" (so the "B+B E" is over the blank background) then moving the "B+B E":
beat bassline editor 4

  • The second bug happens with instrument plug-ins, too.
@husamalhomsi husamalhomsi changed the title "Beat+Bassline Editor" GUI bugs. 2 "Beat+Bassline Editor" GUI bugs. May 28, 2017
@BaraMGB
Copy link
Contributor

BaraMGB commented May 29, 2017

both bugs confirmed. They are related. I look into it.

@BaraMGB BaraMGB self-assigned this May 29, 2017
@BaraMGB
Copy link
Contributor

BaraMGB commented May 29, 2017

A quick workaround is to resize the bbEditor window.

The problem here is, the size of the window is saved with the project. But our new theme uses more space in width for the B+B editor. So the right side is cropped.

@husamalhomsi
Copy link
Member Author

husamalhomsi commented May 29, 2017

A quick workaround is to resize the bbEditor window.

I'm aware of that.

@BaraMGB
Copy link
Contributor

BaraMGB commented May 29, 2017

Okay, after a deeper dive into this problem I found it. If a project will be saved and a window is hidden a given size will be saved with the project. In case of the BB Editor this is 640 x 400 Pixel.

https://github.com/LMMS/lmms/blob/stable-1.2/src/gui/MainWindow.cpp#L760

@Wallacoloo Do you know why this is necessary? This leads to this bug.

@Wallacoloo
Copy link
Member

@BaraMGB I vaguely remember changing that code. IIRC: Previously, the behavior was that all open windows have their positions/sizes saved so that the workspace remains identical when the project is reopened. But oftentimes people arrange the windows specifically (e.g. mixer on right, B+BE on left) and minimize/hide them when not in use. When they save the project & these windows aren't visible, the position/size wasn't reported correctly, so their location wouldn't be preserved when opening the project again - I think they were saved with a size of (0, 0) and would be tiny when reopened.

The fix was to add that QSize sizeToStore = visible ? normalGeom.size() : sizeIfInvisible; line, to have some sane default (as opposed to a 0x0 window). I thought it had been implemented in a way where we would save the window's size prior to being minimized, but I guess not.

If it's introducing problems, it should be safe to modify so long as you test the behavior of loading a project with minimized windows afterward.

@Umcaruje
Copy link
Member

loading a project with minimized windows afterward.

We removed minimization of windows, they can only get closed now.

@Wallacoloo
Copy link
Member

Wallacoloo commented May 29, 2017 via email

@BaraMGB
Copy link
Contributor

BaraMGB commented May 29, 2017

If we'd fix that and save the actually size no matter the window is hidden or not the problem persist for older projects. It would be only fixed for projects which will be saved with this new program version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants