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

Implement remaining SFML 2.6.0 changes #187

Closed
ChrisThrasher opened this issue Jun 23, 2023 · 17 comments
Closed

Implement remaining SFML 2.6.0 changes #187

ChrisThrasher opened this issue Jun 23, 2023 · 17 comments
Labels

Comments

@ChrisThrasher
Copy link
Member

ChrisThrasher commented Jun 23, 2023

Credit to @dogunbound for this list from PR #186. I'm moving this list out to its own issue so we can track these changes while we incrementally merge PRs.


Basically, we need to slowly go through EVERY pull request and see if any change needs to be made and make those changes. If there aren't any changes needed for a specific pull request, mark it as complete.
todo list:

@ChrisThrasher
Copy link
Member Author

ChrisThrasher commented Jun 26, 2023

@eXpl0it3r eXpl0it3r pinned this issue Jun 26, 2023
@shane-tran-whitmire
Copy link

I would Highly recommend you put up a draft Pull request of the one you are working on, so others don't accidentally "take" yours.

@ChrisThrasher
Copy link
Member Author

ChrisThrasher commented Jul 3, 2023

Dibs on SFML/SFML#1047

See PR #190

@ChrisThrasher
Copy link
Member Author

See PR #191

@dogunbound
Copy link
Contributor

dogunbound commented Jul 4, 2023

Dibs on SFML/SFML#1746

I'll set up a PR later and update this comment with said PR number. I also just realized you can't really make a PR without a change, so calling dibs here first would be best.

#192

@ChrisThrasher
Copy link
Member Author

ChrisThrasher commented Jul 4, 2023

Dibs on SFML/SFML#1851

#193

@ChrisThrasher
Copy link
Member Author

Dibs on SFML/SFML#1688

#194

@ChrisThrasher
Copy link
Member Author

Dibs on SFML/SFML#1669

#195

@ChrisThrasher
Copy link
Member Author

Dibs on SFML/SFML#1757

#196

@ChrisThrasher
Copy link
Member Author

I'm marking SFML/SFML#1666 as complete since using sf::SoundStream::setProcessingInterval requires inheriting from sf::SoundStream and since that is not something we can express in the C interface, I'm not sure it makes sense to add that to CSFML. I suppose we could make a function called sfSoundStream_setProcessingInterval but then we're taking a protected function and basically making it public which doesn't seem quite right.

I also considered adding it to sfMusic but protected member functions can never be promoted to public member functions so this is not something we can call on an instance of sf::Music and thus compilation fails.

@ChrisThrasher
Copy link
Member Author

Dibs on SFML/SFML#1235

#197

@ChrisThrasher
Copy link
Member Author

Dibs on #SFML/SFML#1557

#198

@shane-tran-whitmire
Copy link

I think it's ok to make protected member variables public in this case. We need to look for another instance of this to really know what we should do though.

@dogunbound
Copy link
Contributor

dogunbound commented Jul 6, 2023

I think I missed taking SFML/SFML#1788 off the needed changes list. @ChrisThrasher could you update that list and check this one off?

Edit: Oh i see the mini list you created.

@ChrisThrasher
Copy link
Member Author

ChrisThrasher commented Nov 2, 2023

See #207 for an implementation of SFML/SFML#1484

Last 2.6.0 feature! 🥳

@ChrisThrasher
Copy link
Member Author

All done!!

@eXpl0it3r eXpl0it3r unpinned this issue Dec 19, 2023
@svenstaro
Copy link

How about a new CSFML release with these changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants