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.
Is this a DWG file or a DGN file?
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Sorry for the delay. I wonder if anybody can (or can not) confirm this to be an issue? It is a “normal” file aka. a dgn. You think thats a file related issue, Mary B? How come?
I only ask because DWG is notorious for having elements on layer "0". I was wondering if that was carrying through in a DWG, even if you are working in MicroStation, because of the way DWG format saves data. I've also never seen a level 0 in anything that wasn't a DWG file (but I certainly haven't seen everything).Layer "0" functions a little like our Default level, in that cells/blocks created on layer "0" take the symbology of the active layer. It's more complicated than that, but that's my basic understanding. It made me think that your item labels were doing some sort of DWG thing, or might have come from or being placed in a DWG.
Since this a DGN, my idea would be irrelevant.
Hi Mary,
I have created a new file and copied in the element with the item definition. new created file with item labels.dgn
In the new file the labeling goes to NOT to the current active level but to the level "Default"
The previous file - actually as I am revisiting this this file may have originated from a DWG. But it is a long time dgn now.
So my question now is: Why is the strange behaviour coming over after saving a file as DGN.file possibly originating from DWG.dgn
I would need every Label [Place Field] to go to a specific Level
I need to place all my labels on different levels so I can switch them on and off depending on the context. The type of file I need to print aka. Layouts for different aspects of the project, like "Lighting" , "Security Lighting", "Fire Security", etc)
How can I predefine which Level each label needs to go?
If I have to switch the level and place each label one by one this is really impractical
So it sounds as if the behavior between "100% DGN" and "DWG to DGN" is analogous - Layer 0 and our Default layer having similar functions (at least when it comes to cells, and that each drawing has to have them). Not desirable behavior, by any stretch, but consistent. It appears to not be an issue with just the DWG-DGN file - it's showing the same type of behavior in the pure DGN. The labels are being placed onto the default level of the drawing, with no regard for active settings.
I believe what you are expecting to see and are asking for is perfectly reasonable. I'd say it could even be expected behavior!
Unfortunately, that's about as far as I can get with this. I'm still using SS10 in production due to client requirements, so I don't have a lot if experience with Labels. I hope there's someone else with more experience who can help you, or that this hypothesis of the behavior leads toward a solution. Good luck!
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.