On 09.01.2012 00:56, Greg Ercolano wrote:
> On 01/08/12 04:48, Albrecht Schlosser wrote:
>> This is *not* dependent on linking statically or dynamically! If your
>> version of the FLTK lib is compiled with another ABI version macro than
>> you define in your application, then you *have* different A
On 01/09/12 03:19, Albrecht Schlosser wrote:
>> I'd think the version# would simply be set at FLTK build time,
>> 'baked' into one of the .H files, and then could not be changed
>> unless the lib were rebuilt.
>
> Okay, but it would be difficult (at least I think so) to change the
>
On 01/09/12 03:19, Albrecht Schlosser wrote:
> The reason why I suggested a version number and not a simple on/off
> switch is that someone could enable all 1.3.2 ABI features, and then
> upgrade the sources to 1.3.3 or later, but still keep ABI compatibility
> with the previous headers and shared
On 01/08/12 04:48, Albrecht Schlosser wrote:
> Users are encouraged to do something like this in their main program
> or wherever they have potential ABI differences:
>
> if (fl_abi_version() != FL_ABI_VERSION)
>fl_abort ("FLTK ABI version mismatch: %d != %d",
> fl_abi_version(), FL_ABI_V
Is there a toolbar like CToolBar in MFC? Can be dragged,docked.
Thank you!
___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
