sketchucation logo sketchucation
    • Login
    ℹ️ Licensed Extensions | FredoBatch, ElevationProfile, FredoSketch, LayOps, MatSim and Pic2Shape will require license from Sept 1st More Info

    DCs to store information

    Scheduled Pinned Locked Moved Dynamic Components
    sketchup
    2 Posts 2 Posters 458 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      smpfmc
      last edited by

      Hi we're working with DCs & using them to store information about objects (i.e. date installed, manufactured etc) to build up a record of projects as they are constructed. We have had to make similar objects unique in order to do this because if we do not then when a value is entered into a component the value appears in all similar components. This value can be over-written to enter a unique value but does anyone know of a way of surpressing the value from appearing in other similar objects when it's entered without making the objects unique? This would prevent an old value (from another component) being left in a component when one hadn't yet been entered for that component.

      I have another question that I'l post separately about adding new attributes to multiple components.

      Thanks to anyone who takes the time to read this & hopefully someone has an answer.

      1 Reply Last reply Reply Quote 0
      • TIGT Offline
        TIG Moderator
        last edited by

        If you insert DCs then they are automatically made unique by design, so editing the attributes of one only affects that one. Unless you have nested DCs... when the unique containers could then contain repeated versions of the same DC, which of course will change globally should you edit any of that DC's attributes in one container.
        A DC that is copied in a model will be just that - a second instance of the same DC - so editing one will then change the other too - but that is useful if you have six identical widgets and you want to change their manufacturer en mass.
        So have attributes you want to remain unique attached to the container DC so each unique instance has unique attributes, and conversely any attributes you might want to capable of change en mass should be attached to a nested DC, so then changing one will ripple through to several.

        TIG

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post
        Buy SketchPlus
        Buy SUbD
        Buy WrapR
        Buy eBook
        Buy Modelur
        Buy Vertex Tools
        Buy SketchCuisine
        Buy FormFonts

        Advertisement