>> Any chance to get this change back-ported to 1.10 so QGIS 2.0 will
>> work with FIleGDBs?
> I've just done that (although the changeset is a bit more substantial/risky
> than the usual fixes done in stable branch).
Thanks!
I see the QGIS dev team is looking to release 2.0 about the 7th of Se
esday, 13 August 2013 9:50 p.m.
> To: Even Rouault
> Cc: 'gdal-dev@lists.osgeo.org'; 'qgis-develo...@lists.osgeo.org'
> Subject: RE: [gdal-dev] QGIS hanging when opening a FileGDB on 64 bit Linux
>
> Nope I get a crash when opening now via OGRSFDriverRegistrar::Op
From: Jeremy Palmer
Sent: Tuesday, 13 August 2013 9:50 p.m.
To: Even Rouault
Cc: 'gdal-dev@lists.osgeo.org'; 'qgis-develo...@lists.osgeo.org'
Subject: RE: [gdal-dev] QGIS hanging when opening a FileGDB on 64 bit Linux
Nope I get a crash when opening now via OGRSFD
: Even Rouault [even.roua...@mines-paris.org]
Sent: Tuesday, 13 August 2013 7:23 p.m.
To: Jeremy Palmer
Cc: 'Even Rouault'; 'gdal-dev@lists.osgeo.org'; 'qgis-develo...@lists.osgeo.org'
Subject: RE: [gdal-dev] QGIS hanging when opening a FileGDB on 64 bit Linux
Selon Jere
ginal Message-
> From: Even Rouault [mailto:even.roua...@mines-paris.org]
> Sent: Tuesday, 13 August 2013 11:29 a.m.
> To: gdal-dev@lists.osgeo.org
> Cc: Jeremy Palmer; 'qgis-develo...@lists.osgeo.org'
> Subject: Re: [gdal-dev] QGIS hanging when opening a FileGDB on 64 bit
a.m.
To: gdal-dev@lists.osgeo.org
Cc: Jeremy Palmer; 'qgis-develo...@lists.osgeo.org'
Subject: Re: [gdal-dev] QGIS hanging when opening a FileGDB on 64 bit Linux
Le lundi 12 août 2013 22:12:11, Jeremy Palmer a écrit :
> Further to this I see that when you open a FIleGDB in QGIS 3 OG
Le lundi 12 août 2013 22:12:11, Jeremy Palmer a écrit :
> Further to this I see that when you open a FIleGDB in QGIS 3 OGROpen calls
> made to the same database before any OGR_DS_Destroy calls are made. These
> open calls occur during the layer selection dialog, the OGR provider
> construction, and
Further to this I see that when you open a FIleGDB in QGIS 3 OGROpen calls made
to the same database before any OGR_DS_Destroy calls are made. These open calls
occur during the layer selection dialog, the OGR provider construction, and the
initialisation of the QgsOgrFeatureIterator.
I'm guessi
