|
2016-08-14
| ||
| 20:49 | • Closed ticket [3588936fff]: tkUnixKey.c is wrong for me since 8.5.11 plus 9 other changes artifact: c1c0b86cd9 user: fvogel | |
|
2013-02-21
| ||
| 12:43 | • Ticket [3588936fff]: 4 changes artifact: 8383253143 user: anonymous | |
|
2013-01-03
| ||
| 19:35 | • Ticket [3588936fff]: 4 changes artifact: 4587a3f2a8 user: cjmcdonald | |
|
2012-11-29
| ||
| 22:18 | • Ticket [3588936fff]: 4 changes artifact: 38516af8b4 user: wordtech | |
| 20:58 | • Ticket [3588936fff]: 4 changes artifact: 54daa1a965 user: anonymous | |
| 20:54 | • Ticket [3588936fff]: 4 changes artifact: fc9ac7181d user: dkf | |
| 20:40 | • Ticket [3588936fff]: 4 changes artifact: 9d0eb13592 user: anonymous | |
| 16:21 | • Ticket [3588936fff]: 4 changes artifact: 7307e6672d user: dkf | |
| 15:46 | • Ticket [3588936fff]: 4 changes artifact: f9c683a517 user: anonymous | |
|
2012-11-26
| ||
| 21:50 | • Ticket [3588936fff]: 4 changes artifact: 58db5abbd1 user: wordtech | |
| 20:50 | • Ticket [3588936fff]: 2 changes artifact: 44cafdfb23 user: dgp | |
|
2012-11-21
| ||
| 14:18 | • New ticket [3588936fff]. artifact: 454b422e48 user: anonymous | |
| Ticket UUID: | 3588936 | |||
| Title: | tkUnixKey.c is wrong for me since 8.5.11 | |||
| Type: | Bug | Version: | obsolete: 8.5.13 | |
| Submitter: | Created on: | 2012-11-21 14:18:12 | ||
| Subsystem: | 32. Key Symbols | Assigned To: | fvogel | |
| Priority: | 5 Medium | Severity: | Minor | |
| Status: | Closed | Last Modified: | 2016-08-14 20:49:28 | |
| Resolution: | Fixed | Closed By: | fvogel | |
| Closed on: | 2016-08-14 20:49:28 | |||
| Description: |
Hi, on OSX, using unix like Tcl/TK .dylib, since 8.5.11 I cannot acces binding unless I hit a key first. with 8.5.13, if I copy/paste code from 8.5.10 tkUnixKey.c and recompile Tk, everything is fine but I doubt it's a good hack. here's the link to the discussion on comp.lang.tcl https://groups.google.com/d/msg/comp.lang.tcl/8bHk1QKGjFA/ukrgsAQps2QJ Best regards, Nicolas | |||
| User Comments: |
fvogel added on 2016-08-14 20:49:28:
As per my understanding this bug was fixed when fixing [3599312] (with the same fix). Please just reopen if I'm wrong. added on 2013-02-21 12:43:40: while investing to correct the bug, I came to the same conclusion as you about the TkpInitKeymapInfo(). your fix works perfectly, thanx ! it's a shame that SF tracker do not notify about comments, you published the fix 1,5 month earlier.... ++ cjmcdonald added on 2013-01-03 19:35:04: See bug #3599312, which may be the same issue on Unix and has a fix attached. wordtech added on 2012-11-29 22:18:22: I don't have the correct build setup on my system for an X11 version of Tk, and as this is not a native (Aqua) issue, I'm not the right person to address the bug, or even if there is a bug--dkf appears to think there is not one. added on 2012-11-29 20:58:26: does 8.5.10 distros had problems on others platforms? because the ifdef where not present in it... dkf added on 2012-11-29 20:54:53: But then it doesn't work on other platforms, which is the whole reason that code was put in there. added on 2012-11-29 20:40:25: more digging...
in tkUnixKey.c and especially KeySym TkpGetKeySym(), if I remove the TK_USE_INPUT_METHODS ifdef and all enclosed code, it works again with tk8.5.13.
the comment fro the ifdef section is
/*
* If input methods are active, we may already have determined a keysym.
* Return it.
*/
so I guess that Tk do not have a determined keysym
hope this helps...
++
nicolas
dkf added on 2012-11-29 16:21:31: See Bug 1924761 for the change rationale, and I have no idea why you're having problems. added on 2012-11-29 15:46:54: Kevin, so to confirm, this is seen on MacOSX.7.5 with Tk version since 8.5.11 (8.5.10 works fine). I've compiled 8.5.13 on Ubuntu12.0.4 and test it and it works fine. I'm able to use Ctrl+n (File/New in my program) in the very beginning without the need to hit a key first. for the diff, I've just picked the 8.5.10 tkUnixKey.c and paste it in the 8.5.13 distro. best regards, nicolas wordtech added on 2012-11-26 21:50:17: First, just to confirm, this is seen in the X11 version of Tk on OS X? What OS version are you on? Can you test 8.5.11 on another version of X, such as Linux, to see if it's there? Can you provide a diff of tkUnixKey.c? I have very little knowledge of X11 keysyms, and I would think this bug would be evident on other X systems. I may refer this to another maintainer with more Unix expertise than me, depending on the feedback. | |||