gvSIG bugs #3555
No se puede aplicar etiquetado definido por el usuario
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  José Badía | |||
| Category: | Labeling | |||
| Target version: | - | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.2.0 | Add-on build: | ||
| gvSIG build: | 2311 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
En la capa adjunta no es posible aplicar un etiquetado definido por el usuario (todas las entidades de la misma manera). He probado con otras capas y sí que se puede. No obstante interesaría saber qué tiene de especial esta ya que está descargada del Catastro y potencialmente pueden utilizarla muchos usuarios.
Related issues
History
#1
Updated by Antonio Falciano almost 9 years ago
Hi Manuel,
I've checked your layer and found that all its field names contain an underscore and they're not validated by the expression parser. For instance, if I rename the "2_DENOMINA" field as "DENOMINA" (without underscore), a label expression with the new name is considered valid and the labels appear. So the issue is caused by the underscore in the field names. Cheers.
#2
Updated by Álvaro Anguix almost 9 years ago
Exacto, es lo que comenta Antonio. Si pones la tabla en edición, abres el gestor de la tabla y renombras el campo, podrás etiquetar sin problemas.
#3
Updated by Álvaro Anguix almost 9 years ago
- Status changed from New to Won't fix
Me lo apunto para documentarlo en el manual.
#4
Updated by Antonio Falciano almost 9 years ago
Hi Alvaro,
in my humble opinion, this is a bug. It's sad to have to document time consuming workarounds in the manual. Why can't it be fixed?
#6
Updated by Antonio Falciano almost 9 years ago
Álvaro Anguix wrote:
I've investigated further and discovered that SQLJEP supports well the field names that contain the underscore (see its examples of usage here), as in vaious SQL dialects.I agree. :-)
For exactness, the bug in object happens when the field name starts with a number or underscore. For instance:
- 2_DENOMINA ...doesn't work
- _DENOMINA ...doesn't work
- B_DENOMINA ...works
So the field names need to be escaped in order to work. I would suggest to use the square brackets (as it was in gvSIG 1.x) in order to avoid further confusion with single or double quotes. Single quotes work fine with strings actually. Cheers.
#7
Updated by Álvaro Anguix over 8 years ago
- Assignee set to José Badía
#8
Updated by Álvaro Anguix over 8 years ago
- Related to gvSIG bugs #3849: No funciona correctamente el etiquetado definido por el usuario added
#9
Updated by Álvaro Anguix about 4 years ago
- Status changed from New to Closed
Al incluir el nuevo motor de expresiones, funciona correctamente.