David,

This is great information - you're right, I'm not looking at OpenMotif
so you've given me exactly what I need. I've changed LessTif's
_XmMapKeyEvents() so it always allocates space for the three arrays.

This makes it the responsibility of the caller to free the allocated
space. (I don't see this happening in OpenDX. Have I made the wrong
assumption ? It looks silly to allocate static memory for this,
but it may be the right thing to do.)

LessTif's CVS is adapted, it now works against OpenDX's CVS version.

Thanks !

        Danny

David Thompson wrote:
> After looking at the actual code for OpenMotif, OpenDX is correct. It
> is Lesstif that is wrong, since they are trying to provide
> compatibility with Motif. I won't say anymore than that since the
> Lesstif guys aren't suppose to be able to look at the internals of
> real Motif. But this should give them the clue on how to fix their
> version.

-- 
Danny Backx ([EMAIL PROTECTED] [EMAIL PROTECTED])
Home page :     http://users.skynet.be/danny.backx
Projects:       LessTif (http://www.lesstif.org)
                Oleo    (http://www.gnu.org/software/oleo/oleo.html)
_______________________________________________
Lesstif mailing list
[EMAIL PROTECTED]
https://terror.hungry.com/mailman/listinfo/lesstif

Reply via email to