[SoC] [GRASS-dev] Weekly report #3 - GRASS Interactive Scatter Plot Tool
Michael Barton
Michael.Barton at asu.edu
Sun Jul 7 12:43:48 PDT 2013
Are you planning to use wxPlot for the scatterplot display? This provides a consistent graphical interface with the other plotting modules.
Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On Jul 7, 2013, at 10:21 AM, Štěpán Turek <stepan.turek at seznam.cz<mailto:stepan.turek at seznam.cz>>
wrote:
Hi,
yes, you can just run your command giving the right environment variables...
I have just one more question.
Will it work properly when I will call some function from C libraries:
Im my case it is something like this:
int I_ComputeScatts(struct Cell_head *region, struct scCats * scatt_conds, const char ** bands,
int n_bands, struct scCats * scatt_plts, const char ** cats_rasts)
scatt_conds are selected areas in open scatter plots and scatt_plts there are returned computed scatter plots. Let say that this function will be called in separate process form wxGUI created by multiprocessing module. And in this function there is used raster library.
Is it (or can be) this raster library independent form raster library loaded to wxGUI and from the other processes created from wxGUI?
Let say that this function will call Rast_set_window function. Will be raster region set only in scope of the separate process or also out of it?
If the libraries are independent it solves the issue.
Best
Stepan
_______________________________________________
SoC mailing list
SoC at lists.osgeo.org<mailto:SoC at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/soc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/soc/attachments/20130707/83634993/attachment.html>
More information about the SoC
mailing list