You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #41: F14/F15/F16 can't be used without modifiers

Kind bug
Product Synergy
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

From a user email: "Here's the problem, I have three keys F14, F15, and F16 that would be just perfect for previous, play/pause, and next considering that they are seperated from the rest of the function keys. However, Synergy will not assign a function to theses F keys without a modifier... please, please help! F.Y.I the keybord I'm using is the relatively new White Apple Keyboard."

For what it's worth, I am sitting in front of one of those keyboards right now (the Apple wireless one) and F14 an F15 are pre-bound to control the display brightness. In other words, the operating system intercepts those keystrokes and they are not passed on to any application. At least on this system, it looks like F16 is allowed through. If you test this with another application (for example, I just tested this in Xcode), you'll notice that exactly the same thing happens: hit F14 or F15 and the brightness changes, and you can't bind without a modifier.

I've got completely new hot key code in place for Synergy Advance (and all future products), but I can't test what it does with respect to F14-F16 at this moment because I'm right in the middle of some big changes which mean it is in an buildable state. Once I've got it building again I'll test it and see what it does.

Comments

  1. Greg Hurrell

    Marking as ASSIGNED.

  2. Greg Hurrell

    Okay, so I've finished that horrible refactoring work and the code is building again. I've tested the new hot key code on this key board. As I suspected, F14 and F16 are definitely trapped by the operating system and never get passed on to any app unless there is a modifier key held down.

    And coinciding with my experiments above with Xcode, F16 is allowed through on this machine and correctly captured by the new hot key code.

    So it looks like the resolution to this bug lies in the hands of Apple. I suggest you file an enhancement request with them, allowing the user to turn off the use of those keys for brightness.

    http://www.apple.com/macosx/feedback/

    I'm marking this bug as WORKSFORME seeing as the internal builds have working code. You'll see this in a public version soon, I hope, depending on how quick I can get it out.

  3. Greg Hurrell

    Marking as CLOSED.

  4. Greg Hurrell

    Sigh, a minor correction to what I typed above: F14 and *F15* are intercepted, F16 is let through.

  5. Greg Hurrell
    • ** Bug 93 has been marked as a duplicate of this bug. ***
Add a comment

Comments are now closed for this issue.

Menu