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

    [Plugin] Explode2Groups

    Scheduled Pinned Locked Moved Plugins
    26 Posts 11 Posters 15.5k Views 11 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.
    • designerbursaD Offline
      designerbursa
      last edited by

      @unknownuser said:

      It's easy to do...
      At the end of the part that make a group out of some entities you add something like -
      compoi = group.to_component
      You can then choose to use methods like compod=compoi.definition; compod.name="Compo#1" to rename the definition as desired.

      But if this relates to the parallel question once you have all exploded entities, still selected, there is a right-click > context-menu native-item "Make Component...", which makes the Selection into a Component rather than into a Group like with "Make Group" - the resultant dialog lets you name the component etc...

      If you already have a Group then the context-menu item "Make Component..." can also make that selected Group into a Component etc...

      This is very hard for amateurs like me 😄

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

        The native methods are available to all - with no need for coding skills...

        To simply edit ../Plugins/Explode2groups.rb to finally make components rather than groups...
        Edit that RB file using a plain-text editor [e.g. Notepad++ on PC, or TextWrangler on MAC]
        Find line #43
        all.each{|a| aents.add_group(a) }
        Change it to read
        all.each{|a| **gp=**aents.add_group(a)**;ci=gp.to_component;ci.definition.name="Compo#1"** }
        The default component's name - Compo#1 - increments for each new definition...

        TIG

        1 Reply Last reply Reply Quote 0
        • jujuJ Offline
          juju
          last edited by

          at "designerbursa"

          There are some paid extensions you might want to take a look at as well:

          • nz_ConvertMe
          • nz_EasyGroups

          Save the Earth, it's the only planet with chocolate.

          1 Reply Last reply Reply Quote 0
          • designerbursaD Offline
            designerbursa
            last edited by

            @tig said:

            The native methods are available to all - with no need for coding skills...

            To simply edit ../Plugins/Explode2groups.rb to finally make components rather than groups...
            Edit that RB file using a plain-text editor [e.g. Notepad++ on PC, or TextWrangler on MAC]
            Find line #43
            all.each{|a| aents.add_group(a) }
            Change it to read
            all.each{|a| **gp=**aents.add_group(a)**;ci=gp.to_component;ci.definition.name="Compo#1"** }
            The default component's name - Compo#1 - increments for each new definition...

            I tried, it works. But you misunderstood me. I want the components to use the same process. to separate nested components. or is there such a plugin? easy and simple plugin! ..

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

              If you explode a group [or component-instance] which contains nested groups or component-instances then these are then made separated things. Any geometry is then loose. Explode2Groups takes the loose geometry and regroups it depending on 'connected-ness', the other nested objects are then in the selected group's 'parent' context.

              After using the tool you can use the Outliner to select any of these...

              Another way to achieve your goal would be to use the Outliner, and within it select the nested instances and drag them, still within the Outliner, into another context other than their 'parent' - they will then 'move' into that context...

              TIG

              1 Reply Last reply Reply Quote 0
              • designerbursaD Offline
                designerbursa
                last edited by

                Thank you TIG

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

                Advertisement