Comments
-
Greg Hurrell
Thanks for the report, Chris. At the moment I don't have access to one of these new keyboards so I can't do any local testing to figure out what's going wrong, but there are a few possibilities.
It could be a hardware thing: those keys could be treated as special keys now and send different key codes...
Or a software thing: Leopard might be reserving different keys for things like brightness adjustments (intercepting those key events at the OS level and not letting them filter through to applications).
Finally it might be a configuration thing: perhaps Leopard has some default assignments for those keys that mean they're already "taken".
See bug #206 for a similar issue that was reported a while ago; there may be some information that helps you in there:
https://wincent.dev/a/support/bugs/show_bug.cgi?id=206
Let me know how you go. If you can't get to the bottom of this based on this information or the info in bug #206 then this might have to sit on the backburner until I get my hands on a new keyboard and can investigate the issue.
-
Chris Drackett
I actually just found out that this is a display bug only. (F16-F19 will not display in the window, but the keys WILL work) I accidentally had synergy off (just installed) when I submitted this bug. So its a little less severe, just confusing.
-
Greg Hurrell
Ah ok, thanks for the clarification.
Yes, there is a long standing bug which causes some key combinations to be misdisplayed. I was never able to find out why and I ended up writing a completely new hot key engine from scratch for Synergy Advance which doesn't have any display issues.
There really needs to be a bug for this in the database so I'm going to commandeer this one and change the summary to reflect the real nature of the problem.
Add a comment
Comments are now closed for this issue.