Stats

  • Locked Locked
  • Replies 11
  • Subscribers 149
  • Views 19035
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Skill script for creating a selactable area

RFStuff

 Dear All,

For selecting an object we use "leSelBoxOrStretch()". This happens automatically if one does a left click on the mouse and releases it. The created virtual rectangular area selects the object inside it. This way it becomes difficult to accurately select the objects as the objects may not be accomodated in the zoomed area.

So what I actually want is as  follows:-

I will click ( left click in the mouse)  one point ( this will be let's say one corner of the rectangle), then I will go to other corner of the desired area and click the mouse and will fix the other diagonal corner of the rectangle. Then the objects which arefully coming inder this area will be selected.

Could anybody please tell, how it can be done.

Kind Regards,

 

 

Parents
  • Andrew Beckett

    In IC5141 bindkeys are not loaded by default, so they will be being loaded by a .cdsinit file. In IC5141, the .cdsinit file is not controlled by the "Cadence Search File" mechanism (aka "setup.loc") - even in IC61X it isn't unless you choose it to be by defining it as such in the csfLookupConfig file. So in IC5141 the mechanism is that it will look for a .cdsinit file in <ICinstDir>/tools/dfII/local, then the working dir, then the home dir. As soon as it finds a file, it will load it and stop. Frequently people add code in the .cdsinit file to continue looking elsewhere for files to load - so you'll have to see what logic has been applied in the .cdsinit file to find out where it looks.

    In IC615 onwards, bindkeys are loaded by default - but in that case they are loaded using the CSF mechanism, with it finding them by default (unless they exist elsewhere in the setup.loc search locations) in <ICinstDir>/share/cds/setup/dfII/bindkeys . Of course, you can still load them from the .cdsinit if you want - this was to avoid people having to load some bindkeys so that they got some out of the box.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    In IC5141 bindkeys are not loaded by default, so they will be being loaded by a .cdsinit file. In IC5141, the .cdsinit file is not controlled by the "Cadence Search File" mechanism (aka "setup.loc") - even in IC61X it isn't unless you choose it to be by defining it as such in the csfLookupConfig file. So in IC5141 the mechanism is that it will look for a .cdsinit file in <ICinstDir>/tools/dfII/local, then the working dir, then the home dir. As soon as it finds a file, it will load it and stop. Frequently people add code in the .cdsinit file to continue looking elsewhere for files to load - so you'll have to see what logic has been applied in the .cdsinit file to find out where it looks.

    In IC615 onwards, bindkeys are loaded by default - but in that case they are loaded using the CSF mechanism, with it finding them by default (unless they exist elsewhere in the setup.loc search locations) in <ICinstDir>/share/cds/setup/dfII/bindkeys . Of course, you can still load them from the .cdsinit if you want - this was to avoid people having to load some bindkeys so that they got some out of the box.

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.