![]() ![]() Since the link provided above is concerned with bugs, Im both puzzled about the. But then, Im also in no position to say that it isnt. Ive little doubt that my problem is due to my lack of experience and knowledge of the operation of LibreCad. If there are unwanted effects, I think it's a matter of detailed work flow documentation or CAD block basics description. I have no reason to assume my problem is due to a 'bug'. Having an automatic cloning method with attribute modification may make use more convenient, but it's already possible in the current state. My conclusion is, that we should at least update block instances on attribute modification, this is a bug. It's different from other software like DTP or pixel/vector graphics in common. The main problem I think is to understand the intention behind blocks in sense of CAD. There are pros and cons, but it offers all options to the user. To use an imported block for multiple instances, it must be added by the block list. Adding a block from library browser creates a new entry in the block list for each instance. We already have a cloning method, when using the library browser. ![]() Having only the block editor can make this a torture. But I can imagine situations, where a bunch of simple blocks may be changed this way. Of course it doesn't make much sense to select multiple extensive block instances from different master blocks and apply e.g. I think we should ask the user about his intention if he wants to apply modified attributes to the selected entities only (then clone blocks) or if he wants to apply it to all instances (then modify the block master and update all instances).įorget about my suggestion about limiting block modification. With an automatic clone function on modification we can simplify this. After modification these entities could be joined into a block again.Īnother way is to save a block into a separate DXF file and import it again as a new block to modify. For modification of the master block we already have the block editor, available in the block list.įor block variation we already have the explode tool which split a block into it's basic entities. But the main intention I think is the ability to have multiple block instances controlled by one master. One intention is grouping of multiple entities for easier handling. When a block is modified in the block editor, all instances are updated on closing the I share your understanding of blocks. Editing a block in the block editor does this. I played a little bit with blocks and I think the only problem is, that block attributes modified by modify tool doesn't apply to all instances on an open drawing. Therefore we must create a modified clone of the block for the block table or explode all the modified instances and save them as independent it's hard to say, what's the best solution. The problem is to save the modifications. Your steps 1-5 describe exactly what we have discussed before. It may be there because of inheritance or is an obsolete artefact from early days.Ī block pen doesn't make sense, as a block can contain many entities, different in color, line width and style. Without knowing the the associated source, I think the pen property of blocks is or should be ignored. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |