Stats

  • Locked Locked
  • Replies 3
  • Subscribers 166
  • Views 14897
  • Members are here 0
More Content
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

PCB Designer: How to unlock read-only keyboard shortcuts for setting script shortcuts with the alias / funckey command

garypchambers

Having recently upgraded to 17.2 from 16.6 there now seems to be more read-only keyboard shortcuts. For example CTRL+Z (~Z), CTL+S (~S) etc... that were not readonly in 16.6

When trying to set these in 17.2 I get the response:   W- alias ~S is marked read-only, not changed.

This was not an issue with 16.6 and I would still like to use the same shortcuts I had setup previously. Is there a way to unlock this read only state in 17.7 for locked keyboard shortcuts?

Thanks

Parents
  • B Bruekers

    You can unset the protection with:

    alias_protect -n ~S

    alias_protect -n ~Z

    Somehow it does not work if you put these commands on the end of the ENV file, but putting it in the command prompt after start-up works fine (17.2.025).

    Edit:

    You can simply create a skill file which is loaded at startup. create a file, eg "unprotectAlias.il"

    Then add these lines in to the file:

    axlShellPost("alias_protect -n ~S")
    axlShellPost("alias_protect -n ~Z")

    Save the file and place it at a location where allegro.ilinit looks to load SKILL files at startup.

    Now when you start Allegro the ENV is loaded, then the SKILL files and when all is done the axlShellPost() command un-protects the 2 keys. The axlShell() does not work to un-protect during startup!

    Only remaining thing to do is to re-assign them to your wishes. Since you cannot do this before the protection is off you need to add 2 extra lines on the end of the same SKILL file, so it looks like this:

    axlShellPost("alias_protect -n ~S")
    axlShellPost("alias_protect -n ~Z")
    axlShellPost("alias ~S save_test")
    axlShellPost("alias ~Z undo_test")

    Now when you start Allegro your ~S and ~Z keys are redefined to save_test and undo_test (as example!).

Reply
  • B Bruekers

    You can unset the protection with:

    alias_protect -n ~S

    alias_protect -n ~Z

    Somehow it does not work if you put these commands on the end of the ENV file, but putting it in the command prompt after start-up works fine (17.2.025).

    Edit:

    You can simply create a skill file which is loaded at startup. create a file, eg "unprotectAlias.il"

    Then add these lines in to the file:

    axlShellPost("alias_protect -n ~S")
    axlShellPost("alias_protect -n ~Z")

    Save the file and place it at a location where allegro.ilinit looks to load SKILL files at startup.

    Now when you start Allegro the ENV is loaded, then the SKILL files and when all is done the axlShellPost() command un-protects the 2 keys. The axlShell() does not work to un-protect during startup!

    Only remaining thing to do is to re-assign them to your wishes. Since you cannot do this before the protection is off you need to add 2 extra lines on the end of the same SKILL file, so it looks like this:

    axlShellPost("alias_protect -n ~S")
    axlShellPost("alias_protect -n ~Z")
    axlShellPost("alias ~S save_test")
    axlShellPost("alias ~Z undo_test")

    Now when you start Allegro your ~S and ~Z keys are redefined to save_test and undo_test (as example!).

Children
No Data
Cadence Guidelines

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.