Bug report #10719
Disable the "toggle editing" button for the datasources that cannot be edited
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Digitising | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | up/downstream |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 19107 |
Description
QGIS is not yet able to edit MI files. But when you have a .TAB file in you project, it is still possible to toggle it in edition. All the other edition tools are greyed but it remains possible to modify the attribute table and follow the process of saving, even if no change will be kept at the end.
On .MIF layers, the "add geometry" and "paste" tools are accessible in edition even though they are useless.
I think, to not put in confusion the user, all those tools should be greyed.
Related issues
History
#1
Updated by Giovanni Manghi over 10 years ago
- Subject changed from MapInfo Files: Editing tools might all be greyed to Disable the "toggle editing" button for the datasources that cannot be edited
#2
Updated by Jürgen Fischer over 10 years ago
- Resolution set to up/downstream
Seems to be a problem in the OGR driver. It reports that the OLCCreateField is always possible, although it apparently requires TABWrite mode. Unlike the OLCSequentialWrite capability, which is reported unavailable when TABWrite isn't available. See also GDAL #5539
#3
Updated by Giovanni Manghi over 10 years ago
- Status changed from Open to Closed
#4
Updated by Harrissou Santanna over 9 years ago
- Target version changed from Version 2.4 to Future Release - Nice to have
- Status changed from Closed to Reopened
Hi,
Until GDAL/OGR solved the problem, it may be great to pop-up a message that explains to the user, while trying to save changes into MapInfo files, that edition is not yet possible on such a layer (except virtual fields?). He won't therefore waste his time to try and try and try again without understanding what's going wrong....
#5
Updated by Giovanni Manghi over 9 years ago
- Status changed from Reopened to Closed
Harrissou Santanna wrote:
Hi,
Until GDAL/OGR solved the problem, it may be great to pop-up a message that explains to the user, while trying to save changes into MapInfo files, that edition is not yet possible on such a layer (except virtual fields?). He won't therefore waste his time to try and try and try again without understanding what's going wrong....
better file a new ticket with a feature request.