Re: [Qgis-developer] Memory data provider persistence
On Mon, Dec 6, 2010 at 10:45 AM, Barry Rowlingson b.rowling...@lancaster.ac.uk wrote: On Mon, Dec 6, 2010 at 2:04 AM, Chris Crook ccr...@linz.govt.nz wrote: So, for my requirement for memory provider persistance, the only real question is what is the right way to do it. Although Martin had suggested a spatialite database, my leaning is towards a simple QDataStream. A simple implementation could be (in crude pseudo code) Qstring header(Qgis data file); Int version = 1; stream header version; Foreach memory_provider if provider persist stream layer_id stream attribute_count foreach attribute stream attribute_definition stream feature_count foreach feature stream feature This could readily be reloaded after the XML project file is read. Because it is processed sequentially it would sit comfortably in a ZIP file and be sequentially read from it without needing to be extracted and then processed (as a spatialite database would need to be). It is portable between OS etc. If the user actually wants a spatialite database, or any other format, then they can save the layer to that. How does this sound to people? It sounds like you're just creating another spatial data format. Why not, on project exit, just go You have unsaved memory data layers - would you like them converted to [gml|shapefile|spatialite|whatever] and reloaded before saving/qutting or do you want to lose them forever?. I completely agree with Barry - to me it looks like a waste of time to invent a new data format - exclusively readable just by QGIS - and intended just to load/store some data from/to memory provider. Additionally, memory provider was thought to represent just temporary (nonpersistent) data - so asking the user to convert it to some other format when exiting seems reasonable to me. Regards Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Memory data provider persistence
On Mon, Dec 6, 2010 at 2:04 AM, Chris Crook ccr...@linz.govt.nz wrote: So, for my requirement for memory provider persistance, the only real question is what is the right way to do it. Although Martin had suggested a spatialite database, my leaning is towards a simple QDataStream. A simple implementation could be (in crude pseudo code) Qstring header(Qgis data file); Int version = 1; stream header version; Foreach memory_provider if provider persist stream layer_id stream attribute_count foreach attribute stream attribute_definition stream feature_count foreach feature stream feature This could readily be reloaded after the XML project file is read. Because it is processed sequentially it would sit comfortably in a ZIP file and be sequentially read from it without needing to be extracted and then processed (as a spatialite database would need to be). It is portable between OS etc. If the user actually wants a spatialite database, or any other format, then they can save the layer to that. How does this sound to people? It sounds like you're just creating another spatial data format. Why not, on project exit, just go You have unsaved memory data layers - would you like them converted to [gml|shapefile|spatialite|whatever] and reloaded before saving/qutting or do you want to lose them forever?. Barry ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Trying to add Dialog window to qgis
Hi, I have client requirement in which I need to modify QGIS application. I download the source code and have built it in Visual Studio 2009 environment. I need to add a new dialog box which will popup on clicking on the button on toolbar. In order to implement this I have added new dialog using Qt designer in ui project but I am not able to access newly created dialog in my qgis project Let me explain with you an example 1) I have created Plans.ui in my ui project. 2) I have changed Plans.ui properties to do custom build as given below Command Line: D:\Qt\4.7.0\bin\uic.exe -o D:/dev/cpp/build/src/ui/ui_Plans.h D:/dev/cpp/src/ui/Plans.ui Description: Generating ui_Plans.h Outputs: D:\dev\cpp\build\src\ui\ui_Plans.h Additional Dependencies: D:\dev\cpp\src\ui\Plans.ui; 3) When I build the ui project I could see ui_Plans.h file getting created 4) I want to access my above Plans window in qgisapp.cpp (qgis project) file. 5) On further researching I found that I need update make file to generate Plans.h and Plans.cpp... But I don't know how to do it... Could any one please throw a light on this as soon as possible It is very urgent Thanks Regards, Azghar Hussain Project Lead (Software) - Risk and Insurance (RI), RMSI Pvt Ltd, A - 7, Sector - 16, Noida - 201301, UP, India Ph: +91 - 120 - 2511102, Ext No. 2611 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Trying to add Dialog window to qgis
Hi, This is basically a Disaster Management Application ... I need to show various data in the form of map and chart...There will also be hazard modeling... Planning to finish in couple of months seems a really nice application, let us know about it, it will be good to have it among the open source applications stack. cheers -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Re: Acknowledgement of Contributor Guidelines
Hi All Any objections to me going on to give Dave write access to SVN? PSC I think you need to vote on this. +1 from me. Regards Tim On Mon, Dec 6, 2010 at 4:27 PM, dave.deh...@sybase.com wrote: In accordance with requirement #6 of the Contributor Guidelines (http://www.qgis.org/wiki/Contributor_Guidelines), I am sending this email to indicate my agreement to abide by those guidelines. --Dave DeHaan David E. DeHaan, Ph.D. SQL Anywhere Research and Development Query Processing team Sybase iAnywhere www.sybase.com/ianywhere Free Developer Edition: http://www.sybase.com/detail?id=1016644 From: Tim Sutton t...@linfiniti.com To: dave.deh...@sybase.com Cc: QGIS Project Steering Committee qgis-...@lists.osgeo.org Date: 11/30/2010 01:56 PM Subject: Re: [Qgis-psc] Contributing an SQL Anywhere plugin/provider Hi Dave On Tue, Nov 30, 2010 at 6:58 PM, dave.deh...@sybase.com wrote: Hello Project Steering Committee, I work for Sybase, performing RD for our SQL Anywhere (SA) product. SA is a cross-platform feature-rich relational DBMS, whose market niches are small- to medium-sized businesses, embedded applications, and mobile environments. Our most recent version (SA12) added comprehensive spatial support, modelled after the SQL/MM and OGC standards. We ship a spatial viewer with our product as part of the administrative tools, but it is exactly that---a viewer intended for developers or administrators, not an end-user GIS application. Many of our customers are new to spatial data and are starting to consider how it might benefit their business. For those customers interested in trying out a feature-rich GIS application, we would like to be able to recommend the Quantum GIS project. From our perspective, enabling QGIS to work with SQL Anywhere could be a benefit both to Sybase customers and to the QGIS project. To that end, I have written a C++ plugin/data-provider combination that interfaces QGIS (works with v1.5 and 1.6) with an SA12 (or later) backend. All that is needed to compile them is a few SA-specific header files, which we have released under the Apache v2.0 licence. To establish a connection to an SA server requires that the client machine has the (proprietary) SQL Anywhere client libraries installed; otherwise a message to that effect is displayed, along with a link to download the free Developer's edition of SA. The plugin/provider code will be released under GPLv3. Although we could distribute it ourselves, we would prefer to contribute it back to the QGIS project so that the SA compatibility is packaged and distributed as part of the main QGIS application. For convenience, we would also contribute the SA-specific headers to the repository (three files subject to the Apache license, not GPL). I would be willing to join the project as maintainer of this code. I look forward to hearing your thoughts on accepting this contribution. Best regards, David DeHaan PS - In the interest of full discloser, over the weekend I had a brief email discussion with Tim, Marco, and Gary about licensing details. They suggested this posting to the PSC once our lawyers signed off on the GPL release, which has now happened. As per our email discussion, I support the addition of this provider and propose Dave be given SVN access so that he can directly contribute and maintain his work. Its really cool to have such additions make their way into the QGIS code base! +1 It would be nice if possible for us (interested QGIS developers I guess) to test the SQL Anywhere provider. Is there some way we can get licenses of SQL Anywhere for personal use or is there otherwise some kind of trial version that we can use for this purpose? Regards Tim David E. DeHaan, Ph.D. SQL Anywhere Research and Development Query Processing team Sybase iAnywhere www.sybase.com/ianywhere ___ Qgis-psc mailing list qgis-...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-psc -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Visit http://linfiniti.com to find out about: * QGIS programming services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Visit http://linfiniti.com to find out about: * QGIS programming services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org
[Qgis-developer] Re: [Qgis-psc] Re: Acknowledgement of Contributor Guidelines
+1 Marco Am Montag, 6. Dezember 2010, um 16.30:01 schrieb Tim Sutton: Hi All Any objections to me going on to give Dave write access to SVN? PSC I think you need to vote on this. +1 from me. Regards Tim On Mon, Dec 6, 2010 at 4:27 PM, dave.deh...@sybase.com wrote: In accordance with requirement #6 of the Contributor Guidelines (http://www.qgis.org/wiki/Contributor_Guidelines), I am sending this email to indicate my agreement to abide by those guidelines. --Dave DeHaan David E. DeHaan, Ph.D. SQL Anywhere Research and Development Query Processing team Sybase iAnywhere www.sybase.com/ianywhere Free Developer Edition: http://www.sybase.com/detail?id=1016644 From: Tim Sutton t...@linfiniti.com To: dave.deh...@sybase.com Cc: QGIS Project Steering Committee qgis-...@lists.osgeo.org Date: 11/30/2010 01:56 PM Subject:Re: [Qgis-psc] Contributing an SQL Anywhere plugin/provider Hi Dave On Tue, Nov 30, 2010 at 6:58 PM, dave.deh...@sybase.com wrote: Hello Project Steering Committee, I work for Sybase, performing RD for our SQL Anywhere (SA) product. SA is a cross-platform feature-rich relational DBMS, whose market niches are small- to medium-sized businesses, embedded applications, and mobile environments. Our most recent version (SA12) added comprehensive spatial support, modelled after the SQL/MM and OGC standards. We ship a spatial viewer with our product as part of the administrative tools, but it is exactly that---a viewer intended for developers or administrators, not an end-user GIS application. Many of our customers are new to spatial data and are starting to consider how it might benefit their business. For those customers interested in trying out a feature-rich GIS application, we would like to be able to recommend the Quantum GIS project. From our perspective, enabling QGIS to work with SQL Anywhere could be a benefit both to Sybase customers and to the QGIS project. To that end, I have written a C++ plugin/data-provider combination that interfaces QGIS (works with v1.5 and 1.6) with an SA12 (or later) backend. All that is needed to compile them is a few SA-specific header files, which we have released under the Apache v2.0 licence. To establish a connection to an SA server requires that the client machine has the (proprietary) SQL Anywhere client libraries installed; otherwise a message to that effect is displayed, along with a link to download the free Developer's edition of SA. The plugin/provider code will be released under GPLv3. Although we could distribute it ourselves, we would prefer to contribute it back to the QGIS project so that the SA compatibility is packaged and distributed as part of the main QGIS application. For convenience, we would also contribute the SA-specific headers to the repository (three files subject to the Apache license, not GPL). I would be willing to join the project as maintainer of this code. I look forward to hearing your thoughts on accepting this contribution. Best regards, David DeHaan PS - In the interest of full discloser, over the weekend I had a brief email discussion with Tim, Marco, and Gary about licensing details. They suggested this posting to the PSC once our lawyers signed off on the GPL release, which has now happened. As per our email discussion, I support the addition of this provider and propose Dave be given SVN access so that he can directly contribute and maintain his work. Its really cool to have such additions make their way into the QGIS code base! +1 It would be nice if possible for us (interested QGIS developers I guess) to test the SQL Anywhere provider. Is there some way we can get licenses of SQL Anywhere for personal use or is there otherwise some kind of trial version that we can use for this purpose? Regards Tim David E. DeHaan, Ph.D. SQL Anywhere Research and Development Query Processing team Sybase iAnywhere www.sybase.com/ianywhere ___ Qgis-psc mailing list qgis-...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-psc -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Visit http://linfiniti.com to find out about: * QGIS programming services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Churerstrasse 22, CH-8808 Pfäffikon SZ, Switzerland marco.hugentob...@sourcepole.ch http://www.sourcepole.ch
[Qgis-developer] Edit UI doesn't load the field's value
Hi all, it seems there is a problem with Edit UI dialog. I have an .UI which contains a combobox and a spinbox. When I edit a row using the Edit UI dialog, the combobox PROVINCIA loads all the values of the PROVINCIA field, but doesn't select the current row value. The spinbox does the same, it doesn't load the current value. If I use lineedits instead, it works and loads the fields' value. Loading only doesn't work, because if I change the value and and press OK the dialog stores the new value back into the field. Does anybody confirm?? Cheers. -- Giuseppe Sucameli ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
RE: [Qgis-developer] Memory data provider persistence
Hi All Fair comment I guess. In fact Barry's suggestion is pretty much back at my original ticket on this issue. This had two components, one was the warning about memory provider layers, and the other was making it easier to save them (or more accurately, to replace the memory layer with the saved layer in the project). Ideally the legend would also have some sort of visual clue as to which layers were not yet saved. Nonetheless I do think there is value in having the memory provided data saved more or less transparently to the user. For example the contour plugin builds its contours in a memory layer. I don't want them to disappear when I save and reopen the project. Yet sometimes I want to save the project quickly without having to decide where and in what format I want bits of it saved. For example when I have to exit the train on the way to work!! I just want to be able to save the project and then start up later and carry on working. While the memory provider is intended for transient data, I think that it is a valid user requirement that it persist beyond the user session. In terms of the QDataStream suggestion, the idea is not to create a format, it is to persist the memory layer efficiently and transparently. I don't think that is the same thing. I guess that the requirements for the format are that it is reasonably compact and can be efficiently read from and written to a sequential data stream (to facilitate possible writing to a zip file or other compressed format in the future). Also it would be nice if it didn't generate a plethora of files. Any other format that meets that requirement would be good, and I certainly agree that using an open format is preferable. Other suggestions?? Cheers Chris From: Martin Dobias [wonder...@gmail.com] Sent: 06 December 2010 22:57 To: Barry Rowlingson Cc: Chris Crook; qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Memory data provider persistence On Mon, Dec 6, 2010 at 10:45 AM, Barry Rowlingson b.rowling...@lancaster.ac.uk wrote: On Mon, Dec 6, 2010 at 2:04 AM, Chris Crook ccr...@linz.govt.nz wrote: So, for my requirement for memory provider persistance, the only real question is what is the right way to do it. Although Martin had suggested a spatialite database, my leaning is towards a simple QDataStream. A simple implementation could be (in crude pseudo code) Qstring header(Qgis data file); Int version = 1; stream header version; Foreach memory_provider if provider persist stream layer_id stream attribute_count foreach attribute stream attribute_definition stream feature_count foreach feature stream feature This could readily be reloaded after the XML project file is read. Because it is processed sequentially it would sit comfortably in a ZIP file and be sequentially read from it without needing to be extracted and then processed (as a spatialite database would need to be). It is portable between OS etc. If the user actually wants a spatialite database, or any other format, then they can save the layer to that. How does this sound to people? It sounds like you're just creating another spatial data format. Why not, on project exit, just go You have unsaved memory data layers - would you like them converted to [gml|shapefile|spatialite|whatever] and reloaded before saving/qutting or do you want to lose them forever?. I completely agree with Barry - to me it looks like a waste of time to invent a new data format - exclusively readable just by QGIS - and intended just to load/store some data from/to memory provider. Additionally, memory provider was thought to represent just temporary (nonpersistent) data - so asking the user to convert it to some other format when exiting seems reasonable to me. Regards Martin __ This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or i...@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank you. __ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
RE: [Qgis-developer] Memory data provider persistence
Hi Barry et al Good point about a plugin implementation .. I hadn't thought of that obvious option - definitely one to follow up on. It might still need a few tweaks in terms of Qgis. The QgisInterface has a projectRead() signal that could be used to trigger reloading the data, but I don't see a projectSaved() signal to trigger writing. Easy to add that though, and probably generally useful. Do you know of an alternative signal I could use to trigger writing? Given that there is a signal to hook in to this is, as you say, a piece of cake. I'm kicking myself for not having thought of this months ago!! In terms of file location my preference would be something directly related to the project file .. That is obviously easy. And shapefile is not my choice, just because of the messy bunch of files it creates and having so many of them and because the DBF format is limiting and pretty scungy! But that is personal preference I guess. Brilliant .. Cheers Chris -Original Message- From: b.rowling...@googlemail.com [mailto:b.rowling...@googlemail.com] On Behalf Of Barry Rowlingson Sent: Tuesday, 7 December 2010 7:40 a.m. To: Chris Crook Cc: Martin Dobias; qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Memory data provider persistence On Mon, Dec 6, 2010 at 6:05 PM, Chris Crook ccr...@linz.govt.nz wrote: Hi All Fair comment I guess. In fact Barry's suggestion is pretty much back at my original ticket on this issue. This had two components, one was the warning about memory provider layers, and the other was making it easier to save them (or more accurately, to replace the memory layer with the saved layer in the project). Ideally the legend would also have some sort of visual clue as to which layers were not yet saved. Nonetheless I do think there is value in having the memory provided data saved more or less transparently to the user. For example the contour plugin builds its contours in a memory layer. I don't want them to disappear when I save and reopen the project. Yet sometimes I want to save the project quickly without having to decide where and in what format I want bits of it saved. For example when I have to exit the train on the way to work!! I just want to be able to save the project and then start up later and carry on working. So as long as the saving of memory layers is quick, you're happy? So what about if it happened transparently that memory layers were saved to /tmp/something in Shapefile format, and the location and format were configurable from a settings dialog and saved (either per-project or in user settings), and that .qgs files added the converted layers into the project? Sounds like a piece of cake, meets the 'train suddenly arriving at station' criterion (although in this country you get an extra twenty minutes past the expected arrival time with trains), and could possibly be implemented as a plugin. You may never lose memory data provider data again... I'm not sure serializing the object to binary is a good idea, you will one day want to load it into another GIS... Standards are a good thing, that's why there are so many of them. Barry __ This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or i...@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank you. __ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] create python plugin for QGIS
Dear all, i have build a plugin for QGIS , and the purpose of this plugin is to insert the data from/to Databse, now there is no action if i click the button of my newly generated plugin, but i want that there will be some action if i click on the particular button , to do my task which file i have to change/update since the plugin contains several file could any of you please help me? ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: 05 - Re: [Qgis-developer] QGIS problem
Hi Alexander , yes, sure , i will give you more information, first of all, when i tried to open the project from with QGIS 1.5.0 then it loads the project but one box open immediately and its shows the following text 1 cursor states lost. SQL: CLOSE qgisf6 Result: 7 (ERROR: current transaction is aborted, commands ignored until end of transaction block ) and i can not click any object from my project which i load , if i click any object then it always show the message which i have mentioned above with best regards Hasan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Memory data provider persistence
On Mon, Dec 6, 2010 at 7:12 PM, Chris Crook ccr...@linz.govt.nz wrote: Hi Barry et al Good point about a plugin implementation .. I hadn't thought of that obvious option - definitely one to follow up on. It might still need a few tweaks in terms of Qgis. The QgisInterface has a projectRead() signal that could be used to trigger reloading the data, but I don't see a projectSaved() signal to trigger writing. Easy to add that though, and probably generally useful. There's a projectWrite signal: http://www.qgis.org/api/classQgsProject.html#a935c811d84c51e908c73868be9b69c4 which seems to be emitted before the layers are saved, so if anything hooked into that wants to make changes it should be able to. Haven't tried, but will that do the job? Given that there is a signal to hook in to this is, as you say, a piece of cake. I'm kicking myself for not having thought of this months ago!! The only problem might be if the memory provider doesn't set the project as dirty when it changes itself. Otherwise users could do a 'quit', and then qgis quits without chance to save the project. In terms of file location my preference would be something directly related to the project file .. That is obviously easy. And shapefile is not my choice, just because of the messy bunch of files it creates and having so many of them and because the DBF format is limiting and pretty scungy! But that is personal preference I guess. Agreed! I've been saving things as GML lately. Barry ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
RE: [Qgis-developer] Memory data provider persistence
Yes .. I got carried away and put up a patch implementing the projectWrite signal in the QgisInterface before I saw this alternative. Though in fact I do think that is makes sense to have a QgsInterface projectSaved() signal matching the projectRead(). And maybe a savingProject() that happens before it is saved. I forgot about needing to catch changes in the memory provider data to set the dirty state .. This was part of my original plan for implementing the memory provider data into the project file itself but I forgot it in my excitement about a plug in option. (The excitement is about being to do it now - I still think this really belongs in the core system). Maybe if I can trap an event relating to saving edits, then if the edited layer provider is a memory provider I can set the project state to dirty. And plugins will have to set the dirty state themselves (this may happen anyway, eg when the contour plugin generates a new contour layer adding the layer sets the state). This is getting a bit messy though! So maybe there is still some work required to provide the signals for changes to vector provider data. In fact the project does need to take ownership of the data. For it all to make sense it needs a projectDataDirty() flag. Bother! Chris -Original Message- From: b.rowling...@googlemail.com [mailto:b.rowling...@googlemail.com] On Behalf Of Barry Rowlingson Sent: Tuesday, 7 December 2010 12:21 p.m. To: Chris Crook Cc: Martin Dobias; qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Memory data provider persistence On Mon, Dec 6, 2010 at 7:12 PM, Chris Crook ccr...@linz.govt.nz wrote: Hi Barry et al Good point about a plugin implementation .. I hadn't thought of that obvious option - definitely one to follow up on. It might still need a few tweaks in terms of Qgis. The QgisInterface has a projectRead() signal that could be used to trigger reloading the data, but I don't see a projectSaved() signal to trigger writing. Easy to add that though, and probably generally useful. There's a projectWrite signal: http://www.qgis.org/api/classQgsProject.html#a935c811d84c51e908c73868be9b69c4 which seems to be emitted before the layers are saved, so if anything hooked into that wants to make changes it should be able to. Haven't tried, but will that do the job? Given that there is a signal to hook in to this is, as you say, a piece of cake. I'm kicking myself for not having thought of this months ago!! The only problem might be if the memory provider doesn't set the project as dirty when it changes itself. Otherwise users could do a 'quit', and then qgis quits without chance to save the project. In terms of file location my preference would be something directly related to the project file .. That is obviously easy. And shapefile is not my choice, just because of the messy bunch of files it creates and having so many of them and because the DBF format is limiting and pretty scungy! But that is personal preference I guess. Agreed! I've been saving things as GML lately. Barry __ This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or i...@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank you. __ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] New composer option
Hi Marco, I was wondering what the new draw map canvas items option does in the composer. I am at a loss to figure it out with some quick testing. Thanks, John___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Edit UI doesn't load the field's value
Hi Giuseppe, I can confirm this behaviour QGIS 1.5/WinXP, data from PostGIS database. My workaround is to have e.g. the QComboBox filled with values and _additionally_ have a QTextLine named the same as the field in my layer table holding the feature's current value. The QTextLine is not visible to the user but gets changed if the user changes the choice in the QComboBox by Qt'S Signal/Slot mechanism. Example: Layer provincia_polygon with field provincia_id (integer) + non-spatial table provincia with fields id (integer) and provincia (varchar). 1) Fill QComboBox cbxProvincia with strings and ids from table provincia. QLineEdit provincia_id gets filled automatically. 2) Set cbxProvincia's current index to the one corresponding to the value in provincia_id. 3) Create a slot updating provincia_id with the id from cbxProvincia's current index. 4) Connect cbxProvincia's SIGNAL currentIndexChanged to this slot. all the best Bernhard Giuseppe Sucameli schrieb: Hi all, it seems there is a problem with Edit UI dialog. I have an .UI which contains a combobox and a spinbox. When I edit a row using the Edit UI dialog, the combobox PROVINCIA loads all the values of the PROVINCIA field, but doesn't select the current row value. The spinbox does the same, it doesn't load the current value. If I use lineedits instead, it works and loads the fields' value. Loading only doesn't work, because if I change the value and and press OK the dialog stores the new value back into the field. Does anybody confirm?? Cheers. -- Giuseppe Sucameli ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer Information from NOD32 This message was checked by NOD32 Antivirus System for Linux Mail Server. http://www.nod32.com Information from NOD32 This message was checked by NOD32 Antivirus System for Linux Mail Server. http://www.nod32.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
