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.

Sign up for GitHub

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

Jump to bottom

Move scalable resource header #453

Closed
baconpaul opened this issue Feb 2, 2019 · 0 comments
Closed

Move scalable resource header #453

baconpaul opened this issue Feb 2, 2019 · 0 comments

Comments

@baconpaul
Copy link
Collaborator

When @jsakkine did linux resource loader we realized I put scalaberesources.h in the wrong directory. It should be in src/windows. We should correct the script that makes it and move the file.
baconpaul added a commit to baconpaul/surge that referenced this issue Feb 2, 2019
@baconpaul
Move scalableresource.h
43265a9 
When @jsakkine was doing linux resources, he and I realized
that I had put this file in the wrong directory. It should be
in windows and conditionally included. Addresses issue surge-synthesizer#453
baconpaul added a commit to baconpaul/surge that referenced this issue Feb 2, 2019
@baconpaul
Move scalableresource.h
be507bc 
When @jsakkine was doing linux resources, he and I realized
that I had put this file in the wrong directory. It should be
in windows and conditionally included. Addresses issue surge-synthesizer#453
@baconpaul baconpaul mentioned this issue Feb 2, 2019
Merged
baconpaul added a commit to baconpaul/surge that referenced this issue Jul 10, 2019
@baconpaul
Move scalableresource.h
979f3ba 
When @jsakkine was doing linux resources, he and I realized
that I had put this file in the wrong directory. It should be
in windows and conditionally included. Addresses issue surge-synthesizer#453


Former-commit-id: 7eb4a31efd6308799729774ede412595ff6e485d [formerly be507bc]
Former-commit-id: cc90150f2e2d77aba0b1e1256969742150589919
Former-commit-id: 1cf76594e1ff9d363f205bfbac50ad370b27fe5c
@bobobo199733 bobobo199733 mentioned this issue Mar 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@baconpaul