[GRASSLIST:1236] Word of thanks and a question

Hi all,

Thanks to the GRASS develpment team for bring out
the Grass5-b10 with several enhancements and bugfixes.

The binary is working without problem on my machine
running Mandrake Linux7.2. Coming to the question now,
is there a way to avoid the GRASS graphics monitor getting
erased by the tcl/tk panels or terminal windows. The may
not be a problem due to GRASS (perhaps to do with my KDE
window manager setting), but everytime other windows
or tcl/tk panels appear in the foreground over the GRASS
monitor the area of overlap on the GRASS monitor gets erased.
I need to bring the GRASS monitor to the foreground and use
the d.mon select=Xx which refreshes the monitor.

GRASS5beta8 working on other machines (Redhat6.0 and Slackware7.0)
dont seem to have this problem.

Thank you.

Venkatesh Raghavan
Osaka City University

On Fri, Dec 08, 2000 at 05:59:43PM +0900, Venkatesh Raghavan wrote:

Hi all,

Thanks to the GRASS develpment team for bring out
the Grass5-b10 with several enhancements and bugfixes.

The binary is working without problem on my machine
running Mandrake Linux7.2. Coming to the question now,
is there a way to avoid the GRASS graphics monitor getting
erased by the tcl/tk panels or terminal windows. The may
not be a problem due to GRASS (perhaps to do with my KDE
window manager setting), but everytime other windows
or tcl/tk panels appear in the foreground over the GRASS
monitor the area of overlap on the GRASS monitor gets erased.
I need to bring the GRASS monitor to the foreground and use
the d.mon select=Xx which refreshes the monitor.

GRASS5beta8 working on other machines (Redhat6.0 and Slackware7.0)
dont seem to have this problem.

Difference is X 3.3.6 => X 4.0.1, I think. Try putting this in
/etc/X11/XF86Config (or wherever it's stored on Mandrake).

Section "Device"
  ...
  ...
        Option "backingstore" "on"
EndSection

--
Eric G. Miller <egm2@jps.net>

Dear Venkatesh,

On Fri, Dec 08, 2000 at 05:59:43PM +0900, Venkatesh Raghavan wrote:

Hi all,

Thanks to the GRASS develpment team for bring out
the Grass5-b10 with several enhancements and bugfixes.

The binary is working without problem on my machine
running Mandrake Linux7.2. Coming to the question now,
is there a way to avoid the GRASS graphics monitor getting
erased by the tcl/tk panels or terminal windows. The may
not be a problem due to GRASS (perhaps to do with my KDE
window manager setting), but everytime other windows
or tcl/tk panels appear in the foreground over the GRASS
monitor the area of overlap on the GRASS monitor gets erased.
I need to bring the GRASS monitor to the foreground and use
the d.mon select=Xx which refreshes the monitor.

GRASS5beta8 working on other machines (Redhat6.0 and Slackware7.0)
dont seem to have this problem.

are you sure that you didn't change the KDE from GRASS5beta8 times
to now? Actually I face the same problem in KDE only, using fvwm2
it is o.k.
Please see the FAQ for possible help:
http://www.geog.uni-hannover.de/grass/faq/index.html#problems
-> GRASS Monitor does not repaint when is was hidden by another window

My problem is reduced by that, but not fully fixed for KDE. Seems
to be a KDE related problem (I have KDE 1.x, not tested 2.x yet).

Yours

Markus

On Fri, Dec 08, 2000 at 06:50:07AM -0800, Eric G . Miller wrote:

On Fri, Dec 08, 2000 at 05:59:43PM +0900, Venkatesh Raghavan wrote:
> Hi all,
>
> Thanks to the GRASS develpment team for bring out
> the Grass5-b10 with several enhancements and bugfixes.
>
> The binary is working without problem on my machine
> running Mandrake Linux7.2. Coming to the question now,
> is there a way to avoid the GRASS graphics monitor getting
> erased by the tcl/tk panels or terminal windows. The may
> not be a problem due to GRASS (perhaps to do with my KDE
> window manager setting), but everytime other windows
> or tcl/tk panels appear in the foreground over the GRASS
> monitor the area of overlap on the GRASS monitor gets erased.
> I need to bring the GRASS monitor to the foreground and use
> the d.mon select=Xx which refreshes the monitor.
>
> GRASS5beta8 working on other machines (Redhat6.0 and Slackware7.0)
> dont seem to have this problem.

Difference is X 3.3.6 => X 4.0.1, I think. Try putting this in
/etc/X11/XF86Config (or wherever it's stored on Mandrake).

Section "Device"
  ...
  ...
        Option "backingstore" "on"
EndSection

Hi Eric,

this unfortunately doesn't fully fix the problem for KDE (however it
does for fvwm2).

KDE-Example: If you draw a raster map, cover the monitor partly with a
window, run d.erase and move away the covering window, you will find parts
of the old map in the covered window corner. I guess it is an X 4.0.1
problem (as X 3.3.6 was o.k.).

Above backingstore trick is posted on the FAQ.

I have no idea to fully fix it...

Markus

On Fri, Dec 08, 2000 at 03:43:12PM +0000, Markus Neteler wrote:

Hi Eric,

this unfortunately doesn't fully fix the problem for KDE (however it
does for fvwm2).

KDE-Example: If you draw a raster map, cover the monitor partly with a
window, run d.erase and move away the covering window, you will find parts
of the old map in the covered window corner. I guess it is an X 4.0.1
problem (as X 3.3.6 was o.k.).

Above backingstore trick is posted on the FAQ.

I have no idea to fully fix it...

Oh. Haven't used KDE for a while so I didn't know this. Maybe KDE is
overriding this option somehow, since the monitor isn't a KDE app, KDE
must be setting something in X that changes this option. Try opening a
monitor and running xwininfo on it. Here, among the output, I get:

  Backing Store State: Always

--
Eric G. Miller <egm2@jps.net>

On Fri, Dec 08, 2000 at 03:29:46PM +0000, Markus Neteler wrote:

are you sure that you didn't change the KDE from GRASS5beta8 times
to now? Actually I face the same problem in KDE only, using fvwm2
it is o.k.
Please see the FAQ for possible help:
http://www.geog.uni-hannover.de/grass/faq/index.html#problems
-> GRASS Monitor does not repaint when is was hidden by another window

My problem is reduced by that, but not fully fixed for KDE. Seems
to be a KDE related problem (I have KDE 1.x, not tested 2.x yet).

Okay, I downloaded/installed KDE 2.0 from Debian's Woody (got to love
that!) and I don't see this problem. So it must be fixed in newer
versions of KDE (or Debian does something different -- but I don't think
so in regards to KDE).

--
Eric G. Miller <egm2@jps.net>

Hi,

The fix suggested by Eric and Markus worked.
Had to add the option to my /etc/X11/XF86Config-4
file.

Markus Neteler wrote:

KDE-Example: If you draw a raster map, cover the monitor partly with a
    window, run d.erase and move away the covering window, you will find

parts

    of the old map in the covered window corner. I guess it is an X 4.0.1
    problem (as X 3.3.6 was o.k.).

Did not have that problem even with X 4.0.1.
Runing d.erase erased the entire monitor.

Thanks for the tip.

Raghavan
Osaka City University

"Eric G . Miller" wrote:

On Fri, Dec 08, 2000 at 03:29:46PM +0000, Markus Neteler wrote:
> are you sure that you didn't change the KDE from GRASS5beta8 times
> to now? Actually I face the same problem in KDE only, using fvwm2
> it is o.k.
> Please see the FAQ for possible help:
> http://www.geog.uni-hannover.de/grass/faq/index.html#problems
> -> GRASS Monitor does not repaint when is was hidden by another window
>
> My problem is reduced by that, but not fully fixed for KDE. Seems
> to be a KDE related problem (I have KDE 1.x, not tested 2.x yet).

Okay, I downloaded/installed KDE 2.0 from Debian's Woody (got to love
that!) and I don't see this problem. So it must be fixed in newer
versions of KDE (or Debian does something different -- but I don't think
so in regards to KDE).

--
Eric G. Miller <egm2@jps.net>

Grass Users

I just downloaded the GRASS5 beta10 source code and everything went well compiling on a Solaris 7 - however I could not find the create fifos in the appropriate folders. The configure script pointed out that it could not create or find the create fifos file. Once compiled, there was an empty create_fifos.sh file in the grass5/dev folder.

I manually created the fifos and GRASS worked great.

Good Job GRASS 5 TEAM.

Anthony Burns

Anthony G Burns
USDA-NRCS
GIS Specialist
Gainesville, Georgia

anthony.burns@ga.usda.gov
770-536-6981

Hi Anthony,

On Mon, Dec 11, 2000 at 08:10:14AM -0500, Anthony G Burns wrote:

Grass Users

I just downloaded the GRASS5 beta10 source code and everything went well
compiling on a Solaris 7 - however I could not find the create fifos in the
appropriate folders. The configure script pointed out that it could not
create or find the create fifos file.

Please send the full error message to me (personally).

Once compiled, there was an empty
create_fifos.sh file in the grass5/dev folder.

I manually created the fifos and GRASS worked great.

... take a look into
$GISBASE/scripts/

It should be there.

Good Job GRASS 5 TEAM.

:slight_smile:

Markus Neteler