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

Mixer update #1828

Closed
wants to merge 9 commits into from
Closed

Mixer update #1828

wants to merge 9 commits into from

Conversation

M374LX
Copy link
Contributor

@M374LX M374LX commented Mar 6, 2015

Separate the metronome from the mixer
Make the mixer fully independent from the GUI
Clean up mixer's constructor

M374LX and others added 7 commits March 1, 2015 23:05
Update coding conventions, mainly spaces in parentheses. Also remove the unused variable Song::PlayPos::m_timeLineUpdate and the unnecessary declaration "friend class mainWindow;".
Update coding conventions, mainly spaces in parentheses. Also add more comments.
Make the mixer fully independent from the GUI
Clean up the mixer's contructor
@M374LX
Copy link
Contributor Author

M374LX commented Mar 6, 2015

Another possibility is to create a class for the metronome.

@diizy
Copy link
Contributor

diizy commented Mar 6, 2015

Why are you removing spaces from existing parentheses?

It was decided to drop the requirement for spaces, so you no longer have to add them if you don't want to in your own code, but that doesn't meant they need to be removed from existing code.

@M374LX
Copy link
Contributor Author

M374LX commented Mar 6, 2015

The spaces removal was actually because some topics in the coding conventions are not clear, as in issue #1826.

Do you prefer to undo the spaces removal?

@M374LX
Copy link
Contributor Author

M374LX commented Mar 16, 2015

An even better idea is to move the code deciding when to play a metronome sample to Song. Does anyone here disagree?

@tresf
Copy link
Member

tresf commented Apr 13, 2015

@M374LX the spaces in the parenthesis isn't a big deal here but it makes it harder to see the actual change. We'll need a rebase and some testing prior to merge. Could you simplify the PR a bit and squash the commits back into one? If it's easier, feel free to open a new PR. Thanks for the help on this. 👍

@M374LX
Copy link
Contributor Author

M374LX commented Apr 14, 2015

@tresf
After a better analysis, I found that better changes can be done. Perhaps the mixer samples can be handled by the Song class.

I have plans to check this when possible.

@tresf
Copy link
Member

tresf commented Apr 14, 2015

Thanks kindly for the quick response. I hope you don't mind I'll close this out until the new work is complete. Please open a new PR when you feel it is ready.

The coupling between core and UI bug is a good placeholder for now and since the conversation above is mostly in regards to coding conventions, we should be safe to start a new PR when its ready. :)

@tresf tresf closed this Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants