Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#124 X Error

development
open
nobody
Program (79)
5
2004-09-28
2004-09-28
Peter Kovář
No

This little patch adds X error handler instead of
default error handler in Xlib, which calls exit() at
the end. This helped to track the bug with new 32-bit
visual introduced in the X11R6.8 with (slow) Composite
extension.

RFE & RFC: X error could trigger save of all modified
buffers in order to avoid data loss.

Discussion

  • Peter Kovář
    Peter Kovář
    2004-09-28

    X Error patch

     
  • Nathan Gray
    Nathan Gray
    2006-04-11

    Logged In: YES
    user_id=121553

    I had thought to do the same thing, but I think it would be
    better to save "incremental save" files like ~foo instead of
    triggering a real save.

     
  • Peter Kovář
    Peter Kovář
    2008-10-25

    X Error patch for 5.6

     
  • Peter Kovář
    Peter Kovář
    2008-10-25

    More detailed X Error patch for 5.6

     
  • Peter Kovář
    Peter Kovář
    2008-10-25

    This modification helped me to better understand what's going on with αRGB visuals such as 32-bit TrueColor (ID 0x23). Errors were repeorted when def->pixel was FFXXXXXX IOW α channel was used.

    So little modification of libX11-1.1.4

    XQueryColor()
    val &= 0x00FFFFFF;

    allows to run with such visual.

    However these settings in ~/NEdit triggers another set of vector font rendering issues
    nedit*renderTable: xft
    nedit*xft*fontType: FONT_IS_XFT
    nedit*xft*fontName: Sans