nazgul@alphalpha.com (Kee Hinckley) (11/27/90)
> Is there any reason why XmNdialogTitle is an XmString? > Isn't any font/charset info lost when the XmString is > converted to a char*? Is this info somehow passed to the > window manager allowing different fonts within a title bar? I think it is possible to specify the character set (using compound strings) in R4, although I haven't tried yet.
meeks@osf.org (W. Scott Meeks) (12/01/90)
>> Is there any reason why XmNdialogTitle is an XmString? >> Isn't any font/charset info lost when the XmString is >> converted to a char*? Is this info somehow passed to the >> window manager allowing different fonts within a title bar? > >I think it is possible to specify the character set (using >compound strings) in R4, although I haven't tried yet. > Actually the XmString in XmNdialogTitle is converted to Compound Text (XPG Compound Text standard for ICCCM), which is typed in Motif as char*, before it is sent to MWM. So all the font/charset information is retained and it is possible to have multifont window titles. Looks pretty cool actually. W. Scott Meeks Open Software Foundation meeks@osf.org (617) 621-7229