network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 7 months |
| seen | yesterday | |
| stats | profile views | 11 |
|
1d |
accepted | How to handle adding a PostGIS layer in pyQgis without saving password? |
|
Apr 10 |
awarded | Tumbleweed |
|
Apr 3 |
asked | How to handle adding a PostGIS layer in pyQgis without saving password? |
|
Mar 7 |
comment |
Handle add new feature event and/or access feature before commit? Thanks for guidance Kelly. It is new application for the users, so looks like I should definitely continue with 2.0, however the only problem is that I don't know when 2.0 can be released, while I need to deliver the final version after 2 months. |
|
Mar 7 |
accepted | Handle add new feature event and/or access feature before commit? |
|
Mar 6 |
accepted | Get feature while editing |
|
Mar 6 |
awarded | Commentator |
|
Mar 6 |
comment |
Handle add new feature event and/or access feature before commit? I'm confused now which version I should proceed with, since if I go with 1.8 it will not work with 2.0 later on. Is there any source with the latest PyQGIS API documentation on the Internet (not for 1.8)? |
|
Mar 6 |
comment |
Handle add new feature event and/or access feature before commit? I did some tests and yes, featureAdded doesn't work for memory and postgres layers in 1.8 and master. However, thank you for the clue, so I can at least find new features now. Unfortunately it is not very effective with big layers, as you noted. It would be nice if it is possible to pick up all changed features from provider or elsewhere, including new, modified and deleted... |
|
Mar 4 |
comment |
Handle add new feature event and/or access feature before commit? It is 1.8, but think to switch on 1.9 since there are some bugs fixed in the latest build. |
|
Mar 3 |
comment |
Handle add new feature event and/or access feature before commit? Hi Kelly, I forgot to mention that I'm using PostgreSQL layer and I tried to handle featureAdded signal with no luck.
QObject.connect(layer, SIGNAL("featureAdded(qint64)"), self.featureAdded).
However, editingStarted and editingStopped work ok. So, I'm looking for any solution either to catch featureAdded event or at least to have an access to the new features before commit. |
|
Mar 2 |
awarded | Scholar |
|
Mar 2 |
accepted | QGIS line style |
|
Mar 1 |
asked | Handle add new feature event and/or access feature before commit? |
|
Mar 1 |
comment |
Get feature while editing Thanks, found it. Yes, I guess it is a bug. If after assigning editForm in the code I go to the layer's properties (Fields) and select Attribute editor layout = Provide ui-file I can see a correct path to the UI form. If I click OK now, to save settings and try to add new features, my form pops up as it was before. |
|
Mar 1 |
comment |
Get feature while editing Looks like layer.setEditForm("form.ui") doesn't work anymore with the latest buid (1.9.0 b5dc778). I also can't find UI Edit form setting on the layer's properties in QGIS. |
|
Feb 28 |
comment |
Get feature while editing Meanwhile, does it mean that if I create a couple of new features, it still won't possible to extract them somehow from the layer afterwards, but before calling save on the layer? |
|
Feb 28 |
comment |
Get feature while editing Hi Nathan, thanks for your prompt response. I will try with the latest version then. Do you have any prediction on 2.0 release? I know there is a discussion around it, but maybe you have some fresh updates. |
|
Feb 27 |
asked | Get feature while editing |
|
Feb 5 |
asked | Handling save event in QGIS |
