Try to stretch a locked A, and it jumps along B

[Ignacio Azpiazu]

I've seen this before in a Graphisoft part and now it is happening to an object I'm writing, and I can't figure out what the cause is: in 2D I have two dumb (black) hotspots only, in 0,0 and widcab,0 (widcab is equal to A). A is locked, and widcab is given by the parameter settings.

If I grab the object from a hotspot I still get the 'Stretch' option in the context menu, and if I try to stretch it won't stretch (which is good) but the object will jump along B by a given dimension.

Anybody seen this before?

[Anonymous]

If you are locking out the A & B values they should really be locked and not equal to another value that is stretchy. If there are any two hotspots at A along one axis and/or B along the other AC will use them (or try to) to adjust those values. This can have unintended consequences. In general it is best to either use the AB values or disable them altogether.

[Barry Kelly]

Ignacio wrote:
I've seen this before in a Graphisoft part and now it is happening to an object I'm writing, and I can't figure out what the cause is: in 2D I have two dumb (black) hotspots only, in 0,0 and widcab,0 (widcab is equal to A). A is locked, and widcab is given by the parameter settings.

If I grab the object from a hotspot I still get the 'Stretch' option in the context menu, and if I try to stretch it won't stretch (which is good) but the object will jump along B by a given dimension.

Anybody seen this before?

We've had this problem with locked A & B values.
The trick is to unlock them and hide them ("X" button) if you don't want the user to use them.

Then the object should stretch as expected.

Barry.

[Frank Beister]

You can do this context sensitive too:

IF GLOB_CONTEXT=5 then
LOCK "A"
HIDEPARAMETER "A"
ENDIF

[Ignacio Azpiazu]

Thanks guys. It felt miserable for a couple of hours.