xpra icon
Bug tracker and wiki

Changes between Version 1 and Version 2 of Ticket #705, comment 8


Ignore:
Timestamp:
11/01/14 18:14:03 (5 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #705, comment 8

    v1 v2  
    11Found this in the Java patch {{{nomotif-6706121.patch}}} - worth a read:
    22''
    3 Unfortunately the concept of "insets" borrowed to AWT from Win32 is *absolutely*, *unbelievably* foreign to X11.  Few WMs provide the size of frame decor (i.e. insets) in a property they set on the client window, so we check if we can get away with just peeking at it.  [Future versions of wm-spec might add a standardized hint for this].
     3Unfortunately the concept of "insets" borrowed to AWT from Win32 is *absolutely*, *unbelievably* foreign to X11.  Few WMs provide the size of frame decor (i.e. insets) in a property they set on the client window, so we check if we can get away with just peeking at it.  [Future versions of wm-spec might add a standardized hint for this].''
    44
    5 Otherwise we do some special casing.  Actually the fallback code ("default" case) seems to cover most of the existing WMs (modulo Reparent/Configure order perhaps?).
     5''Otherwise we do some special casing.  Actually the fallback code ("default" case) seems to cover most of the existing WMs (modulo Reparent/Configure order perhaps?).''
    66
    7 Fallback code tries to account for the two most common cases:
     7''Fallback code tries to account for the two most common cases:''
    88
    9 . single reparenting
     9* ''single reparenting
    1010 parent window is the WM frame
    11  [twm, olwm, sawfish]
     11 [twm, olwm, sawfish]''
    1212
    13 . double reparenting
     13* ''double reparenting
    1414 parent is a lining exactly the size of the client
    1515 grandpa is the WM frame
    16  [mwm, e!, kwin, fvwm2 ... ]
    17 ''
     16 [mwm, e!, kwin, fvwm2 ... ]''
    1817
    1918This code is absolutely horrible, no wonder they refactored it in JDK 7!