DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version: 1.3-current (r9217)
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version: 1.3-current (r9217)
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version: 1.3-current (r9217)
Attached file fltree.patch...
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version:
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version: 1.3-current (r9217)
Attached a patch (fltree.patch) to address slowness when selecting items
in the 100k test program. Thanks
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version: 1.3-current (r9217)
I tested fltree.patch in Windows with the tree-100k.cxx sample code and my
application. It worked fine.
Looks like fltree.patch would break the ABI, so we can probably not
apply this in fltk 1.3.x.
Good point.
Hmm, we really need a way to get ABI breaking stuff into FLTK,
because if we don't, we forget to add it later.
Also, I think a lot of people compile static, and aren't concerned
with the
Perhaps we can create a configure(1) controlled macro flag called
FLTK_ABI_FEATURE that is default off, and could be used to
#ifdef out ABI breaking features.
Oh, and in case it isn't obvious, users could configure'
this feature on (eg. 'configure --enable-abi-features')
and build
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: http://www.fltk.org/str.php?L2795
Version: 1.3-current
Fix Version: 1.3-current (r9217)
Albrecht: see my reply in fltk.bugs, along with an RFC that might
make ABI breaking code a possible option
Hello !
So I imagine with this arrangement, when FLTK bumps its ABI version,
it's clear to the devs what to clean up; the #ifdef's are removed,
the feature file is merged into the normal file, and the feature file
would be removed.
Or something like that.
For me, this sounds like a great
OK, I just added fltree.patch to STR#2795:
See: http://fltk.org/str.php?T2795
This is the direction I plan to go for optimizing the
selection slowness issue with the 100k item tree.
Please give it a whirl, and if there's comments or trouble
with it, please follow up in the STR.
I didn't check
Hello,
I have a property dialog including a tree, so I need that when the dialog is
shown a given item in the tree is selected and visible (tree scrolled
beforehand) to reflect current property state.
The problem is that neither display() nor show_item() work until the tree (and
dialog) are
Finally got some more time to work on this. The workaround I have found to
this problem is to add this somewhere in the main loop:
gui.mOutput-throw_focus();
the fltk::Output will steal key events for Delete, Backspace, Ctrl, and a few
others. I'm not sure why this should happen. I can
11 matches
Mail list logo
