Re: [fltk.development] [RFE] STR #2599: expose dead keys to applications

DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature I've had a look at things and it seems that fcitx doesn't like it when you call Xutf8LookupString() before XFilterEvent(). The XIM API is a bit

Re: [fltk.development] [RFE] STR #2599: expose dead keys to applications

DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature Pierre Ossman wrote: 1. Implement a hook system in FLTK where applications get an opportunity to handle platform events before FLTK. Then ...

Re: [fltk.development] [RFE] STR #2599: expose dead keys to applications

DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature Actually, Fl::event_dispatch() is called much later than what is needed here. It allows intercepting FLTK events, but not the native ones. It

Re: [fltk.development] [RFE] STR #2599: expose dead keys to applications

DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2599 Version: 1.3-feature Sparkaround, Many thanks for your great help. We now have all the information needed about the patch and the issue of composed character

[fltk.development] [RFE] STR #2618: Fl_Tree::add() needs a way to add items that contain front slashes

DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2618 Version: 1.3-feature The add() function in Fl_Tree needs to be able to allow the user to specify items that contain front slashes, without the slashes being

[fltk.development] API naming: future/past tense, etc

I was noticing while creating the Fl_Tree API I had some second thoughts about function naming. Things like: open() / close() / select() / deselect() all seem obvious enough, but when testing to see if something is selected, seemed one could go either present or past tense: is_open() vs.

Re: [fltk.development] [RFE] STR #2618: Fl_Tree::add() needs a way to add items that contain front slashes

[STR Closed w/Resolution] Link: http://www.fltk.org/str.php?L2618 Version: 1.3-feature Fix Version: 1.3-current (r8632) Fixed in Subversion repository. Fl_Tree's add(), item_pathname(), and other 'pathname' oriented methods now handle escape characters (\) to protect forward and back slashes.

Re: [fltk.development] API naming: future/past tense, etc

I guess it's too late to change now, but to avoid future madness, is there something most folks agree on with this? I'd be curious.. I don't know about others, but I've always preferred past tense - is_opened(), etc Regards, Ben

[fltk.development] Online Doxygen docs

Hey all, I've not been able to work this out, but how does one rebuild the online doxygen docs from the latest source? I can build my own local copy, but the ones online are a little outdated and I've done a pile of work improving them (especially with the FileChooser class). I'd appreciate