trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: September 2016

Re: [trinity-users] [SOLVED] Undefined color: "WINDOW_FOREGROUND" and the old dot.trinity

From: Slávek Banko <slavek.banko@...>
Date: Tue, 20 Sep 2016 16:37:39 +0200
Anyway, the problem is already fixed for the upcoming TDE R14.0.4:

  https://bugs.trinitydesktop.org/show_bug.cgi?id=1375

Cheers
-- 
Slávek

On Tuesday 20 of September 2016 16:23:52 A M wrote:
> The issue was solved, thanks to the most useful comments by three list
> participants. The first advice, by Gerhard Zintel, was a suggestion to
> simply uncheck one of the preferences via the TDE Control Center:
>
>
>
> *" I had the same issue before. I cannot clearly remember but try to
> un-check "Apply colors to non-TDE applications" in TDE Control Center
> => Appearence & Themes => Colors. "*
>
> That immediately worked, thanks Gerhard!  But then the next advice came
> from Nick Koretsky which also commented on the Gerhard's advice:
>
>
>
>
>
>
>
>
>
> *That's a bad solution - this checkbox is unfortunately named, it
> should be named "apply styles' - it govern not only colors, but also
> button styles, button placements and fonts in gtk apps The correct
> solution is to add following to you .xsession file ( sleep 10 xrdb -all
> -query|sed -e 's#[A-Z_]*BACKGROUND# gray90#' \*
>
>
>
> *-e 's#[A-Z_]*FOREGROUND# Black#'  \ -e 's#[A-Z_]*HIGHLIGHT# White#' \
> -e 's#[A-Z_]*LOWLIGHT# Black#'|xrdb -merge ) &*
>
> I tried this as well, and it works and seems in fact to be more
> appropriate for our environment. I've applied it by adding to the
> system-wide script that is executed at login and does it one time per
> session. It works pretty well (and has no impact on gtk applications).
> So we'll stick to this method.
>
> Finally, another advice came from "iadest":
>
>
>
>
>
>
>
>
>
>
>
> *Hello Try to edit ~/.Xresourced adding: *.WINDOW_FOREGROUND: black
> Then execute command: xrdb -merge ~/.Xresources I had similar problems
> with Perl/Tk and *.BACKGROUND color. Maybe this solution will work for
> Emacs too.*
> *MCbx*
>
> As this solution was basically quite similar to that of Nick's which
> was already nicely implemented, I did not try this..
>
> In any case, these advices saved me a day. Thanks a lot for all those
> who replied!
>
> Andy.



-- 
Slávek