Re: [Qgis-developer] QGIS indexing data when editing
Dear Nicolas, The indexing is used for snapping in the application. It takes a few sec when enable the first tool, but snapping is much faster later on. Best wishes, Denis On 08/12/2015 02:30 PM, Doctor Who wrote: Hello, I'm using QGIS 2.10.1 and 2.8.3 with PostGreSQL 9.3 and PostGIS 2.5 under Linux openSUSE 13.2 64bits. A strange things appear since i've move from PostGreSQL 9.1 -> 9.3 Each time I open a layer for editing, when I selected any tools (node tools or creation entity tools), QGIS freeze about 30 sec and display 'indexing data' progress bar. (memory of my computer grow up in same time) After that, I could editing my data, close it and reopen editing session whithout any problem or any crash. But if I close my project and reopen it, again indexing data when I want to edit a layer. I've seen that new thing under a small layer (90 entities) and bigger one (about 250 000 objects), same things for Polygon or Point geometry. I've a primary key constraint and a spatial index. Have you already see that somewhere else ? I can't find why as it never happens before. Best regards, Nicolas - -- GIS administrator in Urban Agency of the Greater Amiens Founder and main administrator of forumSIG -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-indexing-data-when-editing-tp5219525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-user] Any working GRASS in QGIS available? - Processing Bug?
Sure thing. Open the .qgis2/python/plugins/processing/algs/grass7/ folder and open the Grass7Algorithm.py file in a text editor. You can see the changes that you'll need to make on GitHub: https://github.com/qgis/QGIS/commit/2a14ffd281d0a0e99a0a899622a29ca0efdb0852 It is just a couple small changes. I suppose alternately you could just download the Grass7Algorithm.py file from GitHub and replace the one in the above mentioned folder. Andrew On Tue, Aug 11, 2015 at 12:29 PM, Bernd Vogelgesang < bernd.vogelges...@gmx.de> wrote: > Hi Andrew > > > Am 06.08.2015, 19:20 Uhr, schrieb Andrew : > > Victor, > > I edited the version of the processing plugin that i have installed (QGIS > 2.8.3, processing 2.10.1) with the changes you made and now GRASS7 tools > work as they should, thanks! > > Andrew > > > Could you maybe describe a little bit what you have changed and how ? > > Bernd > > > > On Thu, Aug 6, 2015 at 5:59 AM, Victor Olaya wrote: > >> A quick (but very relevant) note about GRASS7: >> >> It seems that, in one of the latest changes, I unintentionally left >> out a code line where GRASS was actually being called. I was getting a >> bit crazy wondering where the error might be and why GRASS7 was not >> working in the latest releaseand finally found out that the reason >> was that. So, in short, Processing was not running grass when running >> a grass7 algorithm. >> >> I have added that line back and it should be fine now. >> >> If you can install the current master version, please test and let me >> know if there are any issues or it is working correctly as before. >> >> Regards >> >> >> >> 2015-08-03 1:37 GMT+02:00 Bernd Vogelgesang : >> > Hi Alex >> > >> > Am 03.08.2015, 01:20 Uhr, schrieb Alex Mandel < >> tech_...@wildintellect.com>: >> > >> >> Ah but we're closer to finding a solution with all those details. It >> may >> >> be fixable in Processing, which can be pushed to the plugin repo for >> >> update any time. >> >> >> >> Passing this along to devs who might have enough information now. >> >> >> >> Thanks, >> >> Alex >> > >> > >> > >> > Thanks for taking care, >> > >> > by the way: by copying the gdal algorithms from processing 2.10.1 to the >> > 2.9.3 folder (.qgis2/python/plugins/processing/algs/gdal), I gained >> access >> > to the new GDAL dissolve polygons :) >> > >> > Unfortunately, the model from before (GRASS6) didn't work anymore, and >> all >> > attempts to adjust it via diff of a test model failed. So reworking my >> model >> > (for the 10th time or so) in Ubuntu 2.8.3 from ubuntugis-ltr with >> working >> > GRASS7, SAGA and everything and a partially upgraded Processing 2.9.3 >> > >> > I'm on my way ... finally .. hopefully ... >> > >> > Bernd >> > >> > >> > >> >> On 08/02/2015 03:07 PM, Bernd Vogelgesang wrote: >> >>> >> >>> Am 02.08.2015, 22:44 Uhr, schrieb Alex Mandel >> >>> : >> >>> >> After some brief testing, my OSGeoLive 8.5 VM with QGIS 2.6 and >> Processing 2.9.3, GRASS 7 works. >> >> My QGIS 2.8, GRASS 6/7, Processing 2.10.1 does not. >> >>> >> >>> >> >>> Gave Windows another try: Removed everything, and installed the simple >> >>> install OSGEO4W setup. >> >>> QGIS 2.10.1 with Processing 2.10.1 and GRASS 6 working. >> >>> >> >>> switched back to Ubuntu, cause of a bug in the modeler version of GDAL >> >>> Dissolve Polygons (which is crucial for me). >> >>> https://hub.qgis.org/issues/13174 >> >>> >> >>> Ubuntu: Now that I installed 2.8 with the debian repository only (so >> >>> without ubuntis depencies), my GRASS 6 works (sorted out another >> error, >> >>> that GRASS takes a column name "OR" from shape as an sql-command or >> >>> sth), update to Processing 2.10.1 worked as well. >> >>> >> >>> The drawback, no SAGA, which might come handy cause the now available >> >>> algos do not really do what I expect ;) >> >>> >> >>> I think the problem is within Processing in combination with the >> >>> packaging: >> >>> When e.g. I install QGIS 2.8 with ubuntugis-ltr dependencies (where >> >>> nobody on the install page claims I shouldn't do), GRASS7 and the >> >>> modeler are working, but Processing version is 2.6. Updating >> Processing >> >>> to current Processing 2.10.1 (as recommended) seems to work. >> >>> (Besides that v.clean in the modeler only returns a polygon layer from >> >>> an polygon input, if I also set an output name for the error layer, >> >>> otherwise I get an empty line shape) >> >>> >> >>> But: The next time I run QGIS and want to run an GRASS algo: Missing >> >>> depencies >> >>> >> >>> I can now replace Processing 2.10.1 with the second latest 2.9.3 from >> >>> https://plugins.qgis.org/plugins/processing/version/2.9.3/ >> >>> and there v.clean does what it should in Processing AND modeler. >> >>> >> >>> But: Now I do not have GDAL Dissolve polygons which is in Processing >> >>> 2.10.1. Well, I could switch back to Windows QGIS 2.10, but, grr, >> there >> >>> is the bug in this algo ... >> >>> >> >>> You see, I'm trapped. >> >>> >>
Re: [Qgis-developer] CI testing for OSX
Hi > On 12 Aug 2015, at 15:43, Nyall Dawson wrote: > > Good news everybody! > > With recent changes to the Travis CI service we've now been able to > unlock multi-OS continuous integration testing of QGIS. This means > that now every commit and pull request will be tested on both a Linux > and OSX build. > > End result is that our OSX build should be more stable and widely tested. Awesome stuff Nyall - can you give any notes on what specifically you had to do to enable OS X testing? Regards Tim > > Nyall > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer Tim Sutton QGIS Project Steering Committee Member t...@qgis.org ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Building plugin for Print Composer
We have talked a lot with Nyall about this. It was a requirement for a work
I was developing some months ago (it's what I was describing some emails
ago in this thead).
I suppose the work Nyall is talking about is the deep refactoring of the
Composer which will converge in the Report engine (QGIS > 3.x), is it right?
giovanni
2015-08-08 11:19 GMT+02:00 Nyall Dawson :
>
> On 7 Aug 2015 6:58 pm, "Vincent Mora" wrote:
> >
> > Hi all,
> >
> > I need to add graphs generated by a plugin to compositions. I'm
> considering to develop a PluginComposerItem in the same spirit as
> PluginLayers, adding/removing a button in the toolbar when the plugin is
> registered/removed.
>
> Just a warning that similar work is already underway - adding a composer
> item type registry so that plugins can register their own custom item
> types.
>
> It's an extensive work though, because composer has a lot of hard coded
> handling of all the existing item types (checkout all the item specific
> methods in QgsComposition/QgsComposerView). That's why this work is tied up
> with the layouts/reporting framework refactor.
>
> Nyall
>
> >
> > Is that what was needed in your cases, or was a more general approach
> required (like the qgis plugin mechanism, being able to access the
> interface) ?
> >
> > V.
> >
> >
> > Le 22/06/2015 18:05, G. Allegri a écrit :
> >>
> >> The suggestion from John is exactly what we did too. And we also built
> a chart composer...
> >>
> >> It would be great to have the means to know what other teams are
> working to. It would save a lor of time and money and, probably, get better
> software from a shared effort ;)
> >>
> >> giovanni
> >>
> >> Il 22/giu/2015 19:31, "John Gitau" ha scritto:
> >>>
> >>> Hi Jakob,
> >>>
> >>> A workaround would be to have a plugin that creates a new composer
> view object:
> >>>
> >>> custom_composer = self.iface.createNewComposer("My Composer")
> >>>
> >>> Then get a reference to the main window in the composer view:
> >>>
> >>> main_window = custom_composer.composerWindow()
> >>>
> >>> Then you can either add a new toolbar (and required actions) or append
> an action to the main toolbar. Have a look at the ComposerWrapper class for
> something similar we implemented for designing charts in the composer:
> https://gist.github.com/gkahiu/06a43a589f9441736397
> >>>
> >>> Hope this is helpful.
> >>>
> >>> Cheers,
> >>>
> >>> John
> >>>
> >>> On Mon, Jun 22, 2015 at 2:07 PM, G. Allegri
> wrote:
>
> You can act on it but you can't custom gui widgets to the Composer
> interface.
> I cannot check the code right know. I listen to a specific (existing)
> composition opening but if I remember correctly you can watch the Composer
> opening too.
>
> Il 22/giu/2015 17:19, "Jakob Lanstorp" ha
> scritto:
> >
> > Hi Giovanni, thanks for the update. Another solution would be to
> catch the
> > event when a user starts an existing print composer. Cannot in doc
> for the
> > pyqgis API find anything for this. Anyone who know is one can
> listens for a
> > print composer to startup by the user and act on it.
> >
> >
> >
> > -
> > Jakob Lanstorp
> > --
> > View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Building-plugin-for-Print-Composer-tp5212187p5212221.html
> > Sent from the Quantum GIS - Developer mailing list archive at
> Nabble.com.
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >>>
> >>>
> >>>
> >>> ___
> >>> Qgis-developer mailing list
> >>> Qgis-developer@lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >>
> >>
> >>
> >> ___
> >> Qgis-developer mailing list
> >> Qgis-developer@lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> >
> >
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
--
Giovanni Allegri
http://about.me/giovanniallegri
Gis3W - http://gis3w.it
Ikare - http://ikare.it
Twitter: https://twitter.com/_giohappy_
blog: http://blog.spaziogis.it
GEO+ geomatica in Italia http://bit.ly/GEOplus
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] CI testing for OSX
My package should have the Oracle plugin. No way to test though. On Aug 12, 2015, at 9:11 AM, Nyall Dawson wrote: > On 13 August 2015 at 00:08, chris marx wrote: >> That's great news. Is there any chance of getting a Mac/Linux build of QGIS >> with the oracle support turned on? Or at least some way to do it that >> doesn't involve building from source? > > I'm not sure what's involved in that... in any case, it's a totally > different discussion :) > > Nyall > > >> >> On Wed, Aug 12, 2015 at 10:03 AM, Matthias Kuhn wrote: >>> >>> Thanks for that! >>> >>> On 08/12/2015 03:43 PM, Nyall Dawson wrote: Good news everybody! With recent changes to the Travis CI service we've now been able to unlock multi-OS continuous integration testing of QGIS. This means that now every commit and pull request will be tested on both a Linux and OSX build. End result is that our OSX build should be more stable and widely tested. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> >>> >>> >>> ___ >>> Qgis-developer mailing list >>> Qgis-developer@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> >> >> >> ___ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer - William Kyngesburye http://www.kyngchaos.com/ All generalizations are dangerous, even this one. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] CI testing for OSX
On 12-08-15 15:43, Nyall Dawson wrote: > Good news everybody! > > With recent changes to the Travis CI service we've now been able to > unlock multi-OS continuous integration testing of QGIS. This means > that now every commit and pull request will be tested on both a Linux > and OSX build. > > End result is that our OSX build should be more stable and widely tested. Cool! Thanks Nyall (and Matthias and everybody else busy with the testing stuff). Stability == GOOD Regards, Richard Duivenvoorde ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] CI testing for OSX
On 13 August 2015 at 00:08, chris marx wrote: > That's great news. Is there any chance of getting a Mac/Linux build of QGIS > with the oracle support turned on? Or at least some way to do it that > doesn't involve building from source? I'm not sure what's involved in that... in any case, it's a totally different discussion :) Nyall > > On Wed, Aug 12, 2015 at 10:03 AM, Matthias Kuhn wrote: >> >> Thanks for that! >> >> On 08/12/2015 03:43 PM, Nyall Dawson wrote: >> > Good news everybody! >> > >> > With recent changes to the Travis CI service we've now been able to >> > unlock multi-OS continuous integration testing of QGIS. This means >> > that now every commit and pull request will be tested on both a Linux >> > and OSX build. >> > >> > End result is that our OSX build should be more stable and widely >> > tested. >> > >> > Nyall >> > ___ >> > Qgis-developer mailing list >> > Qgis-developer@lists.osgeo.org >> > http://lists.osgeo.org/mailman/listinfo/qgis-developer >> >> >> >> ___ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] CI testing for OSX
That's great news. Is there any chance of getting a Mac/Linux build of QGIS with the oracle support turned on? Or at least some way to do it that doesn't involve building from source? Thanks, Chris- On Wed, Aug 12, 2015 at 10:03 AM, Matthias Kuhn wrote: > Thanks for that! > > On 08/12/2015 03:43 PM, Nyall Dawson wrote: > > Good news everybody! > > > > With recent changes to the Travis CI service we've now been able to > > unlock multi-OS continuous integration testing of QGIS. This means > > that now every commit and pull request will be tested on both a Linux > > and OSX build. > > > > End result is that our OSX build should be more stable and widely tested. > > > > Nyall > > ___ > > Qgis-developer mailing list > > Qgis-developer@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] CI testing for OSX
Thanks for that! On 08/12/2015 03:43 PM, Nyall Dawson wrote: > Good news everybody! > > With recent changes to the Travis CI service we've now been able to > unlock multi-OS continuous integration testing of QGIS. This means > that now every commit and pull request will be tested on both a Linux > and OSX build. > > End result is that our OSX build should be more stable and widely tested. > > Nyall > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] CI testing for OSX
Good news everybody! With recent changes to the Travis CI service we've now been able to unlock multi-OS continuous integration testing of QGIS. This means that now every commit and pull request will be tested on both a Linux and OSX build. End result is that our OSX build should be more stable and widely tested. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] QGIS indexing data when editing
Hello, I'm using QGIS 2.10.1 and 2.8.3 with PostGreSQL 9.3 and PostGIS 2.5 under Linux openSUSE 13.2 64bits. A strange things appear since i've move from PostGreSQL 9.1 -> 9.3 Each time I open a layer for editing, when I selected any tools (node tools or creation entity tools), QGIS freeze about 30 sec and display 'indexing data' progress bar. (memory of my computer grow up in same time) After that, I could editing my data, close it and reopen editing session whithout any problem or any crash. But if I close my project and reopen it, again indexing data when I want to edit a layer. I've seen that new thing under a small layer (90 entities) and bigger one (about 250 000 objects), same things for Polygon or Point geometry. I've a primary key constraint and a spatial index. Have you already see that somewhere else ? I can't find why as it never happens before. Best regards, Nicolas - -- GIS administrator in Urban Agency of the Greater Amiens Founder and main administrator of forumSIG -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-indexing-data-when-editing-tp5219525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Empty selectedFeatures list
Hi Jürgen On 08/12/2015 10:51 AM, Jürgen E. Fischer wrote: > Hi Matthias, > > On Wed, 12. Aug 2015 at 10:21:50 +0200, Matthias Kuhn wrote: >> To avoid confusion: the error in the log before said "expression tree >> too large" and not "expression text too long". > Didn't anyone claim otherwise? Not directly, but reading Anita's question I got the feeling that it could have been misinterpreted. I thought it's better to state it explicitly ;) Matthias signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Empty selectedFeatures list
Hi Matthias, On Wed, 12. Aug 2015 at 10:21:50 +0200, Matthias Kuhn wrote: > To avoid confusion: the error in the log before said "expression tree > too large" and not "expression text too long". Didn't anyone claim otherwise? > So it is very well possible that the issue is completely solved with > this change (but that needs to be verified first!) At least it's not tied to 1000 anymore - but yes, there might be still some other sqlite limitation. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Empty selectedFeatures list
Hi, On 08/12/2015 10:08 AM, Jürgen E. Fischer wrote: > Hi Anita, > > On Wed, 12. Aug 2015 at 09:57:48 +0200, Anita Graser wrote: >> Will it now throw an error when the request is too huge? > No, selectedFeatures doesn't have a way to return errors (other than returning > a list that has less entries than selectedFeatureCount()). To avoid confusion: the error in the log before said "expression tree too large" and not "expression text too long". So it is very well possible that the issue is completely solved with this change (but that needs to be verified first!) Matthias signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Empty selectedFeatures list
Hi Anita, On Wed, 12. Aug 2015 at 09:57:48 +0200, Anita Graser wrote: > Will it now throw an error when the request is too huge? No, selectedFeatures doesn't have a way to return errors (other than returning a list that has less entries than selectedFeatureCount()). Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Empty selectedFeatures list
On Wed, Aug 12, 2015 at 9:14 AM, Jürgen E. wrote: > Hi Matthias, > > On Wed, 12. Aug 2015 at 08:31:00 +0200, Matthias Kuhn wrote: > > I can imagine it is related to sending huge request like "fid=1 or fid=2 > > or fid=3 or fid=4..." and spatialite does not like it... I will try if > > changing it to "fid in (1,2,3,4...)" makes it any better. > > > Anyway, please open a ticket for it, this definitely looks like a bug. > > Aren't you tracking github? That's already fixed in > > 45d4dbe ;) > Thanks Jürgen! From what I can see in 45d4dbe, the request should now be smaller. Will it now throw an error when the request is too huge? Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Empty selectedFeatures list
Hi Matthias, On Wed, 12. Aug 2015 at 08:31:00 +0200, Matthias Kuhn wrote: > I can imagine it is related to sending huge request like "fid=1 or fid=2 > or fid=3 or fid=4..." and spatialite does not like it... I will try if > changing it to "fid in (1,2,3,4...)" makes it any better. > Anyway, please open a ticket for it, this definitely looks like a bug. Aren't you tracking github? That's already fixed in 45d4dbe ;) Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
