> The reason is because in order to have form tooltips when programming > to the Windows API (as VFP must do internally), you have to > initialize the windows common controls, which basically calls and > loads Comctl32.dll if needed (and maybe others?) into memory. This > must be done first, even if you never end up using tooltips. When you > set this property in VFP to .T., it no doubt does this for you > internally, which would be a waste of memory if you never end up > using the functionality.
Really? Seems odd that they would use the common controls for tool tips but nothing else... Maybe ActiveX controls support tool tips somehow and that'd be why... Either way, it's a great argument for using common superclasses to set it once and forget it. Too bad it's not that easy with legacy apps... -- Derek _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
