| [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #2998
Application: | FLTK Library |
Duplicate Of: | STR #2980 |
Status: | 2 - Closed w/o Resolution |
Priority: | 4 - High, e.g. key functionality not working |
Scope: | 2 - Specific to an operating system |
Subsystem: | Core Library |
Summary: | Fl::event_text() returns no meaningful value for FL_DND_ENTER and FL_DND_DRAG on OS X |
Version: | 1.3.2 |
Created By: | jlp2 |
Assigned To: | ianmacarthur |
Fix Version: | 1.3-current |
Update Notification: | |
Trouble Report Files:
Trouble Report Comments:
|
#1 | jlp2 05:40 Oct 27, 2013 |
| Using the current FLTK 1.3.2 release, the Fl::event_text() function has no meaningful value for the FL_DND_ENTER or FL_DND_DRAG event under OS X. I'm not sure if this is intended or if it's a bug. I attached a .diff file that shows the changes I made to get the value for these events, too. Maybe someone who knows the code better could verify if this solution is correct. | |
|
#2 | ianmacarthur 15:45 Mar 11, 2014 |
| This STR mirrors the Win32 STR #2980 also.
I would note that I don't think I'd expect event_text() to have anything useful for a FL_DND_ENTER or FL_DND_DRAG event, I think I'd only expect it to have something useful to read in response to a FL_KEYUP, FL_KEYDOWN, FL_PASTE, and FL_DND_RELEASE.
Can the OP describe what was anticipated? | |
|
#3 | ianmacarthur 16:26 Sep 04, 2014 |
| Duplicates #2980, which is left open for consideration | |
|
#4 | ianmacarthur 02:44 Sep 05, 2014 |
| Assigned as duplicate of 2980 | |
[ Return to Bugs & Features ]
|
| |