Hi,
imho the best way would be, to connect new WX monitors, so they work via
command line interface. Some proposal interface was there (see p.mon &
friends in wxgui source) - using temporary files for the communication
jachym
[EMAIL PROTECTED] píše v Ne 09. 03. 2008 v 12:32 +0100:
> Dear all,
>
Maybe this would help on windows as well? Currently, you have to install
tcltk 8.4, to get nviz working
jachym
William Kyngesburye píše v Ne 09. 03. 2008 v 19:52 -0500:
> Ah, it looks like --enable-xft is a new option in Tk 8.5, and is
> enabled by default. In the working Tiger TclTk 8.5 GUI,
Ah, it looks like --enable-xft is a new option in Tk 8.5, and is
enabled by default. In the working Tiger TclTk 8.5 GUI, the menu
fonts look nice, compared to the 8.4 GUI.
So, disabled xft and now TclTk 8.5 GUI works on Leopard. NVIZ also
works. NVIZ still won't run on Tiger though.
On
On Mar 9, 2008, at 2:16 PM, [EMAIL PROTECTED] wrote:
Date: Sun, 9 Mar 2008 19:26:39 +0100
From: "Martin Landa" <[EMAIL PROTECTED]>
Subject: Re: [GRASS-dev] how to start wx vdigit?
To: "William Kyngesburye" <[EMAIL PROTECTED]>
Cc: Michael Barton <[EMAIL PROTECTED]>, GRASS developers list
On Mar 8, 2008, at 9:06 AM, Michael Barton wrote:
For 8.5 it apparently mostly works, if it is just a few little issues
which are not so hard to fix, then we should try and solve them.
i.e. we should at least look into 8.5 problems, it is probably just
1-5
lines of code to be adjusted, and th
#61: vdigit makefile uses hardwired compile and link flags
+---
Reporter: kyngchaos | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Mil
#58: v.digit relies upon non-portable hacks
---+
Reporter: marisn| Owner: martinl
Type: defect| Status: assigned
Priority: critical | Milestone: 6.3.0
Component: def
Oops, forgot the -shared flag in the vdigit makefile. It ended up
linking as a program. See: http://trac.osgeo.org/grass/ticket/61
Changed the shared flag to something appropriate for OSX, and I didn't
need to add the "import wx" to grass6_wxvdigit.py.
I successfully digitized a boundary.
On Mar 9, 2008, at 2:43 PM, Martin Landa wrote:
Now fixed in trunk, http://trac.osgeo.org/grass/changeset/30510
Yep, works now.
important is the last part of the message which comes when you try to
import grass6_wxvdigit Python module .
Try:
cd gui/wxpython/vdigit
python
import grass6_wxvd
Hi,
2008/3/9, William Kyngesburye <[EMAIL PROTECTED]>:
> I wanted to start with an empty vector map, so I tried to create one
> from the GUI. Error in console:
>
> Traceback (most recent call last):
>File "/Applications/GRASS-6.3.app/Contents/MacOS/etc/wxpython/
> wxgui.py", line 433, in
OK, here's what I got:
I wanted to start with an empty vector map, so I tried to create one
from the GUI. Error in console:
Traceback (most recent call last):
File "/Applications/GRASS-6.3.app/Contents/MacOS/etc/wxpython/
wxgui.py", line 433, in OnMenuCmd
menuform.GUI().ParseCommand(
Hi,
there currently two ways
1) add vector map layer into the layer tree, right click and from
contextual menu choose 'Start editing'
2) select in Map display window toolbar 'Digitize' (the last tool in
the toolbar), then from enabled vdigit toolbar choose vector map layer
you want to edit (this
I'm testing a possible solution to compiling the wx vdigit on OSX, but
I can't figure out how to start it.
In the wx gui, Vector->Develop vector map->Digitize vector map runs
the TclTk v.digit, not the wxpython digitizer. I have my vdigit test
built and it looks like it's installed (etc/wx
I can build an OSX GRASS app with TclTk 8.5 for others to test, and
try it myself.
If we intend to support multiple versions of TclTk, it would be
helpful to have a TCLTKVER variable in Platform.make for the
configured major.minor version.
On Mar 8, 2008, at 9:06 AM, Michael Barton wrote:
#83: r.param.scale - plan curvature doesn't work
--+-
Reporter: guano| Owner: guano
Type: defect | Status: assigned
Priority: major| Milestone: 6.3.0
Component: defa
#67: r.out.gdal type= and no-data issues
---+
Reporter: sieczka | Owner: martinl
Type: defect| Status: closed
Priority: critical | Milestone: 6.3.0
Component: default |
Dear all,
I would like to look into supporting d.mon and friends under native Win.
As far as I understand, we need two things:
1. A native Windows graphics device, so we won't need an X Server
for the graphics output.
2. A BSD style sockets interface, so the d.* commands can communicate
with t
Rewrite this in python ?
or using new gdal features
jachym
Hamish píše v So 08. 03. 2008 v 20:27 -0800:
> Hi,
>
> re. r.in.wms XML paring code for layers with spaces in the name
>
> given some text like this:
>
> DATA="Foo Bar Baz"
> echo "$DATA" | sed -e "s/\s*\(\w*\)/~\1~/g" -e "s/<\/Name>
Hi all,
just some thought on the SoC project(s)
>>
>> * displaced symbols.
>>Create a module to place map symbols on a map, so that the
>>feature and other overlap information is minimized (NP-Complete
>>problem). The map symbol should be referenced to their original
>>location, b
19 matches
Mail list logo
