‘\U+0020’ as a space in AutoCAD attribute going into Vault

[warrentdo]

Hello All,

Just before I start testing has anyone had any experiences of using ‘\U+0020’ to mimic a space when using it in the property name of an AutoCAD block that will be mapped to vault?

Has using ‘\U+0020’ caused any other issues that you are aware of? 

Regards,

Warren.

[pendean]

Test it.

[paullimapa]

Question: Why would you need another character to mimic a space?  Does Vault not support spaces in block names in AutoCAD?

[warrentdo]

Before I test it I was looking for any other isues that I may come across later down the line. I was trying to look for help and use the experience of the group. There is no point testing if there are known issues. 

[warrentdo]

Hello, this is not a space in a block name, but a space in a property name which i believe that AutoCAD will not. Vault will except spaces in both.

[paullimapa]

Here's a screenshot showing the Properties of a Block in AutoCAD. Some of these Properties shown obviously cannot have a space like Scale X, Y & Z.

But a number of the Properties do support a space in AutoCAD. So which of these Properties are you referring to that currently cannot have a space and you want to replace with ‘\U+0020’?

[warrentdo]

Hello, these will be custom properties. 'Room Number' 'Area Type' etc.

[paullimapa]

How do you add custom properties to a Block in plain AutoCAD?

[warrentdo]

ATTDEF. the property name is represented by the TAG name.

[cadffm]

so we speaking about simple ATTRIB tags

Okay.

You are right, Spaces are not allowed [F1] ATTDEF

But by programming, it is possible to do that for existing (blockreference)attributes.

Back to your U+0020 Question: THIS WORKS on Acad side. (Note: I didn't test all functions, but it works generally)

[cadffm]

---

@warrentdo  schrieb:

Has using ‘\U+0020’ caused any other issues that you are aware of? 

---

I guess, near to nobody have expierence with that (perhaps I am wrong and for Vault users it is a common workareound),

because it sounds a bit crazy (I would never do that)

For usual you should use UPPERCASE chars withour special characters for Attdes/Attributes.

I tested (and it works):

EATTEDIT

DATAEXTRACT

FIND

properties-palette to change ATTRIB value

ATTOUT/ATTIN

REFEDIT

BEDIT

ATTSYNC

..

Failed:

BATTMAN

properties-palette to change ATTDEF tag

ddedit  to change ATTDEF tag

..

Now it's an you or others, to check each single function.

[warrentdo]

I agree that the naming convention is crazy, but unfortunately im being forced into this.