Jump to content


Unable to assign single function keys for shortcuts


1 reply to this topic

#1 walloon

    Member

  • Members
  • PipPip
  • 24 posts
  • Location:Los Angeles

Posted 10 June 2010 - 03:44 PM

For years -- including through SCX 10.3.4 -- I have assigned "Lookup" and "Check Selected" to my keyboards F11 and F12 keys respectively in the Preferences/Shortcuts. For no apparent reason, I am rnow refused with error message: "SORRY, THE KEY COMBINATION F11 CAN NOT BE USED AS A SHORTCUT. PLEASE CHOOSE A DIFFERENT SHORT CUT". Putting aside the fact there is no "combinaton" -- it's one key stroke --If I append it with the command key, for example, it takes. But I always liked just have a single key to punch.

I'm on Mac, OS10.6.3. And yes, I've made sure the system preferences/keyboard does not conflict with any default keyboard assignments.

If it appeared at first try, it would be understandable. But it's always permitted this, but now doesn't.
thanks for the help.

#2 Evan Gross

    Administrator

  • Admin
  • PipPipPip
  • 2,986 posts
  • Gender:Male
  • Location:Toronto, Canada
  • Interests:This Place!

Posted 10 June 2010 - 04:52 PM

View Postwalloon, on 10 June 2010 - 03:44 PM, said:

For years -- including through SCX 10.3.4 -- I have assigned "Lookup" and "Check Selected" to my keyboards F11 and F12 keys respectively in the Preferences/Shortcuts. For no apparent reason, I am rnow refused with error message: "SORRY, THE KEY COMBINATION F11 CAN NOT BE USED AS A SHORTCUT. PLEASE CHOOSE A DIFFERENT SHORT CUT". Putting aside the fact there is no "combinaton" -- it's one key stroke --If I append it with the command key, for example, it takes. But I always liked just have a single key to punch.

I'm on Mac, OS10.6.3. And yes, I've made sure the system preferences/keyboard does not conflict with any default keyboard assignments.

If it appeared at first try, it would be understandable. But it's always permitted this, but now doesn't.
thanks for the help.
Yeah, looks like this got broken. Seeing as I have to do a quick 10.3.6 update (to work around the crash with the version of WebKit installed with Safari 5.0), I'll roll in a fix for this problem as well.

Thanks for the report - awfully good timing all things considered!