Announcement

Collapse
No announcement yet.

Awesome find in Dynamo, by John Pierson (60secondrevit): Crops and section boxes

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Awesome find in Dynamo, by John Pierson (60secondrevit): Crops and section boxes

    John Pierson found a great correlation between views, and their crop regions, and section boxes, while working in Dynamo the other day.

    He discovered that if you are looking at an Elevation View, its Crop Region element is the Element ID of the view, minus 1.

    So if the view is 55555555, the crop region is 55555554.

    In 3D views, the section box is one below the views element ID, and the crop region is 2 below.

    So if the views element ID is 66666666, the section box is 66666665, and the crop region is 66666664.

    That makes it pretty handy for doing things with section boxes and crop regions, since you can select them directly by element ID.
    Attached Files
    Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
    @Web | @Twitter | @LinkedIn | @Email
    Tags: None
    #2
    Is this pre or post Tweet?

    (I've been playing as well) - any insight into what were you/John imagining for such a discovery? Thinking maybe tying section box to an element boundary box for isolating elements in view?

    Comment

      #3
      If you want to get a Bounding Box of a Section Box on a 3D view (for instance), you need to select both the Section Box and the View, to put them in to the BoundingBox.ByElement node you see in the graph. Section Boxes dont have other properties, to really ask "what view am i in?" So without the nifty workaround, you have to do something like this (attached) to both the view, and the section box,(Collect the list of section boxes, and the list of views) then compare the results, and then sift the results out of the Filtered List, which is just a bunch more steps.

      Its just a heck of a lot simpler.

      (EDIT: Its post tweet. I just was excited about his find, so i thought i would share it here after he tweeted about it)
      Attached Files
      Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
      @Web | @Twitter | @LinkedIn | @Email

      Comment

        #4
        Good to know!
        Might be useful to test if it is always consistent or if you can break it. Eg. if you Crop/Uncrop or make custom crop regions will it ever produce a new ID.
        (Its the exceptions to the rule that screw up a good program)
        "One must imagine Sisyphus happy." Albert Camus - "The innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may ​do well under the new." Nicolo Machiavelli -"Things that are too complex are not useful, Things that are useful are simple." Mikhail Kalashnikov

        Comment

          #5
          This is great!

          Did you find any correlation between viewport and crop region also for floor plans??

          Andrea

          Comment

            #6
            Originally posted by snowyweston View Post
            Is this pre or post Tweet?

            (I've been playing as well) - any insight into what were you/John imagining for such a discovery? Thinking maybe tying section box to an element boundary box for isolating elements in view?
            Just saw this thread! Originally I discovered this for obtaining the crop region from interior elevation views to override them to be bolder. Aaron needed it and it seemed to work for 3d as well, so I shared it with the world finally.

            John Pierson
            Creator of Rhythm, Monocle, Bang! and Lots of Other Okay Stuff.
            Twitter - @60secondrevit | Email - [email protected] | Work - parallaxteam.com | Blog - designtechunraveled.com | 🔗- bio.link/johnpierson

            Comment

              #7
              Andrea, the floor plan are a bit more tough to figure out. Unlike the other view types, the floor plan alternates between -1 and +3 of the view. Could probably build in logic that checks for this though.
              :thumbsup:
              John Pierson
              Creator of Rhythm, Monocle, Bang! and Lots of Other Okay Stuff.
              Twitter - @60secondrevit | Email - [email protected] | Work - parallaxteam.com | Blog - designtechunraveled.com | 🔗- bio.link/johnpierson

              Comment

                #8
                This is like the "text door neighbor" thing https://www.reddit.com/r/textdoor/

                ----------
                That he is mad, ’tis true. Tis true, ’tis pity,
                And pity ’tis ’tis true

                Comment

                  #9
                  Originally posted by Twiceroadsfool View Post
                  If you want to get a Bounding Box of a Section Box on a 3D view (for instance), you need to select both the Section Box and the View, to put them in to the BoundingBox.ByElement
                  I am trying to recreate this but I can only find BoundingBox.ByElements from ClockworkforDynamo..
                  can you point me in the right direction for this node? Or may post a file where you get a bounding box from a 3D view and a section box?

                  Comment

                  Previous template Next

                  Related Topics

                  Collapse

                  Monumetric Footer In-screen

                  Collapse
                  Working...
                  X