|
|
Pretty sure the example can be done without deriving from Fl_Tree_Item.. it'd just be not as clean from an OO point of view.
Not sure about rust, but you could use Fl_Tree_Item's userdata as a pointer to your own structure of data per item to keep track of your widget/icon state info, and the my_handle() method I added to Fl_Tree_Item could just as easily be a static function that takes a pointer to the Fl_Tree_Item as a parameter. The callback can then get the item and pass it to the static global function my_handle() which can do the work it does.
Anyway, if you're interested or need guidance on that, let me know.
Meanwhile, about this issue, can we close it? It's become more of a how-to-use instead of a bug report, and such things are better done on the newsgroup where everyone can benefit from the discussion. Once this issue closes, most people will never see it.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
[ Direct Link to Message ] | |
|
| |