mirror of
https://github.com/SFML/SFML.git
synced 2024-11-24 20:31:05 +08:00
65fef85b30
CMake doesn't require absolute paths so we can safely remove SRCROOT and let implicit relative pathing achieve the same result with less work on our part. |
||
|---|---|---|
| .. | ||
| resources | ||
| CMakeLists.txt | ||
| CocoaAppDelegate.h | ||
| CocoaAppDelegate.mm | ||
| main.m | ||
| MainMenu.xib | ||
| NSString+stdstring.h | ||
| NSString+stdstring.mm | ||
| readme.txt | ||
SFML IN COCOA APPLICATION ========================= This is a small example of the integration of SFML in a Cocoa application. Features -------- * This example shows how basic UI elements can interact with SFML render areas such as sf::RenderWindow (you can use sf::Window and OpenGL code too, of course). * It also provides tools for converting NSString to and from std::[w]string in an Objective-C Category of NSString. * Moreover, it shows how you can prevent annoying the system alerts produced when the SFML view has focus and the user press a key (see SilentWindow interface in CocoaAppDelegate.[h|mm]). Special Considerations ---------------------- While mixing SFML into a Cocoa application you have to deal with mixing C++ and Objective-C. In order to proceed you should use .mm extension for Objective-C++ files. Be aware of the limitations of Objective-C++. Please refer to the official documentation provided by Apple for more information. You can also work around these limitations by using CSFML.