Navy.gif/glfw
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
6f8ec4075b
glfw/README.md

401 lines
22 KiB
Markdown
Raw Normal View History

Removed version noise.
2013-06-13 15:07:28 +02:00
# GLFW
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Migrate from Travis CI to GitHub Actions The old Travis CI .org service has been throttled for a while now and is said to be shutting down completely next week. This migrates the Travis CI build jobs to GitHub Actions, with minor changes. - The trailing whitespace detection has been removed for now. - The libegl1-mesa-dev dependency for Wayland has been removed as it appears to no longer be necessary for building.
2021-06-07 22:21:23 +02:00
[![Build status](https://github.com/glfw/glfw/actions/workflows/build.yml/badge.svg)](https://github.com/glfw/glfw/actions)
CI file fixes
2016-02-04 14:58:44 +01:00
[![Build status](https://ci.appveyor.com/api/projects/status/0kf0ct9831i5l6sp/branch/master?svg=true)](https://ci.appveyor.com/project/elmindreda/glfw)
Add Coverity badge, I guess
2016-06-23 16:09:55 +02:00
[![Coverity Scan](https://scan.coverity.com/projects/4884/badge.svg)](https://scan.coverity.com/projects/glfw-glfw)
Add initial Travis CI file
2015-04-14 23:47:17 +02:00
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
## Introduction
Documentation work
2016-08-09 01:34:56 +02:00
GLFW is an Open Source, multi-platform library for OpenGL, OpenGL ES and Vulkan
application development. It provides a simple, platform-independent API for
creating windows, contexts and surfaces, reading input, handling events, etc.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Documentation work
2019-04-16 01:36:49 +02:00
GLFW natively supports Windows, macOS and Linux and other Unix-like systems. On
Fix typo Fixes #1601.
2019-08-28 21:28:23 +02:00
Linux both X11 and Wayland are supported.
Documentation work
2017-01-29 20:10:53 +01:00
Documentation work
2016-08-17 16:48:22 +02:00
GLFW is licensed under the [zlib/libpng
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
license](https://www.glfw.org/license.html).
Start 3.2.1
2016-06-05 19:35:39 +02:00
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
You can [download](https://www.glfw.org/download.html) the latest stable release
Documentation work
2019-04-16 01:36:49 +02:00
as source or Windows binaries, or fetch the `latest` branch from GitHub. Each
release starting with 3.0 also has a corresponding [annotated
Documentation work
2016-08-17 16:48:22 +02:00
tag](https://github.com/glfw/glfw/releases) with source and binary archives.
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
The [documentation](https://www.glfw.org/docs/latest/) is available online and is
Documentation work
2019-04-16 01:36:49 +02:00
included in all source and binary archives. See the [release
notes](https://www.glfw.org/docs/latest/news.html) for new features, caveats and
deprecations in the latest release. For more details see the [version
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
history](https://www.glfw.org/changelog.html).
Documentation work
2017-01-29 20:10:53 +01:00
The `master` branch is the stable integration branch and _should_ always compile
and run on all supported platforms, although details of newly added features may
change until they have been included in a release. New features and many bug
fixes live in [other branches](https://github.com/glfw/glfw/branches/all) until
they are stable enough to merge.
Start 3.3
2016-08-18 23:42:15 +02:00
Updated readme links to guides.
2013-04-07 13:26:06 +02:00
If you are new to GLFW, you may find the
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
[tutorial](https://www.glfw.org/docs/latest/quick.html) for GLFW 3 useful. If
Documentation work
2017-07-12 00:21:17 +02:00
you have used GLFW 2 in the past, there is a [transition
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
guide](https://www.glfw.org/docs/latest/moving.html) for moving to the GLFW
Documentation work
2017-07-12 00:21:17 +02:00
3 API.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Move list of contributors to separate file Fixes #1839
2021-07-19 18:25:50 +02:00
GLFW exists because of the contributions of [many people](CONTRIBUTORS.md)
around the world, whether by reporting bugs, providing community support, adding
features, reviewing or testing code, debugging, proofreading docs, suggesting
features or fixing bugs.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Moved GLFW compilation guide to docs.
2013-10-27 12:50:33 +01:00
## Compiling GLFW
Cross-linked build guides.
2013-10-21 22:23:15 +02:00
Documentation work
2019-04-16 01:36:49 +02:00
GLFW itself requires only the headers and libraries for your OS and window
system. It does not need the headers for any context creation API (WGL, GLX,
EGL, NSGL, OSMesa) or rendering API (OpenGL, OpenGL ES, Vulkan) to enable
support for them.
Documentation work [ci skip]
2016-07-14 18:32:30 +02:00
Documentation work [ci skip]
2016-07-14 18:29:39 +02:00
GLFW supports compilation on Windows with Visual C++ 2010 and later, MinGW and
Update default name from OS X to macOS Note that earlier releases are still referred to by their proper names; OS X <version> or Mac OS X <version>.
2016-10-20 00:50:54 +02:00
MinGW-w64, on macOS with Clang and on Linux and other Unix-like systems with GCC
Documentation work [ci skip]
2016-07-14 18:29:39 +02:00
and Clang. It will likely compile in other environments as well, but this is
not regularly tested.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
There are [pre-compiled Windows binaries](https://www.glfw.org/download.html)
Documentation work
2017-07-12 00:21:17 +02:00
available for all supported compilers.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
See the [compilation guide](https://www.glfw.org/docs/latest/compile.html) for
Documentation work
2017-07-12 00:21:17 +02:00
more information about how to compile GLFW yourself.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Documentation work
2016-07-14 18:02:44 +02:00
Documentation work [ci skip]
2016-07-14 18:11:17 +02:00
## Using GLFW
Documentation work
2016-07-14 18:02:44 +02:00
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
See the [documentation](https://www.glfw.org/docs/latest/) for tutorials, guides
Documentation work
2017-01-29 20:10:53 +01:00
and the API reference.
## Contributing to GLFW
See the [contribution
Move contribution guide to visible directory
2017-11-20 18:55:43 +01:00
guide](https://github.com/glfw/glfw/blob/master/docs/CONTRIBUTING.md) for
Documentation work
2017-01-29 20:10:53 +01:00
more information.
Documentation work
2016-07-14 18:02:44 +02:00
Documentation work [ci skip]
2016-07-14 18:11:17 +02:00
## System requirements
Documentation work
2016-07-14 18:02:44 +02:00
Cocoa: Move slightly towards modern Objective-C
2019-01-03 19:32:45 +01:00
GLFW supports Windows XP and later and macOS 10.8 and later. Linux and other
Documentation work
2017-01-29 20:10:53 +01:00
Unix-like systems running the X Window System are supported even without
a desktop environment or modern extensions, although some features require
a running window or clipboard manager. The OSMesa backend requires Mesa 6.3.
Documentation work
2016-07-14 18:02:44 +02:00
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
See the [compatibility guide](https://www.glfw.org/docs/latest/compat.html)
Documentation work [ci skip]
2016-07-14 18:19:46 +02:00
in the documentation for more information.
Documentation work
2016-07-14 18:02:44 +02:00
Added dependency section to readme.
2014-01-12 05:40:36 +01:00
## Dependencies
Update minimum required CMake version to 3.1
2019-11-26 18:09:22 +01:00
GLFW itself needs only CMake 3.1 or later and the headers and libraries for your
OS and window system.
Documentation work
2016-08-09 01:34:56 +02:00
Documentation work [ci skip]
2016-02-08 16:23:44 +01:00
The examples and test programs depend on a number of tiny libraries. These are
located in the `deps/` directory.
Added dependency section to readme.
2014-01-12 05:40:36 +01:00
Clarified dependency list.
2014-06-18 16:13:49 +02:00
- [getopt\_port](https://github.com/kimgr/getopt_port/) for examples
with command-line options
Updated TinyCThread URL.
2014-10-15 03:55:25 +02:00
- [TinyCThread](https://github.com/tinycthread/tinycthread) for threaded
Clarified dependency list.
2014-06-18 16:13:49 +02:00
examples
Replace glad and the Vulkan SDK with glad2 This removes all dependencies from the GLFW test programs on the Vulkan SDK. It also removes support for linking the GLFW shared library (dynamic library, DLL) against the Vulkan loader static library.
2019-04-14 17:34:38 +02:00
- [glad2](https://github.com/Dav1dde/glad) for loading OpenGL and Vulkan
functions
Add linmath.h to readme dependency list
2015-08-09 16:58:25 +02:00
- [linmath.h](https://github.com/datenwolf/linmath.h) for linear algebra in
examples
Update repo URL for Nuklear Fixes #1826.
2021-01-03 21:13:02 +01:00
- [Nuklear](https://github.com/Immediate-Mode-UI/Nuklear) for test and example UI
Add stb_image_write
2016-10-13 17:42:44 +02:00
- [stb\_image\_write](https://github.com/nothings/stb) for writing images to disk
Add basic Vulkan support Added GLFW_INCLUDE_VULKAN. Added glfwVulkanSupported, glfwGetRequiredInstanceExtensions, glfwGetInstanceProcAddress, glfwGetPhysicalDevicePresentationSupport and glfwCreateWindowSurface. Added port of LunarG SDK tri example.
2015-08-10 20:19:04 +02:00
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
The documentation is generated with [Doxygen](https://doxygen.org/) if CMake can
Documentation work
2017-07-12 00:21:17 +02:00
find that tool.
Documentation work [ci skip]
2016-02-08 16:23:44 +01:00
Added dependency section to readme.
2014-01-12 05:40:36 +01:00
Documentation work [ci skip]
2016-07-14 18:32:30 +02:00
## Reporting bugs
Bugs are reported to our [issue tracker](https://github.com/glfw/glfw/issues).
Please check the [contribution
Move contribution guide to visible directory
2017-11-20 18:55:43 +01:00
guide](https://github.com/glfw/glfw/blob/master/docs/CONTRIBUTING.md) for
Documentation work [ci skip]
2016-07-14 18:32:30 +02:00
information on what to include when reporting a bug.
Removed more version noise.
2013-06-13 15:09:10 +02:00
## Changelog
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Add runtime platform selection This adds compile-time support for multiple platforms and runtime detection of them. Window system related platform functions are now called from shared code via the function pointer struct _GLFWplatform. The timer, thread and module loading platform functions are still called directly by name and the implementation chosen at link-time. These functions are the same for any backend on a given OS, including the Null backend. The platforms are now enabled via CMake dependent options following the GLFW_BUILD_<platform> pattern instead of a mix of automagic and ad-hoc option names. There is no longer any option for the Null backend as it is now always enabled. Much of the struct stitching work in platform.h was based on an earlier experimental branch for runtime platform selection by @ronchaine. Every platform function related to windows, contexts, monitors, input, event processing and Vulkan have been renamed so that multiple sets of them can exist without colliding. Calls to these are now routed through the _glfw.platform struct member. These changes makes up most of this commit. For Wayland and X11 the client library loading and display creation is used to detect a running compositor/server. The XDG_SESSION_TYPE environment variable is ignored for now, as X11 is still by far the more complete implementation. Closes #1655 Closes #1958
2021-07-13 21:50:09 +02:00
- Added `GLFW_PLATFORM` init hint for runtime platform selection (#1958)
- Added `GLFW_ANY_PLATFORM`, `GLFW_PLATFORM_WIN32`, `GLFW_PLATFORM_COCOA`,
`GLFW_PLATFORM_WAYLAND`, `GLFW_PLATFORM_X11` and `GLFW_PLATFORM_NULL` symbols to
specify the desired platform (#1958)
- Added `glfwGetPlatform` function to query what platform was selected (#1655,#1958)
- Added `glfwPlatformSupported` function to query if a platform is supported
(#1655,#1958)
Add pluggable heap allocator This adds the glfwInitAllocator function for specifying a custom memory allocator to use instead of the C runtime library. The allocator is a struct of type GLFWallocator with fields corresponding to malloc, realloc and free, while the internal API corresponds to calloc, realloc and free. Heap allocation calls are filtered before reaching the user-provided functions, so deallocation of NULL and allocations of zero bytes are not passed on, reallocating NULL is transformed into an allocation and reallocating to size zero is transformed into deallocation. The clearing of a new block to zero is performed by the internal calloc-like function. Closes #544. Fixes #1628. Closes #1947.
2021-08-03 20:53:48 +02:00
- Added `glfwInitAllocator` for setting a custom memory allocator (#544,#1628,#1947)
- Added `GLFWallocator` struct and `GLFWallocatefun`, `GLFWreallocatefun` and
`GLFWdeallocatefun` types (#544,#1628,#1947)
Add glfwInitVulkanLoader This removes the GLFW_VULKAN_STATIC CMake option and the _GLFW_VULKAN_STATIC configuration macro and replaces them with the glfwInitVulkanLoader function, allowing a single library binary to provide both behaviors. This is based on the design from PR #1374 by @pmuetschard. Closes #1374 Closes #1890
2021-10-21 20:45:44 +02:00
- Added `glfwInitVulkanLoader` for using a non-default Vulkan loader (#1374,#1890)
Add more standard cursors This adds the standard cursors for diagonal and omnidirectional resize/move and operation-not-allowed. It also adds new (better?) names for the horizontal and vertical resize/move and pointing hand cursors. References: - https://developer.apple.com/documentation/appkit/nscursor - https://stackoverflow.com/questions/10733228/ - https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setsystemcursor - https://freedesktop.org/wiki/Specifications/cursor-spec/ - https://tronche.com/gui/x/xlib/appendix/b/ Related to #427.
2019-05-07 20:40:37 +02:00
- Added `GLFW_RESIZE_NWSE_CURSOR`, `GLFW_RESIZE_NESW_CURSOR`,
`GLFW_RESIZE_ALL_CURSOR` and `GLFW_NOT_ALLOWED_CURSOR` cursor shapes (#427)
- Added `GLFW_RESIZE_EW_CURSOR` alias for `GLFW_HRESIZE_CURSOR` (#427)
- Added `GLFW_RESIZE_NS_CURSOR` alias for `GLFW_VRESIZE_CURSOR` (#427)
- Added `GLFW_POINTING_HAND_CURSOR` alias for `GLFW_HAND_CURSOR` (#427)
Documentation work for GLFW_MOUSE_PASSTHROUGH Related to #1568.
2020-07-08 23:21:28 +02:00
- Added `GLFW_MOUSE_PASSTHROUGH` window hint for letting mouse input pass
through the window (#1236,#1568)
Add runtime platform selection This adds compile-time support for multiple platforms and runtime detection of them. Window system related platform functions are now called from shared code via the function pointer struct _GLFWplatform. The timer, thread and module loading platform functions are still called directly by name and the implementation chosen at link-time. These functions are the same for any backend on a given OS, including the Null backend. The platforms are now enabled via CMake dependent options following the GLFW_BUILD_<platform> pattern instead of a mix of automagic and ad-hoc option names. There is no longer any option for the Null backend as it is now always enabled. Much of the struct stitching work in platform.h was based on an earlier experimental branch for runtime platform selection by @ronchaine. Every platform function related to windows, contexts, monitors, input, event processing and Vulkan have been renamed so that multiple sets of them can exist without colliding. Calls to these are now routed through the _glfw.platform struct member. These changes makes up most of this commit. For Wayland and X11 the client library loading and display creation is used to detect a running compositor/server. The XDG_SESSION_TYPE environment variable is ignored for now, as X11 is still by far the more complete implementation. Closes #1655 Closes #1958
2021-07-13 21:50:09 +02:00
- Added `GLFW_PLATFORM_UNAVAILABLE` error for platform detection failures (#1958)
Add feature available/implemented errors This adds two new error codes: GLFW_FEATURE_UNAVAILABLE for when a GLFW feature cannot be reasonably implemented on that platform, and GLFW_FEATURE_UNIMPLEMENTED for when it can be but has not been yet. This replaces the current situation where the Wayland code emitted GLFW_PLATFORM_ERROR in both cases while the macOS code silently did nothing. If your application exits on any GLFW error, these error codes should at least be easy to filter out from that behavior. Ideally, GLFW_FEATURE_UNAVAILABLE should be rare and GLFW_FEATURE_UNIMPLEMENTED should never be emitted at all. Fixes #1692.
2020-05-20 18:02:58 +02:00
- Added `GLFW_FEATURE_UNAVAILABLE` error for platform limitations (#1692)
- Added `GLFW_FEATURE_UNIMPLEMENTED` error for incomplete backends (#1692)
EGL: Add support for EGL_ANGLE_platform_angle This adds basic support for selecting the platform type (rendering backend) when running on ANGLE. Related to #1380.
2020-06-25 18:22:08 +02:00
- Added `GLFW_ANGLE_PLATFORM_TYPE` init hint and `GLFW_ANGLE_PLATFORM_TYPE_*`
values to select ANGLE backend (#1380)
Add docs for GLFW_X11_XCB_VULKAN_SURFACE Related to #1793.
2020-12-10 00:11:44 +01:00
- Added `GLFW_X11_XCB_VULKAN_SURFACE` init hint for selecting X11 Vulkan
surface extension (#1793)
Add support for GLFW_NATIVE_INCLUDE_NONE macro By default, the glfw3native.h header will include the platform-specific headers necessary for the return types of GLFW native access functions. Sometimes it is preferrable to declare those types This commit adds support for the GLFW_NATIVE_INCLUDE_NONE macro, which when defined disables the inclusion of all platform-specific headers. Fixes #1348
2022-04-18 23:09:47 +02:00
- Added `GLFW_NATIVE_INCLUDE_NONE` for disabling inclusion of native headers (#1348)
Add runtime platform selection This adds compile-time support for multiple platforms and runtime detection of them. Window system related platform functions are now called from shared code via the function pointer struct _GLFWplatform. The timer, thread and module loading platform functions are still called directly by name and the implementation chosen at link-time. These functions are the same for any backend on a given OS, including the Null backend. The platforms are now enabled via CMake dependent options following the GLFW_BUILD_<platform> pattern instead of a mix of automagic and ad-hoc option names. There is no longer any option for the Null backend as it is now always enabled. Much of the struct stitching work in platform.h was based on an earlier experimental branch for runtime platform selection by @ronchaine. Every platform function related to windows, contexts, monitors, input, event processing and Vulkan have been renamed so that multiple sets of them can exist without colliding. Calls to these are now routed through the _glfw.platform struct member. These changes makes up most of this commit. For Wayland and X11 the client library loading and display creation is used to detect a running compositor/server. The XDG_SESSION_TYPE environment variable is ignored for now, as X11 is still by far the more complete implementation. Closes #1655 Closes #1958
2021-07-13 21:50:09 +02:00
- Added `GLFW_BUILD_WIN32` CMake option for enabling Win32 support (#1958)
- Added `GLFW_BUILD_COCOA` CMake option for enabling Cocoa support (#1958)
- Added `GLFW_BUILD_X11` CMake option for enabling X11 support (#1958)
Add override variable for CMake library type This adds the GLFW_LIBRARY_TYPE CMake cache variable, which allows users and higher-level projects to set what type of library GLFW is built as. When not empty, this value overrides the standard BUILD_SHARED_LIBS option for GLFW while still allowing it to control the type of other libraries in a larger project. This also allows building GLFW as an object library without adding dummy source files (as required by Xcode) or producing unused library binaries. Projects using CMake 3.12 or later can link the resulting GLFW object library normally using target_link_libraries. Fixes #279. Related to #1307. Closes #1497. Closes #1574. Closes #1928.
2021-07-06 23:12:05 +02:00
- Added `GLFW_LIBRARY_TYPE` CMake variable for overriding the library type
(#279,#1307,#1497,#1574,#1928)
Export pkg-config dependencies via the CMake cache This will be useful when building GLFW as a CMake object library and linking it into a larger library that exports pkg-config information. Partly based on #1307 by @a3f. Closes #1307.
2021-07-30 13:19:46 +02:00
- Added `GLFW_PKG_CONFIG_REQUIRES_PRIVATE` and `GLFW_PKG_CONFIG_LIBS_PRIVATE` CMake
variables exposing pkg-config dependencies (#1307)
Make joystick platform code init on demand This makes joystick support initialize the first time a joystick function is called, including those gamepad functions that are layered on top of joystick functions. Related to #1284. Related to #1646.
2020-07-12 18:31:29 +02:00
- Made joystick subsystem initialize at first use (#1284,#1646)
Make GLFW_DOUBLEBUFFER a window attribute
2021-05-13 21:38:46 +02:00
- Made `GLFW_DOUBLEBUFFER` a read-only window attribute
Update minimum required CMake version to 3.1
2019-11-26 18:09:22 +01:00
- Updated the minimum required CMake version to 3.1
Add missing changelog entries
2021-10-28 11:48:34 +02:00
- Updated gamepad mappings from upstream
Disable examples and tests when a subproject This changes the default value of the GLFW_BUILD_EXAMPLES and GLFW_BUILD_TESTS CMake options to false when GLFW is being added as a subdirectory by another CMake project. If you want the previous behavior, force these options to true before adding the GLFW subdirectory: set(GLFW_BUILD_EXAMPLES ON CACHE BOOL "" FORCE) set(GLFW_BUILD_TESTS ON CACHE BOOL "" FORCE) add_subdirectory(path/to/glfw) Doing this is backward compatible with earlier versions of GLFW. The GLFW_BUILD_DOCS option is left enabled as it also requires Doxygen to have any effect, is quicker to build and is more likely to be useful when GLFW is a subproject.
2019-05-08 19:04:21 +02:00
- Disabled tests and examples by default when built as a CMake subdirectory
Add runtime platform selection This adds compile-time support for multiple platforms and runtime detection of them. Window system related platform functions are now called from shared code via the function pointer struct _GLFWplatform. The timer, thread and module loading platform functions are still called directly by name and the implementation chosen at link-time. These functions are the same for any backend on a given OS, including the Null backend. The platforms are now enabled via CMake dependent options following the GLFW_BUILD_<platform> pattern instead of a mix of automagic and ad-hoc option names. There is no longer any option for the Null backend as it is now always enabled. Much of the struct stitching work in platform.h was based on an earlier experimental branch for runtime platform selection by @ronchaine. Every platform function related to windows, contexts, monitors, input, event processing and Vulkan have been renamed so that multiple sets of them can exist without colliding. Calls to these are now routed through the _glfw.platform struct member. These changes makes up most of this commit. For Wayland and X11 the client library loading and display creation is used to detect a running compositor/server. The XDG_SESSION_TYPE environment variable is ignored for now, as X11 is still by far the more complete implementation. Closes #1655 Closes #1958
2021-07-13 21:50:09 +02:00
- Renamed `GLFW_USE_WAYLAND` CMake option to `GLFW_BUILD_WAYLAND` (#1958)
- Removed `GLFW_USE_OSMESA` CMake option enabling the Null platform (#1958)
Remove configuration header
2021-04-15 15:33:19 +02:00
- Removed CMake generated configuration header
Update changelog and add credit
2019-05-02 21:32:14 +02:00
- Bugfix: The CMake config-file package used an absolute path and was not
relocatable (#1470)
Update changelog and add credit Related to #1556.
2019-09-01 20:05:58 +02:00
- Bugfix: Video modes with a duplicate screen area were discarded (#1555,#1556)
Update changelog
2019-10-16 17:43:29 +02:00
- Bugfix: Compiling with -Wextra-semi caused warnings (#1440)
Update changelog and add credit
2020-01-01 01:42:25 +01:00
- Bugfix: Built-in mappings failed because some OEMs re-used VID/PID (#1583)
Clarify docs on default GL header inclusion The documentation claims that any extension loader library header included before the GLFW one will prevent the inclusion of the default OpenGL header. In reality this only worked if the loader defined the canonical desktop OpenGL __gl_h_ inclusion guard and even then relied on the OpenGL header to detect this. This is the companion to 105cf32e0b05e207d4cd5efa462887569ca2116a, which added the preprocessor logic to check for many known OpenGL and OpenGL ES inclusion guards and not even attempt to include the default header if any are present. Some clarification of the language around header inclusion has also been attempted, including making GLFW_INCLUDE_NONE more prominent. Fixes #1695.
2020-05-28 17:38:21 +02:00
- Bugfix: Some extension loader headers did not prevent default OpenGL header
inclusion (#1695)
Skip initial buffer swap when single-buffered This skips the buffer swap after the initial glClear performed during window creation, if the window is single-buffered. This call confused apitrace into thinking the window was double-buffered. Fixes #1873.
2021-05-13 21:41:51 +02:00
- Bugfix: Buffers were swapped at creation on single-buffered windows (#1873)
Remove errors for gamepad element mismatch Because there are controllers in the wild using the same hardware ID despite having different numbers of buttons and axes, an error message was triggered that was only expected for a corrupted mapping database. This removes the error for now, in preparation for better error handling for gamepad mappings overall. Fixes #1763.
2021-06-25 19:49:38 +02:00
- Bugfix: Gamepad mapping updates could spam `GLFW_INVALID_VALUE` due to
incompatible controllers sharing hardware ID (#1763)
Make native access functions verify context API The native access functions for context handles did not verify that the context had been created with the same API the function was for. This makes these functions emit GLFW_NO_WINDOW_CONTEXT on API mismatch.
2021-10-04 20:32:32 +02:00
- Bugfix: Native access functions for context handles did not check that the API matched
Fix glfwMakeContextCurrent using uninitialized TLS Issue reported by danhambleton on the GLFW forum: https://discourse.glfw.org/t/posix-thread-local-storage-tls-error-when-making-context-current/2034
2022-04-08 18:22:39 +02:00
- Bugfix: `glfwMakeContextCurrent` would access TLS slot before initialization
Fix order of error checks in glfwSetGammaRamp Initialization should be checked before arguments.
2022-04-21 15:37:31 +02:00
- Bugfix: `glfwSetGammaRamp` could emit `GLFW_INVALID_VALUE` before initialization
Fix joystick user pointer NULL during disconnect The joystick code did not distinguish between the allocation status of the GLFW joystick object and whether it is connection to an OS level joystick object. These are now tracked separately. Fixes #2092
2022-05-05 22:23:12 +02:00
- Bugfix: `glfwGetJoystickUserPointer` returned `NULL` during disconnection (#2092)
Win32: Add GLFW_WIN32_KEYBOARD_MENU This platform specific window hint enables access to the Windows window menu via the keyboard shortcuts.
2019-08-20 19:00:59 +02:00
- [Win32] Added the `GLFW_WIN32_KEYBOARD_MENU` window hint for enabling access
to the window menu
Win32: Add VERSIONINFO resource to GLFW DLL This will let people see the API version in the Explorer property box.
2019-12-11 19:09:59 +01:00
- [Win32] Added a version info resource to the GLFW DLL
Win32: Add separate window class for helper window The current window procedure needs to deal with messages both for user created windows and the hidden helper window. This commit separates out the device message handling of the helper window, allowing both window procedures to be less complicated.
2022-03-27 19:40:35 +02:00
- [Win32] Made hidden helper window use its own window class
Win32: Disable fb transparency when it is broken On Windows 7, when GLFW framebuffer transparency and the DWM are enabled but DWM transparency is disabled (i.e. when the Transparency setting is disabled under Personalization > Color), the contents of the framebuffer is combined with the last frame using additive blending instead of replacing the previous contents. This commit limits GLFW framebuffer transparency on Windows 7 to when DWM transparency is enabled, removing the previous workaround of setting a layered window color key that led to rendering artifacts. Fixes #1512.
2020-07-28 00:12:45 +02:00
- [Win32] Disabled framebuffer transparency on Windows 7 when DWM windows are
opaque (#1512)
Win32: Fix symbol redefinition warnings When both GLFW_INCLUDE_VULKAN and VK_USE_PLATFORM_WIN32_KHR were defined, the GLFW header would define replacement versions of APIENTRY and WINGDIAPI /before/ including the Vulkan header, which would include windows.h, which (justifiably) defines APIENTRY and WINGDIAPI blindly. Fixes #1524.
2019-07-12 14:23:12 +02:00
- [Win32] Bugfix: `GLFW_INCLUDE_VULKAN` plus `VK_USE_PLATFORM_WIN32_KHR` caused
symbol redefinition (#1524)
Documentation work [ci skip]
2019-07-12 19:04:16 +02:00
- [Win32] Bugfix: The cursor position event was emitted before its cursor enter
event (#1490)
Win32: Fix GLFW_MAXIMIZED not maximizing window The window rect adjustment for content scale broke the initial, correct maximization performed when creating the window with WS_MAXIMIZE. This switches to updating the restored rect instead of the current rect. Fixes #1499. Closes #1503.
2019-08-13 15:18:02 +02:00
- [Win32] Bugfix: The window hint `GLFW_MAXIMIZED` did not move or resize the
window (#1499)
Update changelog and add credit
2020-01-01 01:42:25 +01:00
- [Win32] Bugfix: Disabled cursor mode interfered with some non-client actions
Win32: Fix no Super key release event after Win+V The Win+V hotkey brings up a clipboard history IME that consumes the key release. This adds left and right Super to the modifier keys manually polled for undetected release during event processing. Fixes #1622.
2020-01-15 16:19:56 +01:00
- [Win32] Bugfix: Super key was not released after Win+V hotkey (#1622)
Check scancode before use in glfwGetKeyName
2020-01-15 16:34:58 +01:00
- [Win32] Bugfix: `glfwGetKeyName` could access out of bounds and return an
invalid pointer
Win32: Fix scancode when key message only had VK Some synthetic key messages come with a scancode of zero, causing them to be translate to GLFW_KEY_UNKNOWN. This fills in the missing scancode by translating the provided virtual key. Rather than further complicate a single-use function, its body is merged into the key message handler. Fixes #1623.
2020-01-15 18:54:42 +01:00
- [Win32] Bugfix: Some synthetic key events were reported as `GLFW_KEY_UNKNOWN`
(#1623)
Win32: Fix non-BMP Unicode codepoint input Supplementary Plane codepoints from WM_CHAR and WM_SYSCHAR messages were reported as UTF-16 surrogate pairs. Related to #1635.
2020-06-29 20:43:28 +02:00
- [Win32] Bugfix: Non-BMP Unicode codepoint input was reported as UTF-16
Update changelog Related to #1761.
2020-09-23 23:34:42 +02:00
- [Win32] Bugfix: Monitor functions could return invalid values after
configuration change (#1761)
Update changelog and add credit Related to #1775.
2020-09-29 20:16:59 +02:00
- [Win32] Bugfix: Initialization would segfault on Windows 8 (not 8.1) (#1775)
Win32: Filter out duplicate size events This mirrors the filtering done on X11 and Cocoa. Possibly this should be done by shared code instead. Fixes #1610.
2020-10-07 23:35:17 +02:00
- [Win32] Bugfix: Duplicate size events were not filtered (#1610)
Win32: Fix full screen windows affected by scaling Per-monitor DPI scaling should not affect full screen windows. Fixes #1582.
2021-01-19 22:25:05 +01:00
- [Win32] Bugfix: Full screen windows were incorrectly resized by DPI changes
(#1582)
Win32: Fix content area rescaling on older systems GLFW_SCALE_TO_MONITOR had no effect on Windows 8.1 up to and including Windows 10 version 1607 (Anniversary Update), despite those having support for per-monitor DPI. That done was to avoid handling systems that have non-client scaling, introduced in Windows 10 version 1607, without reliable overriding of the new window size, introduced in Windows 10 version 1703 (Creators Update). Both are needed to keep the content area at a fixed size for windows that have GLFW_SCALE_TO_MONITOR disabled. This change enables window rescaling on Windows 8.1 and all later versions but disables non-client scaling for unscaled windows on Windows 10 version 1607. Versions after 1607 are unaffected. Fixes #1511.
2021-01-20 01:02:24 +01:00
- [Win32] Bugfix: `GLFW_SCALE_TO_MONITOR` had no effect on systems older than
Windows 10 version 1703 (#1511)
Update USE_MSVC_RUNTIME_LIBRARY_DLL for CMake 3.15 This makes USE_MSVC_RUNTIME_LIBRARY_DLL update the directory scope CMAKE_MSVC_RUNTIME_LIBRARY variable instead of CMAKE_C_FLAGS on CMake 3.15 and later. Solution proposed by @moritz-h. Fixes #1783. Closes #1796.
2020-10-12 23:47:35 +02:00
- [Win32] Bugfix: `USE_MSVC_RUNTIME_LIBRARY_DLL` had no effect on CMake 3.15 or
later (#1783,#1796)
Win32: Fix compilation with standalone LLVM The /clang: suffix passed to Clang-CL was accidentally also passed to the regular standalone Clang, which caused compilation to fail. We now pass /W3 to Clang-CL, which it interprets as -Wall. The _CRT_SECURE_NO_WARNINGS macro is now defined for both Clang and Clang-CL. The /entry: flag passed to link.exe is now also passed to lld-link, letting the windows subsystem tests and examples link. Fixes #1807. Closes #1824. Closes #1874.
2021-04-12 20:56:53 +02:00
- [Win32] Bugfix: Compilation with LLVM for Windows failed (#1807,#1824,#1874)
Win32: Remove changing the foreground lock timeout It's rude to ignore the foreground lock timeout, especially by default. Discussion of this code and its removal: https://discourse.glfw.org/t/why-is-spi-setforegroundlocktimeout-set-to-zero-on-glfwinit-win32
2021-08-02 21:42:36 +02:00
- [Win32] Bugfix: The foreground lock timeout was overridden, ignoring the user
Win32: Fix bad content scale on monitor disconnect The monitor handle could have become invalid just before the call to GetDpiForMonitor. It was possible for both window and monitor content scale queries. This ensures both that an appropriate error is emitted and that the retrieved values are zero on error. Fixes #1615
2021-12-01 17:55:16 +01:00
- [Win32] Bugfix: Content scale queries could fail silently (#1615)
- [Win32] Bugfix: Content scales could have garbage values if monitor was recently
disconnected (#1615)
Win32: Fix rect of undecorated maximized windows A window created maximized and undecorated would cover the whole monitor Windows placed it on instead of just that monitor's workarea. This commit adjusts the maximized rect to cover just the workarea, similar to how undecorated windows that become maximized are handled during WM_GETMINMAXINFO. Fixes #1806
2022-03-07 18:14:16 +01:00
- [Win32] Bugfix: A window created maximized and undecorated would cover the whole
monitor (#1806)
Win32: Fix scale fixup losing initial position The window content scale correction at creation overwrote the inital, more pleasant placement of the window by CW_USEDEFAULT, if the window was created with GLFW_MAXIMIZED set. This is because the translation to screen coordinates was done using the current position, not the position from the restored window rect.
2022-03-07 19:19:31 +01:00
- [Win32] Bugfix: The default restored window position was lost when creating a maximized
window
Win32: Fix maximization showing a hidden window The normal way of maximizing a window also makes it visible. This implements window maximization manually for when the window passed to glfwMaximizeWindow is hidden. This will very likely not be forward-compatible and should be replaced.
2022-03-08 23:00:47 +01:00
- [Win32] Bugfix: `glfwMaximizeWindow` would make a hidden window visible
Win32: Fix scancode and key for Alt+PrtSc events Alt+PrtSc emits a different scancode than just PrtSc. Since the GLFW API assumes each key corresponds to only one scancode, this cannot be added to the keycodes array. Instead we replace the scancode at the point of entry. Fixes #1993
2022-03-15 19:12:29 +01:00
- [Win32] Bugfix: `Alt+PrtSc` would emit `GLFW_KEY_UNKNOWN` and a different
scancode than `PrtSc` (#1993)
Win32: Fix glfwGetKeyScancode for GLFW_KEY_PAUSE The bug described in 03cfe957e739e41cdfd66b554c076b5b31f48c1e was already present for another key where modifiers changes its scancode. Related to #1993
2022-03-15 19:22:21 +01:00
- [Win32] Bugfix: `GLFW_KEY_PAUSE` scancode from `glfwGetKeyScancode` did not
match event scancode (#1993)
Win32: Fix using executable instance and not ours Operations that take an instance handle should be passed the handle of whatever module we are inside instead of blindly passing the handle of the executable. This commit makes GLFW retrieve its own instance on initialization. This makes the most difference for window classes, which are per-instance. Using the executable instance led to name conflicts if there were several copies of GLFW in a single process. Note that having this is still a bad idea unless you know what things to avoid, and those things are mostly platform-specific. This is partly because the library wasn't designed for it and partly because it needs to save, update and restore various per-process and per-session settings like current context and video mode. However, multiple simultaneous copies of GLFW in a single Win32 process should now at least initialize, like is already the case on other platforms. Fixes #469 Fixes #1296 Fixes #1395 Related to #927 Related to #1885
2022-03-17 23:54:39 +01:00
- [Win32] Bugfix: Instance-local operations used executable instance (#469,#1296,#1395)
Win32: Fix OSMesa library not being unloaded
2022-04-28 21:12:36 +02:00
- [Win32] Bugfix: The OSMesa library was not unloaded on termination
Cocoa: Select Vulkan surface extension at runtime This mostly just follows the pattern established by X11. Related to #1619.
2020-01-16 01:52:50 +01:00
- [Cocoa] Added support for `VK_EXT_metal_surface` (#1619)
Cocoa: Add fully dynamic loading of Vulkan loader If the application is not linked against the Vulkan loader and relies on a third-party loader library or glfwGetInstanceProcAddress, then our call to dlopen will fail without a custom dyld environment variable. This adds a fallback of looking in the directory of the main executable, which matches the bundle structure recommended by the Vulkan SDK, making that finally work out of the box for fully dynamic loading.
2020-01-16 05:09:19 +01:00
- [Cocoa] Added locating the Vulkan loader at runtime in an application bundle
Cocoa: Finish launching NSApp in glfwInit This moves the remaining bits of NSApplication initialization into _glfwPlatformInit. As a side-effect of this, any command-line program initializing GLFW will get a menu bar, which is not ideal. If this has happened to you and a bisect led you here, please see the GLFW_COCOA_MENUBAR init hint introduced in GLFW 3.3. If this patch is a terrible idea, please get in touch in the 3.4 release timeframe. This is a replacement for 6e6805000ac7ddf39c8c5f6be3e877770cba5083, which attempts to preserve the existing menu bar creation behavior for the 3.3-stable branch. Fixes #1649.
2020-03-05 20:32:19 +01:00
- [Cocoa] Moved main menu creation to GLFW initialization time (#1649)
Fix format of change log entry
2020-06-29 21:14:29 +02:00
- [Cocoa] Changed `EGLNativeWindowType` from `NSView` to `CALayer` (#1169)
Update changelog and add credit Related to #1786.
2020-10-20 20:03:58 +02:00
- [Cocoa] Changed F13 key to report Print Screen for cross-platform consistency
(#1786)
Cocoa: Disable macOS fullscreen when non-resizable Windows with GLFW_RESIZABLE set to false should not be resizable by the user.
2022-06-30 21:11:10 +02:00
- [Cocoa] Disabled macOS fullscreen when `GLFW_RESIZABLE` is false
Cocoa: Replace display link with IOKit query This removes the final dependency on CoreVideo, using a display link to get the refresh rate of monitors where Core Graphics report a refresh rate of zero. Instead we now query the I/O registry directly, similarly to what the display link does at creation. Thanks to @OneSadCookie for pointers to this solution.
2019-12-25 17:09:38 +01:00
- [Cocoa] Removed dependency on the CoreVideo framework
Cocoa: Fix glfwSetWindowSize anchor point This makes glfwSetWindowSize use the top-left corner as anchor point instead of the bottom-left corner. Fixes #1553.
2019-08-29 22:08:29 +02:00
- [Cocoa] Bugfix: `glfwSetWindowSize` used a bottom-left anchor point (#1553)
Cocoa: Process events after window destruction On macOS a destroyed window remained on screen until the next time events were processed. This makes the behavior more consistent with other platforms. Fixes #1412.
2019-11-06 23:34:08 +01:00
- [Cocoa] Bugfix: Window remained on screen after destruction until event poll
(#1412)
Cocoa: Fix pre-window-creation event processing Polling the event queue before NSApp had been allowed to finish launching, in our case by starting our self-terminating run loop, triggered an assertion inside NSApplication. This fix, which makes all event processing functions capable of starting it, makes that assertion less likely. A more Cocoa-friendly fix would be to finish launching NSApp during glfwInit and let people annoyed by the menu bar disabled it with GLFW_COCOA_MENUBAR. That may not be suitable for 3.3-stable, though. Fixes #1543.
2019-11-27 23:21:13 +01:00
- [Cocoa] Bugfix: Event processing before window creation would assert (#1543)
Update changelog and add credit
2020-01-01 01:42:25 +01:00
- [Cocoa] Bugfix: Undecorated windows could not be iconified on recent macOS
Cocoa: Finish launching NSApp in glfwInit This moves the remaining bits of NSApplication initialization into _glfwPlatformInit. As a side-effect of this, any command-line program initializing GLFW will get a menu bar, which is not ideal. If this has happened to you and a bisect led you here, please see the GLFW_COCOA_MENUBAR init hint introduced in GLFW 3.3. If this patch is a terrible idea, please get in touch in the 3.4 release timeframe. This is a replacement for 6e6805000ac7ddf39c8c5f6be3e877770cba5083, which attempts to preserve the existing menu bar creation behavior for the 3.3-stable branch. Fixes #1649.
2020-03-05 20:32:19 +01:00
- [Cocoa] Bugfix: Touching event queue from secondary thread before main thread
would abort (#1649)
Cocoa: Fix non-BMP Unicode codepoint input Supplimentary Plane codepoints were reported as UTF-16 surrogate pairs. Fixes #1635.
2020-06-29 21:16:59 +02:00
- [Cocoa] Bugfix: Non-BMP Unicode codepoint input was reported as UTF-16
(#1635)
Cocoa: Fix potential leak of CFNumber object Spotted by Clang static analysis.
2020-07-23 18:55:29 +02:00
- [Cocoa] Bugfix: Failing to retrieve the refresh rate of built-in displays
could leak memory
Cocoa: Fix ObjC being built as C with CMake 3.19 CMake 3.19 adds -xc when the LANGUAGE file property is C, breaking our workaround for CMake 3.15 and earlier not understanding the .m suffix. Fixes #1787.
2020-10-18 19:34:23 +02:00
- [Cocoa] Bugfix: Objective-C files were compiled as C with CMake 3.19 (#1787)
Update changelog
2021-01-18 16:24:27 +01:00
- [Cocoa] Bugfix: Duplicate video modes were not filtered out (#1830)
Fix some spelling errors in changelog
2021-10-27 23:58:59 +02:00
- [Cocoa] Bugfix: Menu bar was not clickable on macOS 10.15+ until it lost and
Cocoa: Fix menubar for unbundled apps on 10.15 NSApp setActivationPolicy: was being called too soon when the app was not bundled and launched from the command line. This fix is based on #1802 by @richardwilkes. Fixes #1648. Closes #1802.
2020-12-08 23:23:20 +01:00
regained focus (#1648,#1802)
Update changelog and add credit Related to #1833.
2021-01-18 01:34:55 +01:00
- [Cocoa] Bugfix: Monitor name query could segfault on macOS 11 (#1809,#1833)
Update changelog and add credit
2021-01-18 18:55:17 +01:00
- [Cocoa] Bugfix: The install name of the installed dylib was relative (#1504)
Cocoa: Fix MoltenVK layer scale out of sync The contents scale of the hosted CAMetalLayer created for MoltenVK was updated only after the GLFW content scale and framebuffer size events were emitted, causing the layer to get out of sync with the monitor the window was on.
2021-07-16 20:04:56 +02:00
- [Cocoa] Bugfix: The MoltenVK layer contents scale was updated only after
related events were emitted
Cocoa: Fix unresponsive cursor after cursor warp This is a companion to 157ebb80aafe263b86fd450f21a193f0412fb717 and fixes the same issue for calls to glfwSetCursorPos. Related to #1962
2021-09-12 17:15:59 +02:00
- [Cocoa] Bugfix: Moving the cursor programmatically would freeze it for
a fraction of a second (#1962)
Fix some spelling errors in changelog
2021-10-27 23:58:59 +02:00
- [Cocoa] Bugfix: `kIOMasterPortDefault` was deprecated in macOS 12.0 (#1980)
Cocoa: Fix deprecation warning for kUTTypeURL We switched to kUTTypeURL when NSURLPboardType was deprecated, as the official replacement symbol NSPasteboardTypeURL was not available on every version of macOS supported by GLFW. kUTTypeURL has now also been deprecated. This commit moves to a compile-time choice between NSURLPboardType and NSPasteboardTypeURL depending on the minimum targeted macOS version. Fixes #2003
2022-02-02 19:20:32 +01:00
- [Cocoa] Bugfix: `kUTTypeURL` was deprecated in macOS 12.0 (#2003)
Cocoa: Fix AirPlay causing harmless init error Emitting an error for one specific type of failure in retrieving the correct name for a display is not very useful, especially when initialization is otherwise unaffected. There should be a path for information like that but this isn't it. Fixes #1791
2022-03-18 00:31:34 +01:00
- [Cocoa] Bugfix: A connected Apple AirPlay would emit a useless error (#1791)
Cocoa: Fix EGL and OSMesa not being unloaded
2022-04-28 21:14:11 +02:00
- [Cocoa] Bugfix: The EGL and OSMesa libraries were not unloaded on termination
Cocoa: Fix GLFW_MAXIMIZED for nonresizable windows The reasoning here is that glfwRestoreWindow will change nothing for a windowed non-resizable window on Cocoa, and silently refusing to maximize seems slightly more like something other platforms would do. This is possibly either the right thing to do or the wrong one.
2022-06-30 22:08:52 +02:00
- [Cocoa] Bugfix: `GLFW_MAXIMIZED` was always true when `GLFW_RESIZABLE` was false
X11: Fix CMake not checking for XInput2 headers Fixes #1480.
2019-05-07 17:03:55 +02:00
- [X11] Bugfix: The CMake files did not check for the XInput headers (#1480)
Update changelog Related to #1528.
2019-07-11 20:21:04 +02:00
- [X11] Bugfix: Key names were not updated when the keyboard layout changed
(#1462,#1528)
X11: Fix decoration enabling after window creation This fixes the enabling of window decorations after creation. Instead of removing the _MOTIF_WM_HINTS property, we now set or unset the MWM_DECOR_ALL bit of the decorations field. Fixes #1566.
2019-09-26 18:29:37 +02:00
- [X11] Bugfix: Decorations could not be enabled after window creation (#1566)
X11: Fix content scale fallback value on KDE KDE sometimes removes the Xft.dpi resource when it would be set to the X11 default value of 96, causing GLFW to fall back to a value calculated from the core display sizes in pixels and mm in a desktop environment that supports Xft.dpi. This moves to a hardcoded fallback value of 96 on the assumption that there are more people running KDE with 96 DPI than there are people running desktop environments that do not support Xft.dpi. All of this is terrible please send help. Fixes #1578.
2019-10-28 19:18:19 +01:00
- [X11] Bugfix: Content scale fallback value could be inconsistent (#1578)
X11: Fix maximization of hidden windows This fixes glfwMaximizeWindow having no effect on hidden windows by manually appending the maximization states to the EWMH state property.
2019-12-16 14:53:06 +01:00
- [X11] Bugfix: `glfwMaximizeWindow` had no effect on hidden windows
X11: Fix invalid read when clearing GLFW_FLOATING
2019-12-17 01:43:08 +01:00
- [X11] Bugfix: Clearing `GLFW_FLOATING` on a hidden window caused invalid read
X11: Fix updating GLFW_FLOATING on a hidden window
2019-12-16 16:09:52 +01:00
- [X11] Bugfix: Changing `GLFW_FLOATING` on a hidden window could silently fail
Update changelog and add credit
2020-01-01 01:42:25 +01:00
- [X11] Bugfix: Disabled cursor mode was interrupted by indicator windows
- [X11] Bugfix: Monitor physical dimensions could be reported as zero mm
X11: Fix no window position events during resize A window resize action that also resulting in the window being moved did not emit any window positions events, as the position of real ConfigureNotify events was ignored. The real events use parent coordinates instead of root coordinates so this adds parent tracking and conditional translation. Fixes #1613.
2020-01-01 16:56:32 +01:00
- [X11] Bugfix: Window position events were not emitted during resizing (#1613)
X11: Fix BadMatch focusing a window on non-EWMH WM When the WM does not support EWMH or there is no WM running, GLFW falls back to XSetInputFocus, which will emit BadMatch if the window is not viewable, which will terminate the program. Bug spotted on IRC.
2020-01-05 14:34:39 +01:00
- [X11] Bugfix: `glfwFocusWindow` could terminate on older WMs or without a WM
Update changelog and add credit Related to #1602.
2020-01-16 21:12:37 +01:00
- [X11] Bugfix: Querying a disconnected monitor could segfault (#1602)
X11: Fix CJK IME input when locale CTYPE is "C" Fixes #1587. Fixes #1636.
2020-02-06 15:46:37 +01:00
- [X11] Bugfix: IME input of CJK was broken for "C" locale (#1587,#1636)
X11: Add support for XIM callbacks This adds support for the XIM instantiate and destroy callbacks, letting GLFW detect both when the current input method disappears and when a new one is started. Tested with ibus.
2020-01-22 20:12:36 +01:00
- [X11] Bugfix: Termination would segfault if the IM had been destroyed
- [X11] Bugfix: Any IM started after initialization would not be detected
X11: Filter out Xlib errors from other connections
2020-03-16 17:13:59 +01:00
- [X11] Bugfix: Xlib errors caused by other parts of the application could be
reported as GLFW errors
X11: Improve window handle race condition The non-root parent window owned by the WM could be destroyed before we process the ConfigureNotify event using the cached parent handle. Bug was found by unmapping a decorated window. This like all uses of the Xlib error handler is not thread safe and there is nothing we can do about that short of moving to XCB. Fixes #1633.
2020-03-19 23:28:21 +01:00
- [X11] Bugfix: A handle race condition could cause a `BadWindow` error (#1633)
Update changelog and add credit Related to #1598.
2020-03-31 17:30:22 +02:00
- [X11] Bugfix: XKB path used keysyms instead of physical locations for
non-printable keys (#1598)
- [X11] Bugfix: Function keys were mapped to `GLFW_KEY_UNKNOWN` for some layout
Fix some spelling errors in changelog
2021-10-27 23:58:59 +02:00
combinations (#1598)
X11: Fix detection of key events duplicated by XIM Background: The IM will filter out key events, instead sending exact duplicate events that are not filtered. It does not send these for every event, however, so the duplicate events cannot be relied on for key input. Instead we need to identify and discard them. Since they are identical, they have the same timestamp as the originals. The previous duplicate event detection would consume unrelated key events if the keys were pressed simultaneously, as it only tracked a single timestamp. This fixes that issue for any combination of keys, at the expense of a 1 KB array per GLFW window. This fix is a stopgap until explicit IME support is done. Based on #1472 by @LucaRood. Fixes #1112. Fixes #1415. Fixes #1616. Fixes #1663. Closes #1472.
2020-06-30 20:57:24 +02:00
- [X11] Bugfix: Keys pressed simultaneously with others were not always
reported (#1112,#1415,#1472,#1616)
X11: Fix attribs not applied on leaving fullscreen If the GLFW_DECORATED and/or GLFW_FLOATING window attributes were changed while in fullscreen mode, the changes did not take effect when the window entered windowed mode. Bug reported on the GLFW forum. https://discourse.glfw.org/t/turning-on-off-window-decorations-while-in-full-screen-wont-work-properly/1780
2021-03-08 19:32:36 +01:00
- [X11] Bugfix: Some window attributes were not applied on leaving fullscreen
Add issue number to changelog Related to #1863.
2021-03-19 14:47:28 +01:00
(#1863)
X11: Fix function returning before cleanup The _glfwPlatformSetWindowFloating function would return without freeing the state array if the window was already in the requested state.
2021-08-15 14:55:13 +02:00
- [X11] Bugfix: Changing `GLFW_FLOATING` could leak memory
Add credits and update changelog
2021-11-02 23:15:05 +01:00
- [X11] Bugfix: Icon pixel format conversion worked only by accident, relying on
undefined behavior (#1986)
X11: Fix sonames for loaded libraries on OpenBSD The OpenBSD ports tree assigns its own soname version numbers, so the hardcoded sonames GLFW uses to load libraries on non-macOS Unices are often incorrect. Instead OpenBSD recommends that run-time loading should leave out the version numbers entirely. The OpenBSD ld.so then finds the correct library. This upstreams the ports tree fixes for Xcursor and EGL, and adds the corresponding fix for all other run-time loaded library sonames. Tested on OpenBSD 7.0. This issue was initially reported on IRC.
2021-12-22 22:19:25 +01:00
- [X11] Bugfix: Dynamic loading on OpenBSD failed due to soname differences
X11: Fix event polling when event fd > 1023 This replaces select with poll for checking for data on event file descriptors, as select cannot handle file descriptors larger than 1023. Closes #2024
2022-02-01 22:05:55 +01:00
- [X11] Bugfix: Waiting for events would fail if file descriptor was too large
(#2024)
X11: Fix joystick events causing busy waiting On Linux, the inotify descriptor was included in the set used for select, but could not break the outer loop, leading to busy waiting until timeout or the correct X11 event arrived. This commit adds a new function for waiting just on X11 events. Fixes #1872
2022-02-18 15:19:16 +01:00
- [X11] Bugfix: Joystick events could lead to busy-waiting (#1872)
X11: Fix glfwWaitEvents* ignoring joystick events The data available on the X11 connection may be a reply or an internal event for an X11 extension. Previously the check for whether an event was available for us was done outside waitForEvent. This prevented data available on other file descriptors from breaking the outer wait loop. This commit moves the check for whether an event is available into the wait functions, where there is enough knowledge to limit the check to the X11 connection. Related to #932
2022-02-18 15:20:10 +01:00
- [X11] Bugfix: `glfwWaitEvents*` did not continue for joystick events
X11: Fix empty event race condition with a pipe There is a seemingly unavoidable race condition when waiting for data on the X11 display connection, as long as any other thread is also making Xlib calls. The event data we are waiting for could be read by the other thread as part of looking for the reply to its request, before our poll has begun. This commit replaces the X11 event sent by glfwPostEmptyEvent with writing to an unnamed pipe. The race condition remains if other Xlib calls are made on other threads, but glfwPostEmptyEvent should now be race-free. This commit is based on work by pcwalton, OlivierSohn, kovidgoyal and joaodasilva. Closes #2033 Related to #379 Related to #1281 Related to #1285
2022-02-18 14:29:43 +01:00
- [X11] Bugfix: `glfwPostEmptyEvent` could be ignored due to race condition
(#379,#1281,#1285,#2033)
X11: Fix sonames for loaded libraries on NetBSD The NetBSD sonames for X11 and related libraries is more stable than on OpenBSD but the version numbers are still bumped more often than their Linux counterparts, even excluding the one-time version bump across all X11 related libraries. This commit moves to using version-less sonames for X11 and related libraries on NetBSD, which will hopefully be more forward-compatible than hard-coding NetBSD-specific sonames. This may not be the correct long-term solution but it runs now. Binaries also appear to need an LD_LIBRARY_PATH or rpath entry of /usr/X11R7/lib in order for the libraries to be found by dlopen. Tested on NetBSD 9.2.
2022-02-23 18:47:30 +01:00
- [X11] Bugfix: Dynamic loading on NetBSD failed due to soname differences
Update changelog and add credit Related to #1951
2022-03-10 20:04:56 +01:00
- [X11] Bugfix: Left shift of int constant relied on undefined behavior (#1951)
X11: Fix OSMesa library not being unloaded
2022-04-28 21:17:39 +02:00
- [X11] Bugfix: The OSMesa libray was not unloaded on termination
X11: Fix segfault on malformed INCR response The code assumed that at least some data would be received via the INCR mechanism and that, as a result, the string buffer would be allocated. Bug found by Clang static analysis.
2022-04-18 23:22:25 +02:00
- [X11] Bugfix: A malformed response during selection transfer could cause a segfault
X11: Fix previous error handler not being restored GLFW did not restore the previous Xlib error handler when removing its own, instead resetting to the default handler. This commit saves and restores the previous error handler. None of this is thread-safe or could ever be. Fixes #2108
2022-05-25 19:43:55 +02:00
- [X11] Bugfix: Some calls would reset Xlib to the default error handler (#2108)
Wayland: Make libwayland-client dynamically loaded The insight to use wayland.xml to resolve the difficult-to-redirect interface symbols was gleaned from SDL. Instead of compiling the code output of wayland-scanner separately it is made part of the wl_init compilation unit. This lets us do things like transparently rename our copies of Wayland globals. The OS version of wayland-client-protocol.h is no longer used by GLFW, but it is presumably ABI compatible with the output of wayland-scanner. Closes #1174. Closes #1338. Related to #1655. Closes #1943.
2021-07-13 18:12:43 +02:00
- [Wayland] Added dynamic loading of all Wayland libraries
Wayland: Implement key name support
2021-12-29 23:45:06 +01:00
- [Wayland] Added support for key names via xkbcommon
Wayland: Add support for file drop events This adds support for file path drop events in text/uri-list format. It is based on work by Pilzschaf in #2040. Closes #2040
2022-03-31 19:56:48 +02:00
- [Wayland] Added support for file path drop events (#2040)
Wayland: Add support for wl_output::name We now use wl_output::name as the GLFW monitor name, on compositors that provide this event.
2022-06-14 18:20:56 +02:00
- [Wayland] Added support for more human-readable monitor names where available
Update changelog
2020-01-01 01:43:40 +01:00
- [Wayland] Removed support for `wl_shell` (#1443)
Wayland: Fix pointing hand cursor shape Related to #1432.
2019-05-17 18:30:02 +02:00
- [Wayland] Bugfix: The `GLFW_HAND_CURSOR` shape used the wrong image (#1432)
Fix POSIX conformance issues for clock_gettime CLOCK_MONOTONIC should not be used as a feature macro. The POSIX feature macros are provided by unistd.h. CLOCK_MONOTONIC is provided by time.h. CLOCK_MONOTONIC requires _POSIX_C_SOURCE >= 199309L on some systems.
2019-12-15 17:24:26 +01:00
- [Wayland] Bugfix: `CLOCK_MONOTONIC` was not correctly enabled
Wayland: Fix repeated keys reported to NULL window This fixes a race between the key repeat logic and the surface leave event handler, which could result in repeated keys being reported with a window of NULL. Fixes #1704.
2020-06-02 19:54:30 +02:00
- [Wayland] Bugfix: Repeated keys could be reported with `NULL` window (#1704)
Wayland: Fix partial framebuffer size retrieval
2020-07-15 21:56:52 +02:00
- [Wayland] Bugfix: Retrieving partial framebuffer size would segfault
Wayland: Fix scroll offsets being inverted Scrolling offsets were inverted compared to X11 and Win32. Fixes #1463.
2020-07-15 23:11:19 +02:00
- [Wayland] Bugfix: Scrolling offsets were inverted compared to other platforms
(#1463)
Fix some spelling errors in changelog
2021-10-27 23:58:59 +02:00
- [Wayland] Bugfix: Client-Side Decorations were destroyed in the wrong order
Add missing changelog issue number
2020-11-19 02:49:14 +01:00
(#1798)
Update changelog
2021-02-17 21:21:49 +01:00
- [Wayland] Bugfix: Monitors physical size could report zero (#1784,#1792)
Wayland: Fix some keys not repeating According to the libxkbcommon documentation[1], xkb_keymap_key_repeats requires keymap and keycode as input: int xkb_keymap_key_repeats( struct xkb_keymap * keymap, xkb_keycode_t key) However, in inputChar in wl_input.c we are passing in xkb_keysym_t, which was a type mismatch. This results in some keys not repeating when they should and vice versa. [1] https://xkbcommon.org/doc/current/group__components.html#ga9d7f998efeca98b3afc7c257bbac90a8 Closes #1908.
2021-06-01 22:40:44 +02:00
- [Wayland] Bugfix: Some keys were not repeating in Wayland (#1908)
Wayland: Fix cursor offset when shape changes The Wayland protocol spec[1] states that set_cursor must be called with the serial number of the enter event. However, GLFW is passing in the serial number of the latest received event, which does not meet the protocol spec. [1] https://wayland.freedesktop.org/docs/html/apa.html#protocol-spec-wl_pointer As a result, set_cursor calls were simply ignored by the compositor. This fix complies with the protocol more closely by specifically caching the enter event serial, and using it for all set_cursor calls. Fixes #1706 Closes #1899
2021-05-12 09:30:14 +02:00
- [Wayland] Bugfix: Non-arrow cursors are offset from the hotspot (#1706,#1899)
Add missing changelog entries
2021-10-28 11:48:34 +02:00
- [Wayland] Bugfix: The `O_CLOEXEC` flag was not defined on FreeBSD
Wayland: Continue poll() if timerfd can’t be read In the case the key repeat timerfd was interrupted before read(), the cursor timerfd wasn’t read at all even when it could. Related to #1711
2021-12-14 09:29:01 +01:00
- [Wayland] Bugfix: Key repeat could lead to a race condition (#1710)
Wayland: Fix duplicate focus event on activation
2021-12-22 14:16:19 +01:00
- [Wayland] Bugfix: Activating a window would emit two input focus events
Wayland: Fix key repeat continuing when refocused If a window lost input focus while a key was held down, the key repeat mechanism would resume once the window regained focus.
2021-12-22 14:19:55 +01:00
- [Wayland] Bugfix: Disable key repeat mechanism when window loses input focus
Wayland: Fix window hiding Corrects the protocol violation when creating an xdg_surface from a wl_surface that already has a buffer due to EGL buffer swaps. This commit is based on PR #1731 by @ghost, but adapted and altered: - The XDG surface and role are now only created when a window is shown to prevent application lists from showing command-line applications with off-screen-only windows - The special case of Wayland+EGL buffer swap is now in the EGL code to mirror how X11 is handled - Adaption to run-time platform selection and separate credits file Fixes #1492 Closes #1731
2020-07-13 02:47:50 +02:00
- [Wayland] Bugfix: Window hiding and showing did not work (#1492,#1731)
Wayland: Fix repeated key not released on defocus Platform code should not generate key events with GLFW_REPEAT. GLFW_PRESS is translated into GLFW_REPEAT by shared code based on the key state cache. This confused the automatic key release logic into not generating an event with GLFW_RELEASE for a key being repeated when the window lost input focus.
2021-12-26 22:51:20 +01:00
- [Wayland] Bugfix: A key being repeated was not released when window lost focus
Wayland: Fix missing damage event on window show By definition a hidden window on Wayland does not have valid framebuffer contents. This adds a window damage (refresh) event when a window is shown, to request an initial frame for the now visible window.
2021-12-28 01:39:06 +01:00
- [Wayland] Bugfix: Showing a hidden window did not emit a window refresh event
Wayland: Fix GLFW_VISIBLE affecting full screen Full screen window creation was not ignoring the GLFW_VISIBLE hint.
2021-12-28 15:33:58 +01:00
- [Wayland] Bugfix: Full screen window creation did not ignore `GLFW_VISIBLE`
Wayland: Fix keys reported as wrong or unknown key
2021-12-30 02:59:15 +01:00
- [Wayland] Bugfix: Some keys were reported as wrong key or `GLFW_KEY_UNKNOWN`
Wayland: Fix text input not following key repeat The manual key repeat implementation did not call text input.
2021-12-30 21:09:23 +01:00
- [Wayland] Bugfix: Text input did not repeat along with key repeat
Wayland: Fix glfwPostEmptyEvent not always working The display sync requests in glfwPostEmptyEvent could just accumulate as the display was never flushed on secondary threads. This adds a proper flush after each sync request. Fixes #1520 Closes #1521
2022-03-03 21:46:50 +01:00
- [Wayland] Bugfix: `glfwPostEmptyEvent` sometimes had no effect (#1520,#1521)
Wayland: Fix handling of clipboard set to self Passing any part of the result of glfwGetClipboardString to glfwSetClipboardString would result in, at best, a use-after-free error.
2022-03-22 18:46:57 +01:00
- [Wayland] Bugfix: `glfwSetClipboardString` would fail if set to result of
`glfwGetClipboardString`
Wayland: Fix double free on data source error If data source creation fails, the string containing the data for it would be freed a second time during termination.
2022-03-22 18:55:31 +01:00
- [Wayland] Bugfix: Data source creation error would cause double free at termination
Wayland: Fix partial writes of clipboard string The string pointer used to write the contents of our clipboard data offer was never updated, causing it to repeat parts of the beginning of the string until the correct number of bytes had been written.
2022-03-22 19:23:25 +01:00
- [Wayland] Bugfix: Partial writes of clipboard string would cause beginning to repeat
Wayland: Fix error paths not closing sending fd Whatever error happens on our end, we should still close the fd so the other end can move on.
2022-03-23 20:08:12 +01:00
- [Wayland] Bugfix: Some errors would cause clipboard string transfer to hang
Wayland: Improve handling of pending data offers The code assumed that all data offers were selections that supported plaintext UTF-8. The initial data offer events are now handled almost tolerably. Only selection data offers are used for clipboard string and only if they provide plaintext UTF-8. Drag and drop data offers are now rejected as soon as they enter a surface. Related to #2040
2022-03-23 19:58:33 +01:00
- [Wayland] Bugfix: Drag and drop data was misinterpreted as clipboard string
- [Wayland] Bugfix: MIME type matching was not performed for clipboard string
Wayland: Fix OSMesa library not being unloaded
2022-04-28 21:16:06 +02:00
- [Wayland] Bugfix: The OSMesa library was not unloaded on termination
Move last bits of window setup to platform code This avoids glfwCreateWindow emitting GLFW_FEATURE_UNAVAILABLE or GLFW_FEATURE_UNIMPLEMENTED on Wayland because shared code was calling unimplemented or unavailable platform functions during final setup. It also makes it consistent with the final setup of full screen windows.
2022-04-06 21:13:48 +02:00
- [Wayland] Bugfix: `glfwCreateWindow` could emit `GLFW_FEATURE_UNAVAILABLE`
Wayland: Fix missing lock key modifier bits The modifier bits for lock keys were only set when the corresponding key was reported as held down or latched, but not when it was released and locked.
2022-06-08 19:14:13 +02:00
- [Wayland] Bugfix: Lock key modifier bits were only set when lock keys were pressed
Wayland: Fix behavior of leaving full screen mode These changes make GLFW fullscreen more consistent, but unfortunately also make GLFW even more oblivious to user-initiated XDG shell fullscreen changes. Fixes #1995
2022-06-09 21:31:44 +02:00
- [Wayland] Bugfix: A window leaving full screen mode would be iconified (#1995)
- [Wayland] Bugfix: A window leaving full screen mode ignored its desired size
- [Wayland] Bugfix: `glfwSetWindowMonitor` did not update windowed mode size
- [Wayland] Bugfix: `glfwRestoreWindow` would make a full screen window windowed
Wayland: Fix maximization by user being ignored The internal maximization state was not updated when an event was received that the user had changed the maximization state of a window, and no maximization events were emitted. This affected both the GLFW_MAXIMIZED attribute and glfwRestoreWindow.
2022-06-10 13:29:24 +02:00
- [Wayland] Bugfix: A window maximized or restored by the user would enter an
inconsistent state
- [Wayland] Bugfix: Window maximization events were not emitted
Wayland: Fix missing fullscreen code path glfwRestoreWindow assumed it was only called in windowed mode.
2022-06-19 18:30:03 +02:00
- [Wayland] Bugfix: `glfwRestoreWindow` assumed it was always in windowed mode
Wayland: Fix glfwSetWindowSize resizing fs windows glfwSetWindowSize would change the size of fullscreen mode windows as if they were windowed mode.
2022-06-10 14:10:25 +02:00
- [Wayland] Bugfix: `glfwSetWindowSize` would resize a full screen window
Wayland: Fix duplicate window content scale events The window content scale event was emitted every time the window content area was resized, even if its scale had not changed.
2022-06-10 14:19:13 +02:00
- [Wayland] Bugfix: A window content scale event would be emitted every time
the window resized
Wayland: Fix glfwInit closing stdin on failure If platform initialization failed before either timer fd member had been set to -1 or a valid fd, termination would close stdin.
2022-06-10 15:45:07 +02:00
- [Wayland] Bugfix: If `glfwInit` failed it would close stdin
Wayland: Fix erratic fallback decoration behavior The handler for xdg_toplevel::configure treated the provided size as the content area size when instead it is the size of the bounding rectangle of the wl_surface and all its subsurfaces. This caused the fallback decorations to try positioning themselves outside themselves, causing feedback loops during interactive resizing. Fixes #1991 Fixes #2115 Closes #2127 Related to #1914
2022-06-16 01:36:55 +02:00
- [Wayland] Bugfix: Manual resizing with fallback decorations behaved erratically
(#1991,#2115,#2127)
Wayland: Fix size limits for fallback decorations The size limits set on our XDG surface did not include the sizes of the fallback decorations on all sides, when in use. This led to its content area being too small. Related to #2127
2022-06-12 21:36:26 +02:00
- [Wayland] Bugfix: Size limits included frame size for fallback decorations
Wayland: Fix toggling of server-side decorations This is a temporary local fix to have updates to GLFW_DECORATED mostly work as intended. The whole decoration state machine needs to be restructured, but not by this commit.
2022-06-13 19:37:34 +02:00
- [Wayland] Bugfix: Updating `GLFW_DECORATED` had no effect on server-side
decorations
Wayland: Fix duplicate monitor connection events GLFW would report a monitor as connected each time its wl_output received an update, for example if its scale changed. This would also cause the monitor to be added to the monitor array again, causing glfwTerminate to segfault when it attempted to destroy its already destroyed wl_output.
2022-06-14 18:44:24 +02:00
- [Wayland] Bugfix: A monitor would be reported as connected again if its scale
changed
- [Wayland] Bugfix: `glfwTerminate` would segfault if any monitor had changed
scale
Wayland: Fix reporting of monitor scale changes Content scale events would be emitted when a window surface entered or left an output, but not when one of a window's current outputs had its scale changed.
2022-06-14 18:46:47 +02:00
- [Wayland] Bugfix: Window content scale events were not emitted when monitor
scale changed
Wayland: Fix error from glfwSetWindowAspectRatio The aspect ratio was applied during resize but any call to glfwSetWindowAspectRatio emitted a GLFW_FEATURE_UNIMPLEMENTED error.
2022-06-14 20:37:31 +02:00
- [Wayland] Bugfix: `glfwSetWindowAspectRatio` reported an error instead of
applying the specified ratio
Wayland: Fix maximized state lost while hidden If a window was created as maximized, or created as hidden and then iconified or maximized before first being shown, that state was lost and the window was shown as restored.
2022-06-15 18:20:16 +02:00
- [Wayland] Bugfix: `GLFW_MAXIMIZED` window hint had no effect
- [Wayland] Bugfix: `glfwRestoreWindow` had no effect before first show
Wayland: Fix mapping failure on wlroots compositor When showing a window that had already been shown once (and so already had its shell objects), GLFW would attach a new buffer and commit it before waiting for the next configure event. This was a violation of the XDG shell protocol. This was allowed to work as intended on GNOME and KDE without error. However wlroots based compositors would (correctly) emit an error. Unfortunately, I haven't been able to find a way to get both KDE, GNOME and Sway to send the configure event we need in order to map the wl_surface again while keeping our existing shell objects, so with this commit we now create them for each call to glfwShowWindow and destroy them for each call to glfwHideWindow. Fixes #1268
2022-06-20 00:43:24 +02:00
- [Wayland] Bugfix: Hiding and then showing a window caused program abort on
wlroots compositors (#1268)
Wayland: Fix GLFW_DECORATED for XDG decorations On a compositor that supports server-side decorations, they were always enabled in windowed mode, even if GLFW_DECORATED was cleared.
2022-06-20 22:36:23 +02:00
- [Wayland] Bugfix: `GLFW_DECORATED` was ignored when showing a window with XDG
decorations
POSIX: Remove use of deprecated gettimeofday POSIX.1-2008 deprecated gettimeofday, which we used as a fallback if the monotonic clock was unavailable. This replaces that fallback with the non-monotonic real-time clock. Because of the Gordian knot of feature test macros across Unices, this also includes the shift from some platform source files defining _POSIX_C_SOURCE to various values to _DEFAULT_SOURCE being defined for all source files on Linux. This is because -std=c99 on Linux disables _DEFAULT_SOURCE (POSIX 2008 and extensions). Once runtime platform selection comes in, this kind of platform-specific preprocessor logic can be moved into the platform glue files and won't need to be replicated by third-party build setups, but for now, sorry.
2021-06-21 22:14:40 +02:00
- [POSIX] Removed use of deprecated function `gettimeofday`
Fix POSIX conformance issues for clock_gettime CLOCK_MONOTONIC should not be used as a feature macro. The POSIX feature macros are provided by unistd.h. CLOCK_MONOTONIC is provided by time.h. CLOCK_MONOTONIC requires _POSIX_C_SOURCE >= 199309L on some systems.
2019-12-15 17:24:26 +01:00
- [POSIX] Bugfix: `CLOCK_MONOTONIC` was not correctly tested for or enabled
WGL: Limit DWM swap interval hack to Vista and 7 This hack breaks when switching a window to fullscreen, if the OpenGL ICD detects this and switches its swapchain to exclusive mode. This limits the hack to Windows Vista and 7. This hack was added because of vsync jitter under DWM on Windows 7 and I have been unable to reproduce it on any later version. Is this change causing any problems on any version of Windows? Please open an issue! Fixes #1072
2021-10-18 01:05:09 +02:00
- [WGL] Disabled the DWM swap interval hack for Windows 8 and later (#1072)
NSGL: Remove enforcement of forward-compatible flag This sharp corner should have been addressed a long time ago.
2019-05-19 20:51:50 +02:00
- [NSGL] Removed enforcement of forward-compatible flag for core contexts
NSGL: Fix disabling of Retina resolution It appears the default is now YES. Fixes #1442.
2019-12-09 18:53:29 +01:00
- [NSGL] Bugfix: `GLFW_COCOA_RETINA_FRAMEBUFFER` had no effect on newer
macOS versions (#1442)
NSGL: Remove problematic swap interval workaround Fixes #1483.
2019-11-07 15:13:49 +01:00
- [NSGL] Bugfix: Workaround for swap interval on 10.14 broke on 10.12 (#1483)
Update changelog Related to #1840.
2021-07-29 21:27:02 +02:00
- [NSGL] Bugfix: Defining `GL_SILENCE_DEPRECATION` externally caused
a duplicate definition warning (#1840)
EGL: Add support for EGL_EXT_platform_base This adds support for EGL_EXT_platform_base and its associated X11 and Wayland extensions, allowing us to explicitly tell EGL which window system we are using. This is based on work by @linkmauve in #1691. Closes #1691.
2020-06-03 22:02:25 +02:00
- [EGL] Added platform selection via the `EGL_EXT_platform_base` extension
Update changelog
2020-08-04 17:21:17 +02:00
(#442)
EGL: Add support for EGL_ANGLE_platform_angle This adds basic support for selecting the platform type (rendering backend) when running on ANGLE. Related to #1380.
2020-06-25 18:22:08 +02:00
- [EGL] Added ANGLE backend selection via `EGL_ANGLE_platform_angle` extension
(#1380)
Add missing changelog entry Related to #1843.
2021-06-15 18:14:56 +02:00
- [EGL] Bugfix: The `GLFW_DOUBLEBUFFER` context attribute was ignored (#1843)
GLX: Fix context creation failing unnecessarily Regression introduced with 3bb5c459d63d7cf9c990213e39303d9ba5eaebcc.
2022-01-06 07:07:53 +01:00
- [GLX] Bugfix: Context creation failed if GLX 1.4 was not exported by GLX library
Fix glfwMaximizeWindow not checking window mode
2016-06-16 12:52:22 +02:00
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
## Contact
Fix some documentation URLs still using http: Some URLs in the documentation were overlooked during the switch to https: for the GLFW website. This updates those and a few third-party URLs.
2021-06-09 22:43:27 +02:00
On [glfw.org](https://www.glfw.org/) you can find the latest version of GLFW, as
Documentation work
2016-08-02 15:58:58 +02:00
well as news, documentation and other information about the project.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
If you have questions related to the use of GLFW, we have a
Use HTTPS for Discourse forum
2019-10-13 16:42:54 +02:00
[forum](https://discourse.glfw.org/), and the `#glfw` IRC channel on
Update IRC network to Libera.Chat The `#glfw` IRC channel is moving to the Libera.Chat network due to the recent takeover of the Freenode network.
2021-06-09 22:36:13 +02:00
[Libera.Chat](https://libera.chat/).
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
If you have a bug to report, a patch to submit or a feature you'd like to
Updated contact information.
2013-06-24 14:28:42 +02:00
request, please file it in the
[issue tracker](https://github.com/glfw/glfw/issues) on GitHub.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Finally, if you're interested in helping out with the development of GLFW or
Documentation work
2016-08-17 16:48:22 +02:00
porting it to your favorite platform, join us on the forum, GitHub or IRC.
Replaced readme.html with README.md. Removed historic changelog, updated build and use documentation, reformatted contributor list, removed structure table, etc.
2013-02-04 10:46:02 +01:00
Reference in New Issue Copy Permalink