[GRASS-dev] Windows-style Pathnames

Glynn Clements glynn at gclements.plus.com
Tue Nov 7 01:03:34 EST 2006

Hamish wrote:

> > Yes. The way I've done that in the is first to pass the string
> > containing  the path to G_convert_dirseps_to_host(), which will
> > replace all occurences  of / by \, and then quote the path name with
> > \"escaped double quotes\"  within the argument supplied to system() -
> > I think this should cover both  eventualities of the pathname
> > containing spaces, *and* the backslashes  possibly being
> > misinterpreted by a shell. Although as we've seen it should  normally
> > by cmd.exe invoked for this.
> does it check/strip existing " before adding new ones?
> > especially if we get display drivers working.
> it would be nice to go directly to a simple wxPython canvas window that
> could take d.* cmds, instead of bothering to adapt XDRIVER... but the
> PNG driver was a problem too, yes? So we need a socket-less PNG driver?
> or a new direct rendering wxDRIVER? (simple d.mon replacement, probably
> nothing to do with gis manager gui canvas?)

The problem is specifically with standalone drivers; driver-less
rendering works on Windows. A GUI application shouldn't be using
standalone drivers, and I'd rather see a remote-control feature added
to the GUI than putting significant effort into making mon.start work
on Windows.

Glynn Clements <glynn at gclements.plus.com>

More information about the grass-dev mailing list