Does anyone know how to keep linestyles from automatically being loaded into dgnlib'sand dgn files? I have been trying to limit the number of linestyles available to our usersbut this autocreation of linestyles in files is making it almost impossible to purge them.
Any help would be appreciated.
Tom
Just by coincidence, we have a ticket in support for that very subject right now... Line styles aren't something that we work with very much in the building team so we've enlisted some internal help.
But if anyone reading this happens to know, we're all ears! :)
If you are meaning custom Linestyles, then these are loaded by default from your workspace system\symb\ directory and your standards\symb\ directory. The definition of these directories is controlled by the MS_SYMBRSRC config variable.
They are resource files with *.rsc extension, though some of those will be font files. The line style ones will hopefully have used *lstyle* in the name and *font* for the font files.
People tend to change jobs and take their *.rsc files with them and if not controlled over time it can end up becoming a mess with duplicate names in multiple files. You can try and figure out what is what in the custom line style editor or you can move all the files out and put them back one at a time to see what you get. But it will be a pain to straighten out if you want to keep some from one file and some from others. HTH
Steve and Dennis,
Let me clarify my original comment.
What I did was remove the resource file that had many of the new linestyles
with the intent to add only the linestyles i would like to keep to a new resource.
There are some really cool new custom linestyles available.
But what I found is when I removed the resource file all the linestyles
still remained.
So I went the menu "Element>Linestyles>Custom and it indicated that
the linestyles that used to be in the resource are all in the current file.
I compressed file with the delete linestyles option checked and it removed
linestyles from the current file but they were still available.
Now it indicated were in one of my dgnlib libraries.
Changed the offending dgnlib to a dgn so I could compress the linestyles from file
and then renamed back to dgnlib.
Re-opened the orignal dgn file and all the linestyles were again available.
Not from a dgnlib but actually back in the file. Urrgh.
Compressed the file again and the linestyle now were showing from
a different dgnlib.
To sum it up, I had to systematically go through multiple dgnlib's
and purge the linestyles from each one. This method removed many of the linestyles.
But the dgnlib tree ended up at a Bentley delievered file on the c:\drive.
Very difficult to remove these styles on each computer.
Basically what I noticed is when I compressed the linestyles out of a file.
Closed the file and reopened all the linestyles were copied back into the file.
It had been happening without me knowing each time I had opened one of our
dgnlib too.
My question is how can I stop all the linestyles from being copied into each
file that is opened. I only want "used linestyles" to be added to a file
and others only to be referenced; Either from a linestyle resource or a dgnlib.
With the current behavior it is impossible to manage.
They are everywhere.
Tom, what you're describing is very much like what we saw, where the process to permanently remove Line Styles is not that apparent. And yes, it does seem as though the DGNLib storage aspect is where the process seems to differ since with RSC files alone it's fairly straightforward, as Dennis mentioned.
Yes. When it was just resource files, managing them was easier.
With the current behavior, the most problematic part is the linestyles
are copied into every file upon opening it.
So eventhough, I cleaned up the linestyles in dgnlib's to a point.
Every file that was previously opened still has all the linestyles in them.
This reminds me, I need to go check my seed files.
Hopefully a better way of managing them will be forth coming in a future release.
Yes... Any DGN files opened previously while the line styles existed somewhere will have them written locally, so will have to be compressed to remove them. This could probably be done as a batch process.