Jump to content
  • 5

Streamline edits in special groups (annos, modifiers, etc.)


_c_

Question

Streamline edits in Special groups, don't add more to them.

 

We are spending a senseless amount of planning time going in and out of special groups:

  • in and out of slab modifiers, specially the 3D ones,
  • in and out of symbols components (this is massive now)
  • in and out of annotations
  • in and out of live section elevations edits
  • in and out of auto-hybrid
  • in and out of extrudes along path
  • in and out of simple extrudes

and these special groups often combine... 

 

Whenever there is a plane-change involved, this is SO extremely cumbersome for the user. Example: edit 3D modifiers in a slab. It takes a huge lot of view changes, the environment is visible but not actually there, there is no snap....

 

Please collect user data and quantify these actions.
Please do something to optimise it.

 

Below a few screenshots illustrating typical "Special Group" issues.

 

Slab:

 

1845283191_ScreenShot2020-10-01at06_46_33.thumb.png.eb84852b05d45e80b145b3adf2ecb73a.png

 

1424120278_ScreenShot2020-10-01at06_48_29.thumb.png.76542d5134d2fbedc264ff4cbd188a21.png

 

 

793462388_ScreenShot2020-10-01at06_50_28.thumb.png.ec6320232033fccaf1348cb91f13ee19.png

 

Editing the boundary is most times the preferred way, because you can still it directly, using the Reshape tool.

A typical edit involves the cutter, though. But this adds modifiers... and if you are in a boundary [a special group] you can't snap.

 

759438895_ScreenShot2020-10-01at09_57_27.thumb.png.381cac0a8da9c517b36f894a8651c53f.png

 

1024095650_ScreenShot2020-10-01at09_58_02.thumb.png.69776dd444618c5972cb5cf560b00ad3.png

 

Inside the special group "Boundary" you cannot snap and you cannot see outside:

 

1472575537_ScreenShot2020-10-01at10_16_54.thumb.png.dee30c67a2e4e8fb2e2e599e33fbbde7.png

 

 

Edited by _c_
deleted img keeps coming back
  • Like 3
Link to comment

3 answers to this question

Recommended Posts

  • 0

Not directly a special group, but still a major source of troubles in the recommended workflow: class overrides whenever you have more than a handful of viewports.

And any project lasting more than a few weeks will have a huge lot of viewports.

 

1207879566_ScreenShot2020-10-01at09_13_11.thumb.png.9d66694ca455e3e0e4cbf02bd1f1c52f.png

 

698420313_ScreenShot2020-10-01at09_27_18.thumb.png.ef7f4d80ea66beccf907c81d9495b26e.png

 

 

1440044516_ScreenShot2020-10-01at09_12_52.thumb.png.116fad1a9e420bb79b57270c216a0e79.png

 

 

 

Edited by _c_
Link to comment
  • 0

And for those who don't know it, there is pretty efficient way to do this and it works across files.

Don't override the viewports, create a "plot-file", reference the needed source file and override classes for the whole document in this plot file.

You can import classes from the class standards or any other chosen file.

 

You'll never go back to overriding viewports but for the rare exception.

 

 

1735505528_ScreenShot2020-10-01at09_38_26.thumb.png.421850be280f95adac44f334556eae26.png

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...