When I place a Item text (label) they are placed on Level "0"
1. I would expect them to be on the active level (at least!)
Better I need them to be on a specific level. This would allow me to have some labels visible or not depending on what I need to see in a specific context.
One needs to move the label to the right level one by one. Is that the workflow? That does not feel right.
Also:
2.The visibility icons (in the localized version are barely visible - SR filed )
3. The new editing dialog (when you doubleclick a label) appears not to work right. I am not able to switch visibility.
Thanks Mary, I am trying this - once in a while - since the introduction of "items".
I always find it hard to belive how "off" a reasonable/to be expected behaviour functionalities can be possibly implemented. With CE17 there are some things implemented. But - not by a long shot - are useable in production.
The lack of other replies may indicate that others gave up on it for the time being. I am not sure what to make of it. I have also -again- written Service Tickets. Because I think a userfriendly reporting would be of great benefit for all.
mlm said:The lack of other replies may indicate that others gave up on it
The annotations or labels created by our TagWorks products — AreaAnnotator et al. — do what one expects. I don't know why a developer inside Bentley Systems would ignore convention...
Regards, Jon Summers LA Solutions
Hi Jon, hi all,
Area Annotator is - as the name implies - a tool to annotate areas like rooms, floors etc., right? What about cells of machinery, installation, symbolic representation of HVAC objects etc.
Following I collect expectations that are scattered over threads, tickets and ideas elsewhere already.
What we (correct me if I am wrong or if there is something I forgot) expect from "Item fields" is that.
1.it allows to "label" ad-hoc any object with properties to place a text besides it
a. on a specific level for each field (to switch off parts of the "stamp" depending on a layouts context. E.g. on a overview drawing for installation I need to see all electrcal installation with some info like what type of outlet you have.
b. the "set of fields" moves/rotates (AND copies!) with a cell (or another element). - Like tags still "behave"!
c. you can move the set of fields. E.g. to the other side of a symbol as dense placement may demand.
e. If you have a label attached to an object it is necesssary to backwards identify to which object it belongs (highlight?). Because in a tightly packed situation it may be hard to know - or a field has been moved far away.
d. one can also define a leader line/box/? from the element to the "set of fields)
d. (if need be to SaveAs to dwg - which happens increasingly create a cell from any element with properties that is not a cell in dgn)
2. One can build a cell with a predefined set of fields from properties (again like with tags) each field on specific levels.
a. when you place that cell you ideally are asked to fill out the fields (override defaults)
b. after placing the cell the "set of fields" can be moved around as required. When you move the cell the "set of labels" is moved (like anchored)
c. copying a cell/element with a "set of fields" needs to copy the cell/element including the label - without the ado to collect the element and the fields beforehand as of now(?) (again like with tags). After copying you may need go ahead to edit the properties, obviously.
The functionalites may well already be available but the handling is often still impractical.
We need the comprehensive set of functionalities to get the usability when you are handling thousands of properties.
From here is should be easy to then get the benefit of reporting like bill of materials, dynamic tables, etc.
(The wording "tags" "labels", "fields", "annotation", "stamp" etc. in this context are quite interchangeable and there seem to sprout more new words every once in a while whis is adding confusion in my mind)
At last: it would be a stroke of genius if we could work through existing drawings (with simple text) and (half) automaiticly create "intelligent" drawings.
mlm said:What about cells of machinery, installation, symbolic representation of HVAC objects etc
Products in our TagWorks family already cover some of those. In each case, you define the cells that are used for annotation.
Jon Summers said:TagWorks family already cover some of those
That is nice. Can you cover which are or not?
Actually I appreciate it. Although it is a hard sell internally. Additional implementation and installation. Would only be confidently arguable if it would be a specific requirement. Particularly as these should fairly be generic(?) functionality and as it is not localised - those Germans again you know ...