> When XChangeProperty is called a few times with property set to some (different) number and XGetAtomName() returns NULL, then _nxDelAllProperty only deletes the first one.
I don't quite understand what XGetAtomName has to do with this, is this a seperate call FLTK makes? XChangeProperty uses Atoms, not names. Please explain > Looks like nxlib combines all AtomNames = NULL into one even though they have different Atom properties. I think there's two bugs here. First, if XChangeProperty is called with an Atom of 0, then it should just return. This should be tested before doing anything. Secondly, if XChangeProperty is called with an Atom with the same value, the property value should be overwritten (or prepend/appended). In no case should the property be created twice. Does this make sense given your observations? Regards, Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
