On Thu, 3 Oct 2002 11:03:27 +0200 "Olivier Chapuis" wrote:
>
> On Wed, Oct 02, 2002 at 05:41:44PM -0700, Tim Freedom wrote:
> > A couple of things (I must be cursed or something :-) I get the same
> > "odd" results using either method noted above (ie. visual or visualId).
> >
>
> Well, running fvwm 2.5.x in a different visual than the default visual is
> totally broken at present time (but with depth <= 8 and a dynamic
> visual class (PseudoColor, GreyScale and DirectColor)). I hope that
> this will be fixed in a few days.
In a really absurd way, I'm happy to hear that :-) At least its nothing
very particular with my setup and is something that is visible elsewhere.
I'll keep posted for a fix to give it a try.
> >
> > [FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error ***
> > [FVWM][FvwmErrorHandler]: <<ERROR>> Request 72, Error 8, EventType: 0
> > [FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error ***
> > [FVWM][FvwmErrorHandler]: <<ERROR>> Request 72, Error 8, EventType: 0
> > [FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error ***
> > [FVWM][FvwmErrorHandler]: <<ERROR>> Request 72, Error 8, EventType: 0
> >
>
> This says that XPutImage fail (parameter mismatch, a gc problem I guess
> when loading an xpm) and it is the reason of your icon pbs in FvwmButtons.
>
> > And all my FvwmButtons are rather scrambled and ... well take a look for
> > yourself - a small image is attached. Otherwise all else seems ok.
>
> Hum, Do you use some xpm image in others place (menus, Icon and MiniIcon
> style?). I guess that no xpm image will be displayed fine.
I think there are like 3-4 menu icons that I played with at some point
and simply left-in to show people (you know to wow 'em :-) Is that a
problem ? Should I remove 'em ? If you'd like me to run some debug code
for ya, don't hesitate to let me know.
> > What am I doing wrong ?
> >
>
> In theory you do nothing wrong, you just fall on a bug. The 2.5.x
> series is **alpha-alpha** at present time. In practice, I am not sure
> it is a good idea to run fvwm with a visual != than the default
> visual.
Are you saying that running with a visual != default visual is a bad
idea now or in general ? I can see why the "now" would makes sense, but
if it were an "in general" statement, then I don't really know what
to say.
> In an other mail you wrote:
>
> > multiple options are available." So I'm not sure how fvwm determines what
> > the X-server is capable of, but its figuring them to be 8-bit on this
> > machine when they really need to be 24-bit (is it grabbing xdpyinfo's
> > output ?). Anything I can do to make fvwm resolve to 24-bit short of
> > restarting the server with that depth setting explicitly (meaning I'd
> > have to call the powers that be to change the configuration on this
> > machine - after a million+1 questions) ? What do other window managers
> > (like CDE) do to resolve this ?
>
> If you start fvwm without -visual{Id} it asks the server for the
> default visual and use it (I do not think that fvwm is broken here; it
> does not grep xdpyinfo, it uses the X library). But, why you do
> not always start your Xserver with 24-bit set explicitly? I've no
> experience with 8+24 depth video cards, but it seems to me that the
> depth 8 is useful for applications which work only with a depth 8
> dynamic visual (PseudoColor) because, for example, the application
> needs read-write colors. So, if you do not use such apps or if you use
> such apps which can found this depth 8 visual alone or via an option I
> think you should start your Xserver with 24-bit.
I use a great deal of third-party applications and I'm not sure which
require 8-bit and which don't. If I were to restart the Xserver in
24-bit, I'd require the help of the sys-admins here (which usually turn
into a brief interrogation) and if things don't work I will be on very
shaky ground to ask 'em to revert me back (you know that "evil eye" thing),
etc (the option of me controlling that setting/file is not much of an
option - don't ask).
> Others reasons to not use 24-bit by default:
> - This may use more memory (???)
> - Your Xserver driver is not accelerated with this mode.
Simply put, don't want to deal with the appropriate authorities :-)
due to hassle since its nothing that I personally control. Its not
technical at all.
> In abstract if you do not have good reasons to do not use 24-bit
> by default, use it!
>
> So now if you have a good reason for using 8-bit by default either
> - Do not use the -visual{Id} option (fvwm with 256 colors,
> maybe when fvwm will become beta the -color-limit 61 option
> will be not needed).
> - Use the -visual{Id} option (wait a few days for 2.5.x or use
> fvwm-2.4.11).
I've grabbed 2.4.11 and will keep an eye out for a commit that addresses
visuals to grab a snapshot (2.4.11 worked great btw). Do let me know if
I can help.
.tf. (please CC replies)
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Oct 03 2002 - 11:59:37 BST