For all the features to work correctly in tigervnc, one needs a patched version of fltk. You can see the details in the BUILDING.txt file in the tigervnc tarball, here's a summary: # Export dead key information from FLTK to the apps # http://www.fltk.org/str.php?L2599 fltk-1_v4.3.x-keyboard-x11.patch fltk-1_v4.3.x-keyboard-win32.patch fltk-1_v6.3.x-keyboard-osx.patch # Notify applications of changes to the clipboard # http://www.fltk.org/str.php?L2636 fltk-1.3.x-clipboard.patch fltk-1_v5.3.x-clipboard-x11.patch fltk-1_v3.3.x-clipboard-win32-fix.patch fltk-1_v2.3.x-clipboard-win32.patch fltk-1_v2.3.x-clipboard-osx.patch # Ability to convert a Fl_Pixmap to a Fl_RGB_Image # http://www.fltk.org/str.php?L2659 pixmap_v2.patch # Support for custom cursors # http://www.fltk.org/str.php?L2660 fltk-1_v5.3.x-cursor.patch # Improve modality interaction with WM # http://www.fltk.org/str.php?L2802 fltk-1_v2.3.0-modal.patch # Window icons # http://www.fltk.org/str.php?L2816 fltk-1_v3.3.0-icons.patch # Multihead # http://fltk.org/str.php?L2860 fltk-1.3.x-screen_num.patch fltk-1_v3.3.x-multihead.patch I haven't fully analyzed all of these, so I don't know if it would be better to just apply them all uncondionally, or have a tigervnc use flag or something to control applying them? But it would be nice to get an ebuild that incorporates them, I'm particularly missing multihead right now :(.
* These patches are already upstream, or appear to be scheduled to be appplied and shouldn't be controversial: http://www.fltk.org/str.php?L2636 fltk-1.3.x-clipboard.patch fltk-1_v5.3.x-clipboard-x11.patch fltk-1_v3.3.x-clipboard-win32-fix.patch fltk-1_v2.3.x-clipboard-win32.patch fltk-1_v2.3.x-clipboard-osx.patch http://www.fltk.org/str.php?L2659 pixmap_v2.patch http://fltk.org/str.php?L2860 fltk-1.3.x-screen_num.patch * These patches do not change the ABI of fltk: http://www.fltk.org/str.php?L2660 fltk-1_v5.3.x-cursor.patch (Depends on pixmap_v2.patch) http://www.fltk.org/str.php?L2816 fltk-1_v3.3.0-icons.patch * These patches should be looked at a bit first, or wait for upstream: http://www.fltk.org/str.php?L2599 fltk-1_v4.3.x-keyboard-x11.patch fltk-1_v4.3.x-keyboard-win32.patch fltk-1_v6.3.x-keyboard-osx.patch http://fltk.org/str.php?L2860 fltk-1_v3.3.x-multihead.patch Hope this helps!
The patches need to be applied on fltk, not in tigervnc, so reassigning to desktop-misc in case they are interested in applying the patches.
where are they applied? Maybe it would make more sense to ship a snapshot.
=x11-libs/fltk-1.3.2_p10088 is in the tree. It isn't supposed to go stable, I guess. It still isn't obvious how this helps tigervnc, except that it was apparently based on fltk snapshots (hence USE=internal-fltk?).
(In reply to Jeroen Roovers from comment #4) > It still isn't obvious how this helps tigervnc, except that it was > apparently based on fltk snapshots (hence USE=internal-fltk?). Exactly, however in the latest version(1.3.0) they stopped shipping an internal fltk.
(In reply to Raúl Porcel from comment #5) > (In reply to Jeroen Roovers from comment #4) > > It still isn't obvious how this helps tigervnc, except that it was > > apparently based on fltk snapshots (hence USE=internal-fltk?). > > Exactly, however in the latest version(1.3.0) they stopped shipping an > internal fltk. Ah, so for 1.3.0 you could set a minimal fltk version?
(In reply to Jeroen Roovers from comment #6) > (In reply to Raúl Porcel from comment #5) > > (In reply to Jeroen Roovers from comment #4) > > > It still isn't obvious how this helps tigervnc, except that it was > > > apparently based on fltk snapshots (hence USE=internal-fltk?). > > > > Exactly, however in the latest version(1.3.0) they stopped shipping an > > internal fltk. > > Ah, so for 1.3.0 you could set a minimal fltk version? tigervnc-1.3.0-r1 is supposed to go stable for bug 500372, this would mean fltk stable as well...
It looks like most if not all of these patches are in the recently stabilized fltk 1.3.3? So maybe it's time to just close this out as resolved.
This was fixed long time ago
