| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #1122
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 4 - High, e.g. key functionality not working |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Ctrl+C doesn't work instantly in Fl_Text_Display |
|---|
| Version: | 1.1-current |
|---|
| Created By: | Sadysta |
|---|
| Assigned To: | matt |
|---|
| Fix Version: | 1.1.7 (SVN: v4713) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | Sadysta
00:01 Dec 14, 2005 |
| Resumption of STR #1118. You've really rushed to close that one. Unfortunately it's not a Cygwin issue.
I've tested again in these environments:
1) Windows XP, MSVS.NET
2) Slackware Linux 10.1, gcc
and the problem exists.
Maybe it has something to do with the way FLTK handles keyboard events. I've observed that if I do everything very calmly (i.e. press Ctrl slowly, hold it for a second and then firmly press C) the text gets copied most of the time.
BTW. I'm not the only one who is experiencing this. At first it was some (3 or 4) users of my software (Unicom IM), who had reported this issue to me. I've confirmed the problem on my own machine, distributed the demo program among my users to eliminate the possibility of fault in Unicom itself, and only then reported the issue to you.
Please, investigate.
___________ STR #1118 ___________
I remember that once there was a problem with pasting things from external applications to fltk ones, but now the situation is inversed. Sometimes I have to hold Ctrl and press C several times to make the text selected in Fl_Text_Display to get copied to the clipboard.
I've attached a really simple demo program. All you need to do is to try to copy some text from Fl_Text_Display to the clipboard. | |
| |
| #2 | matt
11:53 Dec 15, 2005 |
| Slightly unrelated, and I am sure you'd do this different in a normal program, but you should make sure that the Text_Buffer gets deletd *after* the Text_Display. If you allocate them locally, like you did in the mini example, you must allocate the buffer first, so it gets deleted last.
Anyway, that does not fic the bug, but this text is a pretty sure sign that I look into it (confirmed btw. it doesn't work as expected!) | |
| |
| #3 | matt
12:32 Dec 15, 2005 |
| Fixed in Subversion repository. | |
[ Return to Bugs & Features ]
|
| |
