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

windows/sound.cpp: Rename CheckDeviceCapabilities() #1409

Open
hoffie opened this issue Mar 31, 2021 · 9 comments
Open

windows/sound.cpp: Rename CheckDeviceCapabilities() #1409

hoffie opened this issue Mar 31, 2021 · 9 comments
Labels
good first issue Things which should be doable without lots of context refactoring Non-behavioural changes, Code cleanup

Comments

@hoffie
Copy link
Member

hoffie commented Mar 31, 2021

Describe the bug
CheckDeviceCapabilities() in windows/sound.cpp does more than what the name suggests: It has side effects such as updating instance variables such as lNumInChan.

Expected behavior

Have a name which makes it clear that updates happen.

Version of Jamulus
d5d4691

cc @ann0see @pljones

@hoffie hoffie added refactoring Non-behavioural changes, Code cleanup good first issue Things which should be doable without lots of context labels Mar 31, 2021
@DominikSchaller
Copy link

Maybe a stupid question, but what does "good first issue" mean? Does it mean, it's a good issue for a new developer?

@hoffie
Copy link
Member Author

hoffie commented Mar 31, 2021

what does "good first issue" mean? Does it mean, it's a good issue for a new developer?

Yes, this was the intention. I think this issue requires little Jamulus-specific context but could be worked on by some developer who is new to the project.

@ann0see
Copy link
Member

ann0see commented Apr 22, 2022

Any news here? @DominikSchaller @henkdegroot or @pgScorpio (sorry for the pings...) do you want to rename the function?

@pgScorpio
Copy link
Contributor

@ann0see

Any news here? @DominikSchaller @henkdegroot or @pgScorpio (sorry for the pings...) do you want to rename the function?

No, just wait for the sound redesign.... It's already changed there.

@ann0see ann0see added this to Tracking Jul 1, 2023
@github-project-automation github-project-automation bot moved this to Triage in Tracking Jul 1, 2023
@pljones pljones added Windows Windows runtime issue and removed Windows Windows runtime issue labels Jul 21, 2024
@T-Roel
Copy link

T-Roel commented Dec 8, 2024

@hoffie and @pgScorpio is this issue still necessary? I'd like to start to contribute in the project and this is the only good first issue available.

@ann0see
Copy link
Member

ann0see commented Dec 8, 2024

Thanks!

I believe it's still relevant.
Feel free to raise a PR - but be aware that the review process might take some time.

Concerning contributing: make sure to read the CONTRIBUTING.md file.

@softins
Copy link
Member

softins commented Dec 8, 2024

Hi @T-Roel, neither @hoffie nor @pgScorpio are currently active on the Jamulus project.

I see this issue is a very old one. I've taken a quick look at it, and I don't think it is an important issue. And versions of the function are used in both Windows and Mac. I would be inclined to just close this issue as "Won't fix".

But we're always glad to welcome new contributors. Are you currently a user of Jamulus? And do you use Discord? We have a few Jamulus channels on there where developers chat.

@T-Roel
Copy link

T-Roel commented Dec 8, 2024

@ann0see and @softins thank you very much for your feedback! Since it doesn't seem necessary to do this issue, could you recommend another good first one?

@softins I'm starting using Jamulus in order to investigate some cognitive aspects in networked music performance as part of my PhD. I don't use Discord, but I intend to create a profile to chat with the community :)

@softins
Copy link
Member

softins commented Dec 8, 2024

@T-Roel cool! I've been told the Discord is currently only open to established team members - my bad! But I've just found you on Facebook, and I will make contact with you on Messenger to chat a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Things which should be doable without lots of context refactoring Non-behavioural changes, Code cleanup
Projects
Status: Triage
Development

No branches or pull requests

7 participants