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

"Refresh browser" option at the bottom of LMB/RMB patch menus #1197

Closed
mkruselj opened this issue Sep 21, 2019 · 2 comments · Fixed by #1569
Closed

"Refresh browser" option at the bottom of LMB/RMB patch menus #1197

mkruselj opened this issue Sep 21, 2019 · 2 comments · Fixed by #1569
Labels
UI Issues related to UI look&feel
Milestone

Comments

@mkruselj
Copy link
Collaborator

Makes sense, no? :)

@baconpaul baconpaul modified the milestones: 1.6.2.1, 1.6.3 Sep 21, 2019
@baconpaul baconpaul modified the milestones: 1.6.3, Currently Unscheduled Oct 9, 2019
@baconpaul
Copy link
Collaborator

I'm gonna move this out of 1.6.3. It is too irritating a refernence to thread through and I'd rather spend time on S++. Will keep it open so we can fix it later.

@baconpaul baconpaul modified the milestones: Currently Unscheduled, 1.6.6 Feb 1, 2020
@mkruselj mkruselj added the UI Issues related to UI look&feel label Feb 5, 2020
baconpaul added a commit to baconpaul/surge that referenced this issue Feb 12, 2020
As well as having refresh all data in the user/data menu
add refresh patch and refresh wave lists to the places where
you open waves and patches.

Closes surge-synthesizer#1197
@baconpaul
Copy link
Collaborator

I have no idea what I was thinking when I wrote that comment in October. This was super easy.

baconpaul added a commit that referenced this issue Feb 12, 2020
As well as having refresh all data in the user/data menu
add refresh patch and refresh wave lists to the places where
you open waves and patches.

Closes #1197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UI Issues related to UI look&feel
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants