Package: libfltk1.3
Version: 1.3.0-8
Severity: normal
Drag and drop of text from iceape 2.7.12 into a fltk text widget doesn't
drop the selected text, only a single "<" character.
- run "examples/texteditor-simple.cxx" from fltk1.3-doc
- run iceape and select some text in its html display part
- drag and drop that text into "texteditor-simple"
- texteditor-simple inserts a "<", whereas I expected the
selected text
Uncommenting the printf in src/Fl_x.cxx fl_handle() suggests iceape
offers various types
fl_dnd_source_types[0] = 557 (text/_moz_htmlcontext)
fl_dnd_source_types[1] = 558 (text/_moz_htmlinfo)
fl_dnd_source_types[2] = 559 (text/html)
fl_dnd_source_types[3] = 560 (text/unicode)
fl_dnd_source_types[4] = 561 (text/plain;charset=utf-8)
fl_dnd_source_types[5] = 538 (text/plain)
It seems fl_handle() chooses the first "text/". From iceape that
happens to be "text/_moz_htmlcontext". That type seems to be something
16-bit so has "\0" every second byte so making the string stop at the
first "<" (it's something with html markup anyway).
I don't know if there's supposed to be any significance in the order
types are offered. But perhaps fltk could prefer "text/plain" if
present. Or the "text/plain;charset=utf-8" if that would be better and
would work (I notice fl_Xatextplainutf is upper-case "UTF-8"). Then
fall back to the first text/ otherwise, or something like that.
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages libfltk1.3 depends on:
ii libc6 2.13-10
ii libfontconfig1 2.9.0-7.1
ii libgcc1 1:4.6.1-3
ii libstdc++6 4.6.1-3
ii libx11-6 2:1.5.0-1
ii libxext6 2:1.3.1-2
ii libxft2 2.3.1-1
ii libxinerama1 2:1.1.2-1
ii multiarch-support 2.13-38
libfltk1.3 recommends no packages.
libfltk1.3 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
