-
Notifications
You must be signed in to change notification settings - Fork 41
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
Renamed GOPanelView to GOGUIPanelView and moved to the gui directory #1636
Conversation
When testing this PR I've noticed a few crashes when closing GO, however it doesn't seem to be related to this PR at all (and I can make it happen with a current build too), but it's likely worth examining more closely. |
It looks like some GUI element of the main toolbar is deleted twice: one times explicitly and one times as part as a child of the toolbar window. Could you give me reproducing steps? |
Sure, it seems to happen every time both with a debug build and a release build on (Ubuntu 20.04) Linux.
or
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As the crash I mentioned earlier isn't related to this PR, I approve.
I couldn't reproduce the crash: GO closes correctly. Could you post the screenshot of File->Settings->Audio before the crash? |
@oleg68 This is using a standard Ubuntu 20.04 and a local build. I've re-built both the release and debug version of GO from latest official source and it crashes at closing GO even without having done anything at all after startup, it really doesn't matter if I use PortAudio or RtAudio. It just crashes at closing. I also managed to get a crash while changing from PortAudio to RtAudio in the Settings dialog, but that's another thing, I guess. Screenshots and crash reports from gdb: |
Working with #1035 I noticed that the
GOPanelView
class is close to other GUI classes.So this PR renames
GOPanelView
toGOGUIPanelView
and moved to thegui
directory.It is just refactoring. No GO behavior should be changed.