Customer request ability to edit Linestyles without intermediate steps using .rsc files.
Create New Service Ticket
Problem Area: Custom Line Styles
Inability to directly edit Linestyles contained in active dgn file.
Customer request ability to edit Linestyles in active file without intermediate steps using .rsc files.
8 years later and we are still stuck with the linestyle editor from the days of the original program. :-(
Ryan Mann said:We are still stuck with the linestyle editor from the days of the original program
I agree that the linestyle editor could do with a 21st century refresh, but that's not what this post is about.
Linestyles are intended to be a project resource that allows consistent element display throughout a project. If in-place linestyle editing were to be permitted then each user who takes advantage of that facility would deviate from project standards. It's no different than permitting personal fonts, or using cells from outside a standard project library, or making up your own levels.
Back to the OP: if linestyle editing is permitted 'without intermediate steps using .rsc files', where is the newly-edited linestyle to be stored? Presumably, in the active DGN file. So, what happens when user opens a new DGN file: her linestyle resource is still in the previous DGN file, so what should she do? Recreate the custom linestyle? That impasse is what standards hope to eliminate: if the new linestyle had been created in the project .rsc or, these days, DGNLib, then everyone wins!
Regards, Jon Summers LA Solutions
For me the point of having this is that Bentley is pushing to use dgnlib's to house linestyle libraries. After the linestyle are imported into a dgnlib the only way to edit them is use the clunky resource file editor then reimport. Also with linestyles coming from a dgnlib they will then be copied into the active design file when they are used. That's great for portability but how do I easily update those files if a linestyle changes? Is there an option to update linestyles from the library?
These reminds me of the others DGNlib that easily we can update with a single click on the "Update from Library".
I added myself to the current ticket and this is on the list to implement, but it sounds like it's way down on the list behind a bunch of other things to fix. Here's the info I got back from my ticket.
The Change Request number that you have is an old number from a previous tracking system that we no longer use. The new number in or current system is Defect 117911.
Development has approved the change to be made to the product but it is currently on a backlog of issues that need to be addressed so there is no target release for this change.
I have associated this service request with the defect that is filed.