bindkey to move selected object

Hi ManChak

You can try with hiReplayFile and put all the commands related to form like invoking the form, entering x and y fields and pressing ok or apply in the form.

Having said the above, your way for moving objects is not my favorite.

• I have created a toolbar with direction buttons and delta XY entries.
• Or you may use non HI procedures like leMoveFig or leMoveObject
• Or Instead of move function you can try with Stretch. Advantage with stretch is that if a object is fully selected, it moves else it stretches.
• Or You may use cadence's dx and dy by pressing TAB button

Thanks

Ramakrishnan

I agree with Ramakrishnan. Something like:

procedure(MyMoveSelected(deltax deltay)
  let((xform)
    xform=list(deltax:deltay "R0" 1)
    foreach(obj geGetSelSet()
      dbMoveFig(obj nil xform)
    )
  )
)

The above is untested, but it would be something like that to move all the selected objects.

Regards,

Andrew.

Hi Andrew and Ramakrishnan,

Thank you for your suggestions. I modified Andrew 's code "dbMoveFig(obj nil xform)". It works well now. (Moderator note: corrected Andrew's original code to add the missing argument)

Thanks,

ManChak

What is the purpose of this syntax  " le0MoveForm"    I tried searching in API finder but Im not able to find.
Please can explain exactly what does this line do 

mctang said:

le0MoveForm->moveXField->value=deltx

    le0MoveForm->moveYField->value=delty

Well, as described in the thread above, this is not a terribly good way of doing it because it depends on the interactive forms having been run. What has happened here is that the original poster will have used the interactive move command in the layout editor, and typed in values on fields on the form - and then captured the commands in the CDS.log (and the CIW if the log filter settings are set appropriately) which record how the form was filled in. In general we don't document those - they're there to enable replay of the log file in the same conditions. In this case the form has a number as part of it - I think (if I remember rightly) this is because we keep the form unique for different technologies (may be for different windows - I didn't check). 

Anyway, the point is that this is precisely why you don't want to be using this approach to do your automation, as it relies on both undocumented behaviour, and also potentially the form name may change depending on what you've done before. Hence the suggestion to use the dbMoveFig approach.