--- In [email protected], "mockey_a" <[EMAIL PROTECTED]> wrote: > > > I've never dreamed that it may be related to > > the visual styles... > > It took some time to figure it out (but actually it took longer for > my message to appear here, it was one day late or so). Surprising > was also that with manifest I got no balloon tips at first but a > normal tooltip colored to your specs and all and with close-button > (added TTS_CLOSE in the code). Reason was that I had balloon-tip- > notification switched off in registry. But even with it switched off > I got balloon-tips without manifest (only without close-button).
Really strange. What on earth turning off just (balloon-tip) notification affects the visual styles? Anyway, I realized that I was once on the page you linked, however, never read the page. It was linked from the page TTM_SETWINDOWTHEME, which is actually the same as CCM_SETWINDOWTHEME. I never tried this one. Have you ever tested it? Could it be possible to control the close button or visual styles using only this message without .manifest files? > > So, is this > > also related to the visual styles? Hmm... a bit strange as other > apps > > have DropShadow/Layered-style without .manifest files. Then, maybe > > depends on Compilers too? The reason why PP doesn't have them > > defaultly without .manifest file is because PP is compiled with > VC5? > > Tooltips are created by comctl32.dll. You should have two versions > of that dll (one in windows/system, one in system32). I think apps > compiled with older headers (like from vc5) use the old version of > comctl32 by default (probably other old stuff as well). With the > manifest-file you tell Windows to explicitly use > version="6.0.0.0" (or greater) > of > name="Microsoft.Windows.Common-Controls" > for API-calls from powerpro.exe. Apps compiled with newer headers > should do that by default. I think this system should prevent old > apps from looking strange with visual styles turned on. > Maybe that's not thoroughly correct, but half-way at least ;-) I see. It was the first time I had ever questioned about compilers... > Apparently only the new comctl32-version can have its balloon-tips > switched off from the registry. It doesn't really make sense that it > shows now balloontips at all the, but well... > One more thing: > When you use the close-button the tooltip is not really closed but > deactivated. The window is still there. That is normal, because apps > normally reuse the same windows for their tooltips (just like you do > when you show the balloontip). So before creating the window you > should check for existence of hWnd, otherwise you keep adding > tooltip-windows. I noticed that: script file remained opened. So, I changed hWnd.Exists to hWnd.Visible. I think I should've done it from the start, hWnd.Exists is sort of double checking, invoking the same API twice, I guess. Sean Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
