Changelog for xorgproto-doc-2024.1-1.1.noarch.rpm :

* Tue Mar 26 2024 Stefan Dirsch - Update to version 2024.1
* updates for the DRI3 and Present protocol definitions to support explicit synchronization and other keysyms/keydefs fixes and improvements.
* Fri Jun 16 2023 Stefan Dirsch - Update to version 2023.2
* quick-fix release to address the Present protocol version not being updated in xorgproto-2023.1.
* Sat Jun 10 2023 Stefan Dirsch - Update to version 2023.1 This release introduces a couple of new options for existing extensions:
* A new option PresentOptionAsyncMayTear for the Present extension,
* A new flag XFixesClientDisconnectFlagForceTerminate to the XFixes XFixesClientDisconnectFlags intended to be used by screen lockers, where the server must exit if the screen locker does. The other changes include various fixes, clarifications and keysym definitions updates:
* Tue Jan 31 2023 Stefan Dirsch - switched to multibuild for -doc package to avoid build cycles
* Sun Jan 29 2023 Christopher Yeleighton - Build documentation (boo#1207721)
* Sun Aug 21 2022 Bjørn Lie - Use xz tarball instead of gz, save a few bytes in size.
* Fri Aug 12 2022 Dirk Müller - add gpg validation of sources
* Thu Aug 11 2022 Aaron Stern - xorgproto 2022.2
* DRI3: Add DRI3SetDRMDeviceInUse
* Add the XWAYLAND extension
* Build xz tarballs instead of bzip2
* Thu Apr 21 2022 Stefan Dirsch - xorgproto 2022.1
* No changes to the actual protocols, just the additions of some new keysyms provided by the Linux kernel.
* Wed Sep 15 2021 Stefan Dirsch - xorgproto 2021.5
* This release introduces the version 2.4 of the X Input protocol. It contains the addition of the concept of touchpad gestures. Touchpad gesture is an interaction of two or more fingers that can be interpreted as a swipe or a pinch.
* Mon May 31 2021 Dirk Müller - package licenses as %%license- modernize spec file- list files in files-section to avoid directory permission conflict with filesystem package
* Fri Apr 30 2021 Stefan Dirsch - xorgproto 2021.4 The big new feature in this release is Olivier\'s addition that makes up XFixes 6: the new ClientDisconnectMode. An X server that is started on demand (Xwayland) should ideally also terminate when the last client disconnects. However, some X11 clients that provide system services will linger around forever, preventing that shutdown. With the new XFixes request, a client can designate itself as to-be-terminated and the X server can ignore those clients when counting the number of remaining clients. If no other clients are left, the server can shut down. Note that this requires changes to the X server and each client to work.
* Thu Feb 25 2021 Stefan Dirsch - xorgproto 2021.3 If you thought the 2021.2 release was exciting, well, you\'re in for a surprise: this one even builds with meson! How cool is that?! Somewhat related: the new script to generate and verify the keysyms was missing from the (autotools-generated) tarball, causing a meson build from that tarball to fail during the setup phase. This is fixed now. No changes to the rest of the sources, so this is effectively identical to yesterday\'s tarball.
* Thu Feb 25 2021 Stefan Dirsch - xorgproto 2021.2 This release is mostly all about keysyms. Some additions to Vietnamese and Hangul but the big set of commits here is catching up with several years of Linux kernel releases. The kernel\'s evdev interface has semantic keycodes (e.g. KEY_ESC is what you\'d expect). Beyond the normal range expected to change with different layouts there are many keycodes that should only ever do one thing. For example, KEY_ONSCREEN_KEYBOARD should display the OSK regardless of layout). In the past, we\'ve added these keysyms on a as-requested basis. We now have a reserved subrange in the already reserved range for XF86Foo keysyms. Within that range, keysyms map directly to their evdev counterparts, making future updates easier. The above example KEY_ONSCREEN_KEYBOARD now has a XF86OnScreenKeyboard keysym. The header file follows a strict convention to make this range machine-readable, xkeyboard-config can make use of this to make those keysyms available by default. Note that almost all keys are outside the X keycode range so very little will change under X. Note that most keys exist on selected devices only so the practial use is quite limited. But those keysyms are available through normal XKB configuration so users can re-map existing keys where needed. Aside from those, a bit of misc cleanup work. Many thanks to all contributors.