[GRASS5] XDRIVER changes between 5.0.0pre2 and now?

[Glynn Clements]

Carl Worth wrote:

> However, now that I've updated to that code, I am having several
> display problems, (using XDRIVER). My monitor windows are not
> redrawing themselves properly, (I have to drag other windows over them
> to cause expose events and repaints before I ever see anything).

Note: XDRIVER doesn't process Expose events. It creates a background
pixmap the same size as the window, and all graphics are drawn to that
pixmap. Redraw should handled by the X server without any help from
the application.

> The
> monitor windows are also not responding to the client message delete
> events properly, (ie. they don't close when I use my window manager's
> close button). I've also seen some problems with restarting a monitor
> that I have stopped, (I don't have the exact error, but it was something
> like "Socket not available").
> 
> Has anyone else seen problems like these? They seem bad enough that I
> can't imagine this is a common problem.

It certainly isn't a common problem.

Could you provide details of your platform?

> But I also don't know what I could have done wrong. I didn't have any
> of these problems when using the code at the head of CVS, nor when
> using the grass5.0.0pre2 tar file. And I'm not sure that I compiled
> the code any differently. What changes have happened to the XDRIVER
> code between 5.0.0pre2 and now?

I'll have to get back to you after checking "cvs log".

Did you use "make clean" (preferably "make maintainer-clean") between
compiles? Dependency information is almost non-existent, so
incremental builds are problematic.

-- 
Glynn Clements <glynn.clements at virgin.net>