Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Planned
Categories 2D Drawing
Created by Guest
Created on Jan 27, 2021

Hide in VIEW

An option I use to other applications ie Revit and AECOsim is the 'Hide in View' tool. Simply right click on an element and select Hide in View. That element is then hidden. There is an option to view Hidden items, where you can use the un-hide in view.
As mentioned we have the tool in AECOsim but not in MS.
I think this would be very useful in MS
Ian

  • Guest
    Reply
    |
    Nov 6, 2023

    The VBA macro PokeIt has a hide option from the right-click menu. It's a bit of a cheat because it inverts the selection set and then isolates the selection. Is slow in large design files, but it's available today. https://communities.bentley.com/products/programming/microstation_programming/b/weblog/posts/pokeit-select-and-view-elements-based-on-attributes-from-an-element-plus-much-more

  • Guest
    Reply
    |
    Jun 26, 2022

    Apparently there is an MDL for this, written by Yongan.Fu in the ChinaFirst wiki.

    MDLs for both V8i and CE are provided.

    Haven't tried it so do provide feedback. The translation describes hiding but the command is MDL LOAD IsolateSelected

  • Guest
    Reply
    |
    Jun 6, 2021

    Another use case for persistent hides is to do with how ProStructures 'consumes' elements that are modeled in other apps and referenced in.


    A low LOD concrete wall is modeled in Mstn or OpenBuildings Designer. The model is referenced in Prostructures and used to model the rebar for the wall. Prostructures 'overlays' its own information over the ref element. It even replaces the Smartsolid geometry with its own solids. The link is even persistent and associative and can synch to updates in the Ref model.


    What would be good is there was a way to 'hide' the external element in the PS model session, and vice versa when the PS model is ref attached in Mstn or OBD etc. This will need a persistent hiding mechanism at platform level.


    https://docs.bentley.com/LiveContent/web/ProStructures%20Help-v6/en/PS_SOLIDREFERENCECONCRETE.html



  • Guest
    Reply
    |
    Jun 6, 2021

    Agree that the Hide would work better if the user did not have to generate a display set first.


    What would be a lot more useful is if the hiding could be made persistent.


    There are three use cases here:

    1. CVE's Hide Cached Element and Copy/Hide Cached Element. The advantage here is that the hidden elements are persistent. Hopefully, the new Hide command will leverage the same code to allow the user to hide elements in the same way when using normal Ref attachments.

    2. ACAD-style Partial Loading: Mstn's closest equivalent is using Named Groups. The problem is that the NGs have to be defined in the dgn to be attached. Ideally, this should also be possible in the dgn container doing the attaching.

    3. Display Styles: it would be useful if the user could save the hidden elements as a list that DS could use. Ref attachment Name + ElementIDs?



  • Guest
    Reply
    |
    Jun 2, 2021

    First, I agree. Secondly, in the interim, the equivalent of ISOLATE and HIDE can currently be accomplished using the following key-in string (invoke after selecting the element(s):


    ISOLATE SELECTION: "displayset add;displayset set"

    HIDE SELECTION: "displayset add;displayset remove"



  • Guest
    Reply
    |
    Feb 26, 2021

    Hi all, we plan to do implement this kind of functionality and we are investigating different possible routes.

  • Guest
    Reply
    |
    Feb 23, 2021

    Gerd Eisenacher over 3 years ago

    Right, that would be neat. (And as it is a function in AECOsim it might possibly not be not be too much of an issue in MicroStation as well.)

    Ivo Blaauw over 3 years ago

    A bit Like a reverse "Display Set" or "Isolate".
    I like the idea.

    PrattNaval 2 months ago

    This idea would be a great help for us as well - looking forward to its implementation