wingrass: new wxgui dialog for v.in.ogr in windows7 does not show *.shp files

[marmai]

I work with wingrass native installer 6.4.1 RC1 on Windows7. When chosing in the wxgui: file -> import vector -> common import formats, I get the new dialog. When I chose here for source "file" and for format "ESRI shapefile" and click the "browse" botton, I do not get any shapefiles in the dialog. When entering the first letter of the shapefile I want to import in the "filename" field of the win7 dialog, a list of files with this letter is shown (also the shapefile I want to import). See screenshot. I expect, that the win7 dialog to chose the files, does show files of a wrong filetyp. I am not able to change the filetyp to "all files" instead of "shapefiles".

[marmai]

vector import dialog

[hellik]

Replying to marmai:

I work with wingrass native installer 6.4.1 RC1 on Windows7.

please try one of the latest nightly builds, because IIRC there were some changes regarding this.

Helmut

[hellik]

Replying to hellik:

please try one of the latest nightly builds,

just forgotten: ​http://josef.fsv.cvut.cz/wingrass/grass64/

[hellik]

WinGRASS-6.4.SVN-r45623-VectorImport

[hellik]

Replying to hellik:

Replying to hellik:

please try one of the latest nightly builds,

just forgotten: ​http://josef.fsv.cvut.cz/wingrass/grass64/

tested with WinGRASS-6.4.SVN-r45623-1-Setup.exe on my WinVista32-box. can you test on your Win7-box?

Helmut

[martinl]

Replying to hellik:

tested with WinGRASS-6.4.SVN-r45623-1-Setup.exe on my WinVista32-box. can you test on your Win7-box?

right, it has been recently fixed, works for me with the latest winGRASS build. This bug was also reported by Mac users.

[hellik]

Replying to martinl:

Replying to hellik:

tested with WinGRASS-6.4.SVN-r45623-1-Setup.exe on my WinVista32-box. can you test on your Win7-box?

right, it has been recently fixed, works for me with the latest winGRASS build. This bug was also reported by Mac users.

again forgotten, it's also ok here in my winvista-box (see screenshot).

[hamish]

Hi,

in all cases the file selector's extension type filter should offer a secondary option of "All files (*.*)" if it otherwise chooses one for you. It shouldn't lock users into its own limited assumptions about how files should be named.

e.g. GeoTIFF often comes as .tiff or .geotiff; jpeg as .jpeg; GRIB format raster input is often as .grib or without extension, not just *.grb, *.GRB, etc. Nice to have it pre-filter, but hard-locking it to just a short list of pre-chosen extension choices (usually munged into 8.3 DOS extension limits) creates a road block which doesn't need to be there, so the user needs a way to bypass that if they need to.

thanks, Hamish

[martinl]

Replying to hamish:

in all cases the file selector's extension type filter should offer a secondary option of "All files (*.*)" if it otherwise chooses one for you. It shouldn't lock users into its own limited assumptions about how files should be named.

done in r45846. Milestone postponed to 6.4.2.