• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. <DrawThru3> EF -- First function is deactivated after this...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 2560
  • 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

<DrawThru3> EF -- First function is deactivated after this call.

MikeRVT
MikeRVT over 12 years ago

Hello Gents/Ladies.

I hope someone can identify my problem.

When I execute a move command on an object in the schematic, I like to rotate the object using the right click button.  However, sometimes during the right click I move the mouse and thus execute the DrawThru3 function instead of the rotate.

 To fix this I overrode the DrawThru3 function as shown below.  However, once the rotate is done during a DrawThru3 execution, the move command is no longer active.  For some reason when the DrawThru3 extended function is executed the original function seems to be disabled.  Any idea how I can prevent this behavior?

hiSetBindKeys( "Schematics" list(

list("<DrawThru3> EF"   "schSetEnv(\"rotate\" t)") 

)) 

Thanks,

-- Mike 

 

  • Cancel
Parents
  • dmay
    dmay over 12 years ago
    There is actually an "Enter function" threshold in 6.1.5. For each mouse button, you can set the distance traveled (in some arbitrary number unit) before the movement is considered a drag. Cadence defaults are 500, 10, 10 (m1, m2, m3). The smaller the number, the more likely you'll zoom by accident.

    hiGetEFDrawThruDelta() by default returns (500 10 10). This means the min drag dist with mouse1

    pressed during an EF (enter function), will be 500 (not sure what unit) before it is considered a drawThru bindkey.

    For mouse2 and mouse3 it is only 10 which can be annoying. Try setting these to 200 or higher.

    hiSetEFDrawThruDelta(200 2)

    hiSetEFDrawThruDelta(200 3)


    Derek
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 12 years ago
    There is actually an "Enter function" threshold in 6.1.5. For each mouse button, you can set the distance traveled (in some arbitrary number unit) before the movement is considered a drag. Cadence defaults are 500, 10, 10 (m1, m2, m3). The smaller the number, the more likely you'll zoom by accident.

    hiGetEFDrawThruDelta() by default returns (500 10 10). This means the min drag dist with mouse1

    pressed during an EF (enter function), will be 500 (not sure what unit) before it is considered a drawThru bindkey.

    For mouse2 and mouse3 it is only 10 which can be annoying. Try setting these to 200 or higher.

    hiSetEFDrawThruDelta(200 2)

    hiSetEFDrawThruDelta(200 3)


    Derek
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information