SimoneCRV
Guest
returning here, how exactly isetvalue3 is used?
jenuary
Guest
Try to read this discussion, maybe something good you pull out.
I unfortunately can't take tests in these days because I'm out.
Distance Mate Macro - DASSAULT: SOLIDWORKS 3D Design - Eng-Tips
I posted some quickie mate macros some time back for coincident, concentric, and parallel mates in thread559-175155. I'd been wanting to do a distance mate, but
SimoneCRV
Guest
I solved, thank you.Try to read this discussion, maybe something good you pull out.
I unfortunately can't take tests in these days because I'm out.Distance Mate Macro - DASSAULT: SOLIDWORKS 3D Design - Eng-Tips
I posted some quickie mate macros some time back for coincident, concentric, and parallel mates in thread559-175155. I'd been wanting to do a distance mate, butwww.eng-tips.com
SimoneCRV
Guest
Good morning,
I noticed a problem.
I can suspend a "feature" object with a
swfeat.setsuppression (swcomponentsuppressionstate_e.swcomponentsuppressed)
but at its reactivation,
swfeat.setsuppression (swcomponentsuppressionstate_e.swcomponentfullyresolved)
Nothing happens.
It turns out, but it doesn't turn on again.
where is the error?
I noticed a problem.
I can suspend a "feature" object with a
swfeat.setsuppression (swcomponentsuppressionstate_e.swcomponentsuppressed)
but at its reactivation,
swfeat.setsuppression (swcomponentsuppressionstate_e.swcomponentfullyresolved)
Nothing happens.
It turns out, but it doesn't turn on again.
where is the error?
SperX
Guest
Isn't that unsuppressed? I press that I have not understood the macro, I am not pro like you...ahaha
jenuary
Guest
I think you have to reactivate a feature while you're reactivating a component
( swcomponent(ii)
use method
setsuppression2 method (ifeature) because the other is obsolete since 2004
writing should be this:swfeat.setsuppression2(swfeaturesuppressionaction_e.swunsuppressfeature,swinconfigurationopts_e enumeration.swallconfiguration)
then decide in the second parameter on which configurations or all
|
SimoneCRV
Guest
This is true, but strangely to suspend it, does it also take swcomponent?
jenuary
Guest
Maybe some mistakes on the bees do it too... ; )
So it works now?
So it works now?
SimoneCRV
Guest
you work everything, I'm fixing the userform graphics, so much to do the chic things
SimoneCRV
Guest
Nooo, now I also have to pull out mass and volume of subparts?
jenuary
Guest
from that this is easy, volume and other properties of the part come out from the method
volume property (massproperty2)
volume property (massproperty2)
|
jenuary
Guest
find an example in bees
SimoneCRV
Guest
I hope you don't ask me anything else now. ?
SimoneCRV
Guest
instead it is more difficult than expected.
I don't know why, but it gives me the volume of all parts to the same configuration.
reiterating for the mass, always turns in the first configuration
SimoneCRV
Guest
posto per esempio, la parte del codice
dim swapp as sldworks.sldworks
dim swmodel as sldworks.modeldoc2
dim swassy as sldworks.assemblydoc
dim vmass as variant
dim volume as double
dim swcompbody as sldworks.body2
dim swcompmodel as sldworks.modeldoc2
set swapp = application.sldworks
set swmodel = swapp.activedoc
set swassy = swmodel
dim vcomp as variant
vcomp = swassy.getcomponents(false)
if not isempty(vcomp) then
dim i as integer
for i = 0 to ubound(vcomp)
set swcomp = vcomp(i)
dim modelc as assemblydoc
set modelc = swcomp.getmodeldoc2
dim vmodelc as variant
vmodelc = modelc.getcomponents(false)
dim modelcc as component2
dim h as integer
for h = 0 to ubound(vmodelc)
set modelcc = vmodelc(h)
set swcompbody = modelcc.getbody
set swcompmodel = modelcc.getmodeldoc
volume = swcompmodel.getuserpreferencedoublevalue(swmaterialpropertydensity)
vmass = swcompbody.getmassproperties(volume)
if modelcc.name2 = "nome" & userform1.combobox then
userform2.controls("valore1" & userform1.combobox).value = round(vmass(3), 2)
end if
if modelcc.name2 = "nome2" & userform1.combobox then
userform2.controls("valore2" & userform1.combobox).value = round(vmass(3), 2)
end if
next h
next i
end if
dim swapp as sldworks.sldworks
dim swmodel as sldworks.modeldoc2
dim swassy as sldworks.assemblydoc
dim vmass as variant
dim volume as double
dim swcompbody as sldworks.body2
dim swcompmodel as sldworks.modeldoc2
set swapp = application.sldworks
set swmodel = swapp.activedoc
set swassy = swmodel
dim vcomp as variant
vcomp = swassy.getcomponents(false)
if not isempty(vcomp) then
dim i as integer
for i = 0 to ubound(vcomp)
set swcomp = vcomp(i)
dim modelc as assemblydoc
set modelc = swcomp.getmodeldoc2
dim vmodelc as variant
vmodelc = modelc.getcomponents(false)
dim modelcc as component2
dim h as integer
for h = 0 to ubound(vmodelc)
set modelcc = vmodelc(h)
set swcompbody = modelcc.getbody
set swcompmodel = modelcc.getmodeldoc
volume = swcompmodel.getuserpreferencedoublevalue(swmaterialpropertydensity)
vmass = swcompbody.getmassproperties(volume)
if modelcc.name2 = "nome" & userform1.combobox then
userform2.controls("valore1" & userform1.combobox).value = round(vmass(3), 2)
end if
if modelcc.name2 = "nome2" & userform1.combobox then
userform2.controls("valore2" & userform1.combobox).value = round(vmass(3), 2)
end if
next h
next i
end if
SimoneCRV
Guest
in fact if I make a debug.print modelcc.referencedconfiguration, known that it always turns on the same configuration.
but it is usually the same engine I used to change the odds, turn off/light components and features.
I can't understand where I'm wrong.
but it is usually the same engine I used to change the odds, turn off/light components and features.
I can't understand where I'm wrong.
jenuary
Guest
in fact there is no possibility of obtaining mass properties for each configuration, this because the configuration is loaded and updated once you activate it.
I think you have to cycle all configurations by activating them one at a time and obtaining mass properties. at the end let the configuration you started before the cycle.
SimoneCRV
Guest
If it were to serve, I followed this example, properly modified then, to solve the problem. it is not necessary to cycle all configurations and at the end to activate the initial one.
the example then shows which enum I have to do to get the volume.
I got the volume, for every component I was going to cycle, considering that this last one, is already in the configuration I need.