Toolbox: Using the "Is toolbox" property

Hello, we don't use the toolbox for many reasons that have been mentioned on this forum! However, I used it to create my base of standard parts (screws for the most part). Once the parts have been saved in a new directory, it keeps the "Is toolbox" property (small screw icon in the tree). No problem so far! Everything works without worries.

The practical side I found in keeping this property is that when copying a model assembly (take-home comp), all the "Toolbox" parts are by default non-visible and unchecked (which is good I don't want to copy them!). I then pushed this property to other standard parts to benefit from that "little extra"!

My question (yes finally I'll get to it): Are there any contraindications to using this "Is toolbox" property in this way?

I discovered in particular that the blocking bar could not be used on this type of component (maybe it is blocked by default?)

Thank you

Hello

There's a little piece of software hidden in c>Solidworks that removes the toolbox logo but keeps everything else. It is called "sldsefocprop.exe". If you use it, you can use the blocking bar.

3 Likes

As a limitation: the "configure component" function does not work on toolbox parts

1 Like

Ac cobra @ thank you for the reminder of the little hidden software!

Pascal @ Well done I had forgotten this limitation, by the way if you configure another component you can add a Toolbox component in the configuration modification window by double-clicking on it in the tree!

it is said not to use the toolbox for large designs among others

see this superb tutorial for the management of large assemblies in SolidWorks

http://www.lynkoa.com/tutos/import-export-formats-neutres/gestion-de-gros-assemblage-2

@+ ;-)

3 Likes

Gt22@ interesting tutorial! The pure and hard use of the Toolbox I understand that it weighs down the designs, but does using this "Is toolbox" property overload the components a little bit or is it a simple property? mystery!

1 Like

I'll be you for a test

I'll try to apply to her the info given on the tutorial

to see if it helps or not

and + to be able to make a synthesis of the gains brought

and I think you'll be pleasantly surprised

It is also said to avoid the configue and especially the derivative configue

and one piece one part for large design

so for the libraries to manage differently ;-)

SW help (toolbox/ smart function etc....)

are not always optimized for large designs

but super great for small assemblies

@+ ;-)

3 Likes

That's why I don't use toolbox components anymore, well I take them like you to enrich our library and then I use the software that removes the toolbox logo so it's a standard part and I'm not bothered with the disadvantages but that the advantages...

1 Like

Using the "Is toolbox" property on any Sw file (asm / prt):

Limitations:

-No blocking bar

-"Configure component" function not available by right-clicking on the part (possibility to configure it anyway, see post below).

Advantage(s):

-Non-visible and uncopied part during a default take-home comp.

The choice is yours!

Using the "Is toolbox" property on any Sw file (asm / prt):

Limitations:

-No blocking bar

-"Configure component" function not available by right-clicking on the part (possibility to configure it anyway, see post below).

Advantage(s):

-Non-visible and uncopied part during a default take-home comp.

The choice is yours!