Chris Thrasher

Results 68 issues of Chris Thrasher

In a number of recent issues we've made a point to update the Doxygen documentation to use backticks around things like `std::null opt` or references to other SFML APIs to...

feature
m:doc

With the recent merge of #2992 we have completed the `std::optional`-ification of SFML that we had planned since late 2023. A slew of other API breakages/changes/additions were planned for v3.0.0...

feature

## Description Inspired by #3062. If you construct a texture and a sprite then move the sprite, the sprite is left pointing at an address where there is no longer...

bug
m:sfml-graphics

## Description This document aims to outline everything an SFML 2 user needs to know when upgrading their project.

feature
m:doc

SFML 4 will require C++20 or newer. This issue catalogs places where SFML could benefit from utilizing C++20 features. Some of these changes imply breaking the API while others are...

feature

## Description This follows an existing precedent where any type that exclusively contains `public` functions and data is marked as a `struct`. At this point I think we've found all...

feature

## Description Follows the same pattern as https://github.com/SFML/SFML/pull/2540, https://github.com/SFML/SFML/pull/2759, https://github.com/SFML/SFML/pull/2801, and https://github.com/SFML/SFML/pull/3149. Core Foundation pointers are used in a slightly more complicated way than in the previously cited PRs. In...

bug
m:sfml-window
p:macos

## Description Closes #3157 The rationale in Vittorio's issue lays out the value case for this change so I won't repeat that. The one place this PR differs from Vittorio's...

feature

## Description Closes #3003 The thread safety itself is solved in a simple matter of locking a mutex each time the logging function is called. This ensures that logs are...

feature
m:sfml-system