There are 4 more questions I have about the vector panel in the GIS Manager
so that I can update it.
There are 2 checkboxes labeled "print query output as text in terminal" and
"edit attributes"
The first call the -x flag which, according to the docs (and d.vect) is
"Don't add to list of vectors and commands in monitor". The latter *sounds*
like it is keeping the d.vect results out of the list that d.redraw checks.
Is this what it is doing? If not, what IS it doing. I have yet to see the
query output printed as text in the terminal. This does not seem to be a
correct description of the flag. Is it worth keeping in the GIS Manager
version of d.vect?
The second calls a -e flag. There is no such flag listed in the docs. Is
this a holdover from an earlier version? Should I get rid of it?
As I thought I understood it, the print width setting only works with
ps.map. But perhaps it is called if you use the print dialog in the GIS
Manager? I guess the question is does this setting actually do anything from
within the GIS Manager or is it something that people will only be able to
use via ps.map?
Finally, an option that is NOT in the GIS Manager vector panel is the -c
flag. This fills areas with random colors based on the cat field. I thought
I'd add this if there is interest.
Thanks for your help.
Michael
____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA
There are 4 more questions I have about the vector panel in the GIS Manager
so that I can update it.
There are 2 checkboxes labeled "print query output as text in terminal" and
"edit attributes"
The first call the -x flag which, according to the docs (and d.vect) is
"Don't add to list of vectors and commands in monitor". The latter *sounds*
like it is keeping the d.vect results out of the list that d.redraw checks.
Is this what it is doing? If not, what IS it doing. I have yet to see the
query output printed as text in the terminal. This does not seem to be a
correct description of the flag. Is it worth keeping in the GIS Manager
version of d.vect?
The second calls a -e flag. There is no such flag listed in the docs. Is
this a holdover from an earlier version? Should I get rid of it?
As I thought I understood it, the print width setting only works with
ps.map. But perhaps it is called if you use the print dialog in the GIS
Manager? I guess the question is does this setting actually do anything from
within the GIS Manager or is it something that people will only be able to
use via ps.map?
Finally, an option that is NOT in the GIS Manager vector panel is the -c
flag. This fills areas with random colors based on the cat field. I thought
I'd add this if there is interest.
On Mon, December 13, 2004 5:39, Michael Barton said:
As I thought I understood it, the print width setting only works with
ps.map. But perhaps it is called if you use the print dialog in the GIS
Manager? I guess the question is does this setting actually do anything from
within the GIS Manager or is it something that people will only be able to
use via ps.map?
As far as I understand the GIS Manager print dialog calls ps.map.
Finally, an option that is NOT in the GIS Manager vector panel is the -c
flag. This fills areas with random colors based on the cat field. I thought
I'd add this if there is interest.
I've never really had any need for random coloring. However, if it would be
possible to substitute this by a colour palette (i.e. red to green, or
greyscale, etc) then it would be very interesting.
While I was confused about the function of these options, all are in the
tcltk code for the vector display panel in the d.m. All but the -e flag are
in d.vect.
Moritz filled me in on print width and I've gone ahead and added the -c
flag. It looks to me that the -e flag is a mistake. This leaves the -x flag.
I'm not sure it's helpful in the d.m. But I'd like to see if anyone
agrees/disagrees.
Cheers
Michael
On 12/13/04 1:47 AM, "Radim Blazek" <blazek@itc.it> wrote:
Michael Barton wrote:
There are 4 more questions I have about the vector panel in the GIS Manager
so that I can update it.
There are 2 checkboxes labeled "print query output as text in terminal" and
"edit attributes"
The first call the -x flag which, according to the docs (and d.vect) is
"Don't add to list of vectors and commands in monitor". The latter *sounds*
like it is keeping the d.vect results out of the list that d.redraw checks.
Is this what it is doing? If not, what IS it doing. I have yet to see the
query output printed as text in the terminal. This does not seem to be a
correct description of the flag. Is it worth keeping in the GIS Manager
version of d.vect?
The second calls a -e flag. There is no such flag listed in the docs. Is
this a holdover from an earlier version? Should I get rid of it?
As I thought I understood it, the print width setting only works with
ps.map. But perhaps it is called if you use the print dialog in the GIS
Manager? I guess the question is does this setting actually do anything from
within the GIS Manager or is it something that people will only be able to
use via ps.map?
Finally, an option that is NOT in the GIS Manager vector panel is the -c
flag. This fills areas with random colors based on the cat field. I thought
I'd add this if there is interest.
Thanks for your help.
Michael
You are mixing d.vect and d.what.vect, I guess.
Radim
______________________________
Michael Barton, Professor of Anthropology
School of Human, Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
On Mon, December 13, 2004 15:56, Michael Barton said:
Radim,
While I was confused about the function of these options, all are in the
tcltk code for the vector display panel in the d.m. All but the -e flag are
in d.vect.
Moritz filled me in on print width and I've gone ahead and added the -c
flag. It looks to me that the -e flag is a mistake. This leaves the -x flag.
I'm not sure it's helpful in the d.m. But I'd like to see if anyone
agrees/disagrees.
I agree with you. I would just confuse users. And those that want to use it
are probably more of the command line type anyhow.
Moritz
Cheers
Michael
On 12/13/04 1:47 AM, "Radim Blazek" <blazek@itc.it> wrote:
Michael Barton wrote:
There are 4 more questions I have about the vector panel in the GIS Manager
so that I can update it.
There are 2 checkboxes labeled "print query output as text in terminal" and
"edit attributes"
The first call the -x flag which, according to the docs (and d.vect) is
"Don't add to list of vectors and commands in monitor". The latter *sounds*
like it is keeping the d.vect results out of the list that d.redraw checks.
Is this what it is doing? If not, what IS it doing. I have yet to see the
query output printed as text in the terminal. This does not seem to be a
correct description of the flag. Is it worth keeping in the GIS Manager
version of d.vect?
The second calls a -e flag. There is no such flag listed in the docs. Is
this a holdover from an earlier version? Should I get rid of it?
As I thought I understood it, the print width setting only works with
ps.map. But perhaps it is called if you use the print dialog in the GIS
Manager? I guess the question is does this setting actually do anything
from
within the GIS Manager or is it something that people will only be able to
use via ps.map?
Finally, an option that is NOT in the GIS Manager vector panel is the -c
flag. This fills areas with random colors based on the cat field. I thought
I'd add this if there is interest.
Thanks for your help.
Michael
You are mixing d.vect and d.what.vect, I guess.
Radim
______________________________
Michael Barton, Professor of Anthropology
School of Human, Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
There are 2 checkboxes labeled "print query output as text in
terminal" and"edit attributes"
The first call the -x flag which, according to the docs (and d.vect)
is"Don't add to list of vectors and commands in monitor". The latter
*sounds* like it is keeping the d.vect results out of the list that
d.redraw checks. Is this what it is doing? If not, what IS it doing. I
have yet to see the query output printed as text in the terminal. This
does not seem to be a correct description of the flag. Is it worth
keeping in the GIS Manager version of d.vect?
The second calls a -e flag. There is no such flag listed in the docs.
Is this a holdover from an earlier version? Should I get rid of it?
These two affect d.what.vect when run from the "?" icon in d.m.
So not d.vect flags at all...
When running in MacOSX I needed to use the "Print query output as text
in terminal" (ie -x flag) as the d.what.vect Tcl GUI didn't work.. maybe
that is still the case?
OK, I see what you mean now. I think this is a relatively new addition,
which may explain my confusion.
I just checked to see if the tcltk form mode for d.what.vect works yet on a
Mac and it doesn't. You still have to output to terminal.
Now that I understand why this has been added, I agree that it is necessary
to keep both flags. I'll add a bit of explanation to the vector panel to
make this clearer.
Michael
On 12/13/04 6:41 PM, "Hamish" <hamish_nospam@yahoo.com> wrote:
There are 2 checkboxes labeled "print query output as text in
terminal" and"edit attributes"
The first call the -x flag which, according to the docs (and d.vect)
is"Don't add to list of vectors and commands in monitor". The latter
*sounds* like it is keeping the d.vect results out of the list that
d.redraw checks. Is this what it is doing? If not, what IS it doing. I
have yet to see the query output printed as text in the terminal. This
does not seem to be a correct description of the flag. Is it worth
keeping in the GIS Manager version of d.vect?
The second calls a -e flag. There is no such flag listed in the docs.
Is this a holdover from an earlier version? Should I get rid of it?
These two affect d.what.vect when run from the "?" icon in d.m.
So not d.vect flags at all...
When running in MacOSX I needed to use the "Print query output as text
in terminal" (ie -x flag) as the d.what.vect Tcl GUI didn't work.. maybe
that is still the case?
Hamish
____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA
On Mon, December 13, 2004 15:56, Michael Barton said:
While I was confused about the function of these options, all are in the
tcltk code for the vector display panel in the d.m. All but the -e flag are
in d.vect.
Moritz filled me in on print width and I've gone ahead and added the -c
flag. It looks to me that the -e flag is a mistake. This leaves the -x flag.
I'm not sure it's helpful in the d.m. But I'd like to see if anyone
agrees/disagrees.
I agree with you. I would just confuse users. And those that want to use it
are probably more of the command line type anyhow.
>
On 12/13/04 1:47 AM, "Radim Blazek" <blazek@itc.it> wrote:
There are 2 checkboxes labeled "print query output as text in terminal" and
"edit attributes"
Yes.
The first call the -x flag which, according to the docs (and d.vect) is
"Don't add to list of vectors and commands in monitor". The latter *sounds*
like it is keeping the d.vect results out of the list that d.redraw checks.
That is true for d.vect, but it is used for d.what.vect, without this checkbox and option nobody can use GUI form.
Is this what it is doing? If not, what IS it doing. I have yet to see the
query output printed as text in the terminal. This does not seem to be a
correct description of the flag. Is it worth keeping in the GIS Manager
version of d.vect?
Yes, it must be there at least until GUI form works on all platforms. In GIS manager there is 'vector layer' which is using d.vect and d.what.vect, it is not just d.vect.
The second calls a -e flag. There is no such flag listed in the docs. Is
this a holdover from an earlier version? Should I get rid of it?
d.what.vect :
-e Open form in edit mode.
Also this option is important.
As I thought I understood it, the print width setting only works with
ps.map. But perhaps it is called if you use the print dialog in the GIS
Manager? I guess the question is does this setting actually do anything
from
within the GIS Manager or is it something that people will only be able to
use via ps.map?
Of course it does. PS maps generated from GIS Manager use this parameter.