|
|
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending]
Link: https://www.fltk.org/str.php?L3531
Version: 1.3.5
Fix Version: None
Thank you Albrecht. I "rediscovered" the README.abi-version.txt after
posting the STR. I know that 1.4 deprecates the FLTK_ABI_VERSION, but I
still think there is a problem with the way that all prior distributions
are posted. It is common for most end users to simply use "./configure &&
make && make install" when building an application and the dependent
libraries. Both the end-user-product maintainer and the user-builder must
be informed that "./configure --with-abiversion=10305" is required or the
end-user code may fail to compile. Try creating an application that uses
Fl_Tree wherein the enum FL_TREE-REASON_RESELECTED was a part of a boolean
test:
enum Fl_Tree_Reason {
FL_TREE_REASON_NONE=0, ///< unknown reason
FL_TREE_REASON_SELECTED, ///< an item was selected
FL_TREE_REASON_DESELECTED, ///< an item was de-selected
#if FLTK_ABI_VERSION >= 10301
FL_TREE_REASON_RESELECTED, ///< an item was re-selected (e.g.
double-clicked)
#endif /*FLTK_ABI_VERSION*/
FL_TREE_REASON_OPENED, ///< an item was opened
FL_TREE_REASON_CLOSED, ///< an item was closed
FL_TREE_REASON_DRAGGED ///< an item was dragged into a new place
};
I know this can be resolved at the user code level. But a more universal
solution would be to default the FLTK_ABI_VERSION to the actual
distribution version rather than a null string.
Link: https://www.fltk.org/str.php?L3531
Version: 1.3.5
Fix Version: None
[ Direct Link to Message ] | |
|
| |