gvSIG bugs #110
Fields that shouldn't be enabled when defining a new layer
| Status: | Closed | % Done: | 100% | |
|---|---|---|---|---|
| Priority: | Urgent | Spent time: | - | |
| Assignee: |  Jorge Piera | |||
| Category: | Document view | |||
| Target version: | 2.0.0-alpha4 | |||
| Severity: | Add-on version: | 2.0.0 | ||
| gvSIG version: | 2.0.0 | Add-on build: | 2042 | |
| gvSIG build: | 2042 | Add-on resolve version: | 2.0.0 | |
| Operative System: | Add-on resolve build: | 2044 | ||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: |
Description
When the user is crating a new layer (shapefile at least) one of the steps is to define the table structure. For each field he must set the following parameters:
- "Field" (better called "Field name")
- "Type"
- "Lenght"
- "geomType"
- "geomSubtype"
- "CRS"
- "primaryKey"
- "mandatory"
Fields "geomType", "geomSubtype" and "CRS" should only be enabled when "Type" is "Geometry". Otherwise user could set different type of geometry, subgeometry and CRS to different fields in the same table, which is not logical.
History
#1
Updated by Joaquín del Cerro Murciano over 12 years ago
- Assignee set to Jorge Piera
- Target version set to 2.0.0-alpha4
#2
Updated by Jorge Piera over 12 years ago
- Status changed from New to In progress
- Add-on name deleted (
org.gvsig.gvsigapp)
#3
Updated by Jorge Piera over 12 years ago
- Status changed from In progress to Fixed
- % Done changed from 0 to 100
- Add-on resolve version set to 2.0.0
- Add-on resolve build set to 2044
When the firld type is "Geometry", a "Not applicable" label is displayed in the fields that are not applicable.
#4
Updated by Abenchara Socorro over 11 years ago
- Status changed from Fixed to Closed