search for: icccm

...or upcoming final release Release Notes: Add 7.6 dedication XKB-Enhancing: Fix URL for XKB spec ReleaseNotes: fix typos Update Xserver security docs from DocBook 4.1.2 to 4.3 to match the rest ctext.xml: Replace incorrect fi ligature character with "fi" ICCCM: Fix Preface titles & section nesting ICCCM: Update X Registry contact address ICCCM: Pair copyright notices with matching license notices Sun's copyrights belong to Oracle now XLFD: Fix chapter titles/section nesting XLFD: Fix cross-references to other section...

...=== Henning Sten (2): introduce function xcb_atom_get (essentially a synchronous xcb_intern_atom, use it only on non-performance critical execution paths) add more verbose explanation of the purpose of "encoding" parameter in doxygen documentation tag Julien Danjou (5): icccm: add some comment on text reply usage icccm: fix normal hints flags computing wm: link test against atom lib configure: stop if m4 is not found Release xcb-util 0.3.1 Peter Harris (1): more endianness patches Ulrich Eckhardt (2): "Clean up" magic stru...

xcb-util 0.3.2 is available git tag 0.3.2 Changelog ========= Jonathan Landis (1): Fix copyright statement Julien Danjou (4): build: add check for xproto >= 7.0.8 keysyms: use xcb_key_lookup_t type for col paramter icccm: fix gravity proto Release xcb-util 0.3.2 Peter Harris (2): Don't call exit() in xcb_aux_get_depth; return 0 instead. Fix the type of 'input' in icccm/xcb_icccm.h/xcb_wm_hints_t Download ======== http://xcb.freedesktop.org/dist/xcb-util-0.3.2.tar.gz md5: 1206a87aa971...

Hi, I just noticed that Compiz' window base size calculation in the function recalcNormalHints() is broken. If both PMinSize and PBaseSize are set, the base size is overwritten by the minimum size first and after that the minimum size is overwritten by the base size again. This leads to the base size information being completely lost. I have attached a patch which fixes this problem, however,

On 2007-12-30, Timothy B. Terriberry wrote: > In any format that is to be used on both, it is always better to pick > one and stick with it. Then recommend one single format. Nobody *has* to support all of the features present, yet it makes sense to *allow* common variances. Most of all, because: > Unless you can guarantee that you're writing streams that are only > going to

...config: statement order for XORG_CHECK_DOCBOOK config: use XORG_CHECK_DOCBOOK macro as is. config: use the XORG_ENABLE_DOCS macro to control docs building config: install the documents in $(docdir) config: build CTEXT spec now in DocBook XML format config: build ICCCM spec now in DocBook XML format config: build XLFD spec now in DocBook XML format registry: update link to find latest version Install.sgml: remove until suitable replacement is available config: delete various accessory build files for old docs Remove Linuxdoc Japanese...

...generalize the privates mechanism and the plugin system. It allows to share more code between display, screen and window objects. It also makes it possible to properly introduce new object types without changing the plugin interface or breaking the API. Multi-display support. Various fixes in ICCCM compliance, window stacking and focus handling. Validity checking of ConfigureRequest events. Fixes to transient children placement in place plugin. Hooks have been added to the cube plugin which allow better control of viewport drawing. Middle and right click actions have been made configurabl...

...uot;) <code> tags use DOCTYPE consistently in included xml files, to allow using named entities modify xml-files to use named-entities, for easier manipulation corrected some nested list formatting fix ``fake quotes'' fill in titles for some references to ICCCM and X11 documents use programlisting tag rather than workaround for literallayout font. use consistent labeling for xref's use lineannotation tag to solve font mismatches for xref's inside formatted sample code to fit in 80 columns whitespace/formatting fixes...

...ost-release version increment. We always need to restack windows on map. Newly created windows are placed on top of the stack first, which is not desired for some windows that may be denied focus (such as desktop windows). Send synthetic configure notify events where needed according to ICCCM chapter 4.1.5. glGetString is allowed to return NULL in case an error happened, so avoid crashing in this case and bail out instead. An aboveId of None means that the window was placed on bottom of the stack, so also update the linked list accordingly. Don't restack desktop wi...