[Prev][Next][Index][Thread]

Re: executor messes up fvwm!



In article <m0uDb9b-000GOKC@gwar.ardi.com> mat@ardi.com (Mat Hostetter) writes:
>   I think the problem is that Executor ties up his colormap, so
>   subsequently run programs can't get the colors they desire.  Since you
>   are running in 16bpp mode, you have no colormap and everything works.
>
>   "-privatecmap" is one workaround for his problem, although not a
>   perfect one.
>
>   -Mat
Mat,
	Your response got me to thinking about the problem of running
	Executor with an 8 bit colormap. The current options leave you
	with two extreme solutions. You can either run in the root
	colormap resulting in Executor eating up many of the available
	256 colors that are then not available for other programs or you
	can use the privatecmap option which then results in
	funky/annoying color changes as you change windows. Perhaps there
	could be a more flexible intermediate option that allows you to
	specify & limit the number of colors that Executor will use for
	itself (I know that this can't happen until post Executor
	2). In a sense such behavior is already possible. Specifically,
	if you run Executor after allocating many of the available
	colors, then Executor manages to run with the remaining available
	colors albeit with a somewhat changed on screen appearance. The
	feature that I am suggesting would simply allow you to specify
	the number of colors that Executor can use and then Executor
	would try to make the best use of them (eg. pick the closest
	available color). Is this a reasonable suggestion?

Jeff Kosowsky 




Follow-Ups: References: