Re: What could be missing?

On 2/22/11, Andrew Hood <[email protected]> wrote:
> Jeremy wrote:
>> On 2/20/11, Jeremy <[email protected]> wrote:
>>
>>>You got me thinking in a new direction and I want to attempt a couple
>>>of things first.
>>
>>
>> SOLVED!!!
>>
>> It took me a while to get to it, but it was as simple as entering the
>> following command:
>>
>> export XLIB_SKIP_ARGB_VISUALS=1
>>
>> before starting NEdit. I have made it part of a script I now use each
>> time to start NEdit on the laptop.
>> It seems that Motif has a problem with the ARGB visuals called upon
>> by X.Org when interacting with the specific hardware on my laptop
>> (or something similar to that extent).
>>
>> 'XLIB_SKIP_ARGB_VISUALS=1' directs the X library to prevent the
>> interaction of these ARGB visuals with Motif, which solves the
>> problem perfectly. Now, NEdit performs on my old laptop as
>> perfectly as it does on my other larger, newer machine. :)
>
> If you rebuilt NEdit from CVS, it does that by itself. Quote from
> nedit.c (sorry about the linewrap):
>
>     /* X.Org 6.8 and above add support for ARGB visuals (with
> alpha-channel),
>        typically with a 32-bit color depth. By default, NEdit uses the
> visual
>        with the largest color depth. However, both OpenMotif and Lesstif
>        cannot handle ARGB visuals (crashes, weird display effects, ...), so
>        NEdit should avoid selecting such a visual.
>        Unfortunatly, there appears to be no reliable way to identify
>        ARGB visuals that doesn't require some of the recent X.Org
>        extensions. Luckily, the X.Org developers have provided a mechanism
>        that can hide these problematic visuals from the application.
> This can
>        be achieved by setting the XLIB_SKIP_ARGB_VISUALS environment
> variable.
>        Users can set this variable before starting NEdit, but it is much
>        more convenient that NEdit takes care of this. This must be done
> before
>        the display is opened (empirically verified). */
>     putenv("XLIB_SKIP_ARGB_VISUALS=1");

Hi Andrew. Unfortunately, I never looked at the nedit.c file as I did
not build NEdit but downloaded the version currently available at this
website.
My only question is, given you likely have had this information all
along and that I had described from the very start the weird display
effects on my laptop, assuming you have been following this thread,
why did you not volunteer this information earlier and thus help me
avoid a major waste of time and the grief thereof?
I'm grateful for the help received here and it has been a great
learning experience, no doubt, but am just wondering...
-- 
NEdit Discuss mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/discuss