Closed mself closed 4 years ago
Could you rebase on master to make Github realise there are no conflicts ? When I do it manually and close the pull request they look like if they were rejected with a red icon instead of purple merged one. I think this is because all your PRs are chained. I guess it will not occur if PR start from master
Done. I'm still not sure the best way to make the PRs. If they all start from master, then I can't build on previous work. But if they are chained it seems like they have to be rebased one at a time when you merge the previous PRs. Open to suggestions...
Done. I'm still not sure the best way to make the PRs. If they all start from master, then I can't build on previous work. But if they are chained it seems like they have to be rebased one at a time when you merge the previous PRs. Open to suggestions...
I think start from master is was it the most evident for Github integration so they are all independant from each other
I previously removed these files, thinking they were obsolete. But they are useful templates for creating new widgets.
widgets/base/base*
fileswidgets/vibrato/vibratoview.cpp
that was left over from copying this files from thewidgets/base/baseview.cpp
templateBaseView
andBaseWidget
toSampleView
andSampleWidget