[GRASS-dev] xganim: fix compilation or remove completely?

Helena Mitasova hmitaso at ncsu.edu
Wed Dec 11 19:55:07 PST 2013


I think that if there are no objections xganim can be removed from grass7, the new animation tool is much, much better.

It may be worth keeping it in grass6.4*. To test xganim just use any output from r.sim.water or r.sun.daily or nags head series.
If you are seeing window larger than your screen check your region settings - the size of the xganim window in pixels
is the size of your region (so either change the region to lower resolution or smaller spatial extent).

We can go through xganim in the lab (I may have it still running on the mac laptop) to make sure 
we have everything in the new animation tool that was in xganim, but I believe that we do,


Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmitaso at ncsu.edu

"All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.” 

On Dec 11, 2013, at 10:38 PM, Vaclav Petras wrote:

> Hi,
> when testing the previous problems with C++11/clang/Mavericks, I used the following compilation settings on Ubuntu 12.04:
>   export CC=clang
>   export CXX=clang++
>   export CFLAGS="-ggdb -Wall -Wextra -Werror-implicit-function-declaration -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls"
>   export CXXFLAGS="-ggdb -std=c++11"
> I get the following errors in `visualization/xganim` directory:
> ./bitmaps/rewind.xbm:4:28: error: constant expression evaluates to 128 which cannot be narrowed to type 'char'
>    0x00, 0x00, 0x00, 0x30, 0x80, 0x01, 0x28, 0x40, 0x01, 0x30, 0xa0, 0x01,
>                            ^~~~
> ./bitmaps/rewind.xbm:4:28: note: override this message by inserting an explicit cast
>    0x00, 0x00, 0x00, 0x30, 0x80, 0x01, 0x28, 0x40, 0x01, 0x30, 0xa0, 0x01,
>                            ^~~~
>                            stat)c_cast<char>(
> and a lot of other similar errors.
> I'm not getting these errors on Mavericks.
> I'm not able to test the xganim tool [1] right now; there is no ready-to-use example and I'm not sure which environment it requires (I'm getting white window bigger than my screen). However, the question is: It is worth keeping the xganim tool in code or should we remove it completely?
> Are there any functions which xganim tool does have comparing to g.gui.animation [2]? Or are there some other advantages of xganim? We should avoid loosing functionality as it was with tools such as gm_animate [3]. So these questions shall be answered before removing xganim.
> Best,
> Vaclav
> [1] http://grass.osgeo.org/grass70/manuals/xganim.html
> [2] http://grass.osgeo.org/grass70/manuals/g.gui.animation.html
> [3] http://grass.osgeo.org/grass64/manuals/gm_animate.html
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

More information about the grass-dev mailing list