• 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. ADEXL: How to get parameters of "_" functions for bindkey...

Stats

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

ADEXL: How to get parameters of "_" functions for bindkey usage?

dontpanic
dontpanic over 7 years ago

Hi! I'm trying to define some ADE-XL bindkeys for actions that I use really often, like the following:

; Open run log (history window)
hiSetBindKey("adexl" "Ctrl Alt Shift<Key>L" "_axlDataViewOpenRunLogAction(axlDataViewForm0->axlDataViewWidget0)")
; Open run results (history window)
hiSetBindKey("adexl" "Ctrl Alt Shift<Key>V" "_axlDataViewShowResultsAction(axlDataViewForm0->axlDataViewWidget0)")
; Export results to csv file
hiSetBindKey("adexl" "Ctrl Shift<Key>S" "_axlExportResultsView(axlOutputsForm3->axlOutputsWidget3)")

I usually get those code snippets from spying on the CIW log to see what gets called when I do these actions using the mouse, and often these "_" functions are involved which seem to be undocumented, private functions.

The problem is that this spying method always gives me arguments that are "hardcoded" to the current application instance, session etc, and when these parameters change, my bindkeys break. For instance sometimes instead of "axlOutputsForm3" I should use "axlOutputsForm4" and so on. Is there any function I can call to pass the correct arguments to these "_" functions?

Thanks and regards,
Jorge.


  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Hi Jorge,

    No. The _ at the beginning is an indication that these are private functions, and they're not intended to be used this way - as a result, there's no support for getting hold of the appropriate argument values for these functions procedurally.

    I don't think there's a public API to open the run log. There is to view the results axlViewHistoryResult, and axlExportOutputView to export the results to a file. In the case of axlViewHistoryResult, you'd have to get the handle for that specific history entry, so you'd probably end up writing some code that displayed a choice of the available histories and then picked the one you want. However, this is likely to be more key clicks than just using the right mouse button menu in the first place...

    Note you could always use right click and then O to open the log or right click and then V to view the results - i.e. using the built-in accelerators...

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 7 years ago in reply to Andrew Beckett

    OK Andrew, thanks for the explanation!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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