You're the first one to complain, or should I say inquire?
Juding from CVS logs, I removed Xm/ManagerP.h from the 2.0
tree because it didn't differ much from the 1.2 version.
I could have put an #ifdef in, but I am usually inclined not
to do that, especially in files that get installed by 'make
install'.
So theoretically it is possible to fix this, but I'm not
happy about the obvious fix.
Do you have a problem with that ?
We're not advocating binary compatibility all that much, and
sometimes include files do change, even between minor
releases. The XmFontList changes are a perfect example of that.
Danny
Martin Simmons wrote:
> I have a compiled subclass of XmDrawingArea that works on Linux machines with
> the 0.93.18 rpm but emits the message
>
> (Xt Warning) Representation size 1 must match superclass's to override resizePolicy
>
> under 0.93.36. The application eventually segfaults in XmFontListCopy when
> creating an XmCascadeButtonGadget.
>
> Looking at the widget structure, the warning is caused by the
> XmDrawingAreaPart.resize_policy field having a different offset since the
> XmManagerPart.popup_handler_callback field was added
> (include/Motif-1.2/Xm/ManagerP.h).
>
> Is this an intended binary incompatibilty or a bug?
--
Danny Backx ([EMAIL PROTECTED] [EMAIL PROTECTED])
Home page : http://users.skynet.be/danny.backx
Projects: LessTif (http://lesstif.sourceforge.net)
Xbae (http://xbae.sourceforge.net)
_______________________________________________
Lesstif mailing list
[EMAIL PROTECTED]
https://terror.hungry.com/mailman/listinfo/lesstif
