My thoughts and fears on using text styles in Border-Seed-Files.

Hi,

Please note that the idea of an DGNlib is that this kind of files should be place on server and end user don't have access to this.

Once this is done each user can change text style parameters inside each output files that is not a problem.

This operation changes the icon of the text style to a blue triangule so the user can see that's diferent from the source.

https://communities.bentley.com/products/microstation/w/microstation__wiki/15179/text-style-icon-color-changes

At any time users can revert back to the source parameters from the DGNlib file and make you should make sure users update this.

https://communities.bentley.com/products/microstation/w/microstation__wiki/11665/text-styles---text---microstation

If end user does not want to use the source parameters you can deploy your DGNlib file on the network without text styles which is not standard procedure.

In my opinion seed file should have text style associate.

If you deply your source files without linkage and after you make small or large update/correction you'll have more work to get everthing updated.

Regards

I create and store my text styles in a DGNLIB file, which is stored on the network as part of our standard workspace. That way, if a text style gets out of whack, it can be "reset" to the default value from the network resource. I prefer that method to trying to store my text styles in the drawings themselves - for just the reason you mention. If The text styles are only stored to the drawing, if something gets messed up, there's no central resource to go back to.

If a user needs to make a modification to a standard text style, it does get written into the drawing and stored there, but it can always be reset to the standard if we need to.

A networked DGNLIB is what I would recommend, as opposed to creating your text styles just in your seed file.

I agree with José. Place the dgnlib files on a server, modify the access rights so that those files are read-only for standard users, and give yourself (and other admin types) modify rights.

This not only applies to your dgnlib files with text styles, but other resource dgnlib files with levels, dimension styles, print styles, etc.

Even within the same file text styles can bite you in the tushy. I've got in the habit of never clicking save for a text style change, unless I'm adjusting standard stuff. Others use different approach, creating many text styles to satisfy their needs. You can use the Annotation Lock in conjunction with the scale to account for different drawing scales.

Hello
and thanks for sharing your opinions.

My thoughts of a clean system are in line with your statements.
Unfortunately, we can not cover everything so easily.
For our small group this could still work, if there were not the general network problem .....
For various reasons, we currently have all the resources locally on the PC's.
One major reason is to be able to continue working even in the case of network failure.
And more recently, cloud delusions have broken out in our company and we are no longer allowed to store data on our local network but we must use our cloud services (Sharepoint and One-Drive) .... which, in my opinion, is an absolute no-go.

Maybe it could be possible to solve this problem by a specially shared network structure, if the company will allow this.

Then there would still be the problem that our drawings are regularly processed by internal and external contractors / subcontractors, and there again I see the problem that text styles in the given drawings can be changed intentionally or unintentionally.

How could we handle this problem for external editing?

At the same time I think about something else ....
I read about the possibility to check drawings for standard integrity.
How does it work and could it be used to quickly find out if non-standard text-styles was used?

Thanks

Best regards
Raphael