2012 Frame Generator - G_L Parameter won't update

[Justin.Williams]

There seems to be a bug with the frame generator in 2012. When using the frame generator, the G_L parameter in each part should always update based on the line that it is attached to from the skeleton. Well in 2012, the frame member's length will update (the B_L parameter updates), but the G_L parameter will no longer update, it stays at its original value from when it was first placed.

Has anyone else had this problem?

I've attached the file as an example. The Height of the skeleton was originally 121.370 in, and now it is 82 in. The parameter for the outside vertical legs will not update from 121.370 in to 82 in. I've tested this a few times with the same results.

[bobvdd]

While adding code to incorporate the length in the partnumber, I somehow dropped the most important line of all, actually the line that set the G_L value to the reference parameter 😞

' Assign the FIRST non-renamed reference parameter to G_L
oparam.Expression = oparams.ReferenceParameters.Item(iref).Name

I still don't know how I managed to do this but it happened.

I will also upload this newer version to the blog but for the time being please use the correct version here attached to the newsgroup post..

Thanks for persisting with me on this one.

Bob

[kdlklm]

I am receiving an error message, that goes as follows

Runtime error 16
Expression too complex

The error occurs on the following line.

            height = oCompOcc.Definition.RangeBox.MaxPoint.Z - oCompOcc.Definition.RangeBox.MinPoint.Z

[bobvdd]

You can safely remove that line. I am not using the height parameter.

But I would still like to find the cause of the error.

Can you send me a small data set or the ipt where it is failing on?

Txs

Bob

[kdlklm]

this should be the file you're looking for.

[admin]

Bob we are getting this on only 1 of our computers (out of 3) and it is running 32bit Windows XP, the other 2 that don't get the error are both 64bit Windows 7, hopefully that helps?

[bobvdd]

Thanks Adam for pointing me in the right direction.

There is indeed something funky going on with subtracting Doubles on 32 bit machines in VBA.
No wonder that I did not see the problem as I am working on a 64 bit machine.

You can avoid the run-time error If you replace the line

           height = oCompOcc.Definition.RangeBox.MaxPoint.Z - oCompOcc.Definition.RangeBox.MinPoint.Z

with

            Dim maxz As Double

            Dim minz As Double

            maxz = oCompOcc.Definition.RangeBox.MaxPoint.Z

            minz = oCompOcc.Definition.RangeBox.MinPoint.Z

            height = maxz – minz

I have updated both blog posts with the correct code now:

http://beinginventive.typepad.com/being-inventive/2011/06/double-mitered-frames-report-the-wrong-fra...

http://beinginventive.typepad.com/being-inventive/2011/06/length-parameter-of-frame-generator-beams-...

Bob