V12 Editing features in diagram broken

[Paolo F Cantoni]

Is it just me, but when I try to edit attributes directly in the diagram, the attribute is "trashed".  For example suppose I have:
AttributeName datatype
And I try and change the name to SomeAttribute Datatype,
I end up with Some (and no Datatype).  It's REALLY annoying if I forget to View Properties on the attribute and edit it in the dialog - where things work OK.

Anyone else seeing this or just me?  I'd like confirmation before I report it.

TIA,
Paolo

[KP]

Inline editing doesn't work if you have spaces in the attribute name. Is that the problem?

[qwerty]

Woaa. I almost never use inline editing. But this got top of EAUI at once.

q.

[Paolo F Cantoni]

Inline editing doesn't work if you have spaces in the attribute name. Is that the problem?

Yes  It is.  I suspected same, but didn't want to bias the responses.

So is it a bug?  I'd say so.  Whether there are spaces in the name or not, the syntax is pretty explicit.

Paolo

[Paolo F Cantoni]

Woaa. I almost never use inline editing. But this got top of EAUI at once.

q.

Yes, It's always been a bit "Iffy" so I avoid it, but sometimes, you can't stop yourself...

Paolo

[Eve]

So is it a bug?  I'd say so.  Whether there are spaces in the name or not, the syntax is pretty explicit.

It's not expected to handle spaces in the name. When we wrote the parser that powers that feature we had to make some restrictions.

However, what may be a bug is that it accepted a partial parse as valid.

[Paolo F Cantoni]

So is it a bug?  I'd say so.  Whether there are spaces in the name or not, the syntax is pretty explicit.

It's not expected to handle spaces in the name. When we wrote the parser that powers that feature we had to make some restrictions.

However, what may be a bug is that it accepted a partial parse as valid.

It's a bug ...

Since (as far as I can tell) ALL the other input/edit mechanisms ALLOW spaces in the attribute name, to have this mechanism NOT handle them is INVALID.

The inconsistent (and therefore wrong) decision was made in design/coding.

Reported,
Paolo

[Eve]

This method of input is fundamentally different from dialog based input where one entry box represents the exact contents of exactly one field. Extending your argument, I should also be able to define attribute names containing punctuation including colon.

[Paolo F Cantoni]

This method of input is fundamentally different from dialog based input where one entry box represents the exact contents of exactly one field. Extending your argument, I should also be able to define attribute names containing punctuation including colon.

No, that's not what I'm saying.  It's a consistency thing.

I strongly suspect that if colons were allowed in attribute names, one could come up with an algorithm that would sort it out for you!  I mean Microsoft managed it - allowing embedded periods (full stops) in file names and still using it to separate the file base name from the file extension.

It just takes more "Denkstoff".

Paolo