Resizing cabinets with FredoScale
-
Are you trying to stretch all three drawers at the same time? Are you using Box Stretching? That works for me.
-
I tried also with all drawers a the same time.
Stretching works for red and green axes direction, but doesn't work in Z direction.
Only the mid drawer is resized.
Acting on each drawer separately then it works.
Any idea Dave why it doesn't work in Z ? -
Well, think about what Box Stretching is doing. It takes the end components in the nest and moves them while it stretches those in the middle. It seems to me it is doing exactly the same thing in all three directions correctly. It may not do the wanted thing but it is doing what it was designed to do.
-
Ah yes, you're correct Dave.
-
Dave, thanks, yes I am using box stretching and showing the position of the divider [as available from the local menu] and moving the divider to an appropriate position for the stretch to happen which I inferenced to a pre-prepared line for an accurate position.
No, I was not trying to stretch all 3 drawers at a time to adjust height [though I would for width or depth] but I was originally additionally trying to stretch the drawer face fronts [not shown here] so trying to stretch as much of the cabinet at once [Carcass group, drawerboxes group and drawerfronts group] with as few actions as possible rather than going into each group to activate Fredoscale, and mostly it worked except for the top drawer which is why I have broken it down to just the drawerboxes to test where it fails at the minimum level. It would appear though that there are irratic limitations when using Fredoscale with group hierarchy, and it works most reliably when all components being scaled are within the same group, and even that is not bullet-proof. I am certain that my computer is easily up to the job so that wouldn't be the issue.
-
@dave r said:
Well, think about what Box Stretching is doing. It takes the end components in the nest and moves them while it stretches those in the middle. It seems to me it is doing exactly the same thing in all three directions correctly. It may not do the wanted thing but it is doing what it was designed to do.
Dave, please see the post I just made, as I had raised the divider for stretching, the upper drawer should stretch.
-
I don't know. The only weird thing I see when I try to resize just the top drawer vertically with Box Stretcher after selecting all of it including the drawer guides is the drawer guides get resized, too. That doesn't happen with the middle or lower drawer though. The drawer box gets resized just fine though.
I guess I wouldn't make a group of the entire set of drawers. Instead I would make a nested component of each drawer box sans drawer guides.
If you have to do much of this, though, especially with different drawer front options, it seems to me that you shouldn't be wasting time on this and instead make a dynamic drawer component.
-
@bucksbedrooms said:
@dave r said:
Well, think about what Box Stretching is doing. It takes the end components in the nest and moves them while it stretches those in the middle. It seems to me it is doing exactly the same thing in all three directions correctly. It may not do the wanted thing but it is doing what it was designed to do.
Dave, please see the post I just made, as I had raised the divider for stretching, the upper drawer should stretch.
I was explaining to Jean-Franco why he was getting the results he got.
-
@dave r said:
I don't know. The only weird thing I see when I try to resize just the top drawer vertically with Box Stretcher after selecting all of it including the drawer guides is the drawer guides get resized, too. That doesn't happen with the middle or lower drawer though. The drawer box gets resized just fine though.
I guess I wouldn't make a group of the entire set of drawers. Instead I would make a nested component of each drawer box sans drawer guides.
If you have to do much of this, though, especially with different drawer front options, it seems to me that you shouldn't be wasting time on this and instead make a dynamic drawer component.
Thanks Dave, I am fairly new to sketchup which is why I am starting off using Fredo Scale for resizing, as have very limited time to get current job completed before getting involved with dynamic components once I have more time available to look into it. The runners shouldn't stretch if the dividing line is high enough, though as I have been saying, behaviour seems a little irratic. As I will be using Cutlist Bridge plugin by Joe Zeh aka Chief Woodworker and he advises against nested components, that is why I have been nesting components in groups instead, and it does seem a cleaner method, which avoids 'strange happenings' like duplicates and changes to components in a complex model, but I guess each user has their own convention discipline [early in the day for me as a new user, but getting the idea not to group too deeply].
-
Well, maybe Joe has some ideas for you regarding organizing your model. Having the drawers nested as you have them in your example doesn't make a lot of sense to me and would very much complicate my workflow.
-
@dave r said:
Well, maybe Joe has some ideas for you regarding organizing your model. Having the drawers nested as you have them in your example doesn't make a lot of sense to me and would very much complicate my workflow.
Does any one know where there is some 'Best Practice' for woodworkers regarding workflow organisation of components, groups and layers which is well regarded generally or is this a subject likely to cause too much difference of opinion?
-
I think you'll get a lot of differences of opinions.
I've been drawing with SketchUp for almost 10 years and never once found a case where a group made more sense for me than a component so I don't use groups--ever. Joe seems to like them, though. Some folks hink it makes sense to make groups of parts when there is only one of those parts in the model and they'll make components only when there's more than one. Or they like to make groups until they need them to be components. When I'm creating a model for a plan, there will absolutely always be more than one of every part. Since I only use components, there is never a time when I look at something and wonder if it is a component or a group.
Joe prefers to show models in isometric views while I use perspective views except for the 2D views I create. Some people put each part on its own layer and make scenes for only one part. I make layers for assemblies and often show more than one part in a single scene. Some folks prefer to do dimensioning in SketchUp while others, including me, do all and other text dimensioning in LayOut.
I think you have to work out what works best for you. My process works well for me and I find it extremely logical and fast.
-
@dave r said:
I think you'll get a lot of differences of opinions.
I've been drawing with SketchUp for almost 10 years and never once found a case where a group made more sense for me than a component so I don't use groups--ever. Joe seems to like them, though. Some folks hink it makes sense to make groups of parts when there is only one of those parts in the model and they'll make components only when there's more than one. Or they like to make groups until they need them to be components. When I'm creating a model for a plan, there will absolutely always be more than one of every part. Since I only use components, there is never a time when I look at something and wonder if it is a component or a group.
Joe prefers to show models in isometric views while I use perspective views except for the 2D views I create. Some people put each part on its own layer and make scenes for only one part. I make layers for assemblies and often show more than one part in a single scene. Some folks prefer to do dimensioning in SketchUp while others, including me, do all and other text dimensioning in LayOut.
I think you have to work out what works best for you. My process works well for me and I find it extremely logical and fast.
Thank you Dave for your view on this, which is helpful as it would be good if I can lay a sound foundation at this stage so I don't have to alter everything again in the future. So far my poor experience seems to be related to groups so maybe I should give your method of avoiding them a chance and use some sort of prefix system for components which contain other components, which should help the cutlist situation. I also see the advantages of perspective views, like yourself. Layers for assemblies sounds good too. Thanks again for taking the time to advise.
-
glad if my babbling is helpful.
FWIW, I also tend to minimize nesting as much as possible it generally makes it more complex to edit the model and it is easy to get nests screwed up. also make sure you have a clear understanding of layers and only make layer associations for components/groups. Leave Layer 0 active at all time, draw everything on Layer 0 and make sure edges and faces always remain on Layer 0.
-
@dave r said:
glad if my babbling is helpful.
FWIW, I also tend to minimize nesting as much as possible it generally makes it more complex to edit the model and it is easy to get nests screwed up. also make sure you have a clear understanding of layers and only make layer associations for components/groups. Leave Layer 0 active at all time, draw everything on Layer 0 and make sure edges and faces always remain on Layer 0.
Thanks Dave.
So far, Fredoscale seems to be behaving while avoiding groups.
Advertisement