On 18 Apr 2002 11:33:29 +0100, Tim Phipps wrote: > > fvwm-workers@fvwm.org wrote: > > >Wasn't it planned to make the new code complatible with the old > >FvwmTheme way? Now, all my colour sets are gone. > > Yes, I don't know what's gone wrong. The differences between FvwmTheme.c > and colorset.c are fairly minor and I didn't have a problem with a > TrueColor display. I've switched to a PseudoColor and things are going > wrong. Things that have changed are: > > * The error handler, it used to core dump on just a few and was > silent on the rest, now it prints a message > * The cleanup routine that is used after a colorset pixmap is > changed, it used to wait for a period of inactivity before > deleting it, now it just waits 3 seconds for the change. > > Neither of these should have broken things badly, is it possible to get > an equivalnce check between the current colorset.c and the one I sent > in? I don't think the reformatting could have broken anything.
I just replaced the colorset.c in cvs with the one you sent (changing s/FVWMTHEME_PRIVATE/FVWM_COLORSET_PRIVATE/) and I get exectly the same results as mentioned in my other message with my depth 24, 16 and even 8. Everything works for me except for gradients. Well, this means most of fvwm-themes colors@ work except for [EMAIL PROTECTED] that uses VGradient. I may suggest to temporarily comment out all *FvwmTheme ... VGradient. Or you say anything else except for gradients are broken too? Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
