--- In [email protected], "brucexs" <bswit...@...> wrote: > Maybe: If you click on an icon, that would make the desktop the foreground > window, which would call you hook again, which would make PowerPro the > foreground window -- maybe that would be source of confusion?
Well, it works fine with my test dialog app. I can't select the icons at all when the ppro bar comes to the front. But I'm not going to worry about it anymore, I've lost too much time in this microsoft mess. > > Is it possible to use this plugin architecture to easily get the Bar's > > window messages (PAINT, MOUSEMOVE, ...) to accomplish the pinned/stick on > > bottom effect (append a SetWinPos BOTTOM) that I mentioned was built into > > that rainlendar desktop calendar? ( > > http://tech.groups.yahoo.com/group/power-pro/message/36360 ) > > No, you cannot register for paints, sorry. As PowerPro is meant to be used > as bar, and so clicked on (leading to paint then too, but you want it to stay > foreground in that case), this does not sound simple to implement as a way of > deciding when to stay background. I had thought that by appending SetWindowPos(..HWND_BOTTOM..) to the very end of existing WM_PAINT (and/or other select WINDOWCHANGINGPOS type events) it could be accomplished, but if it gets more hacky than that then I don't think I want to try. > If you really want to play with this, I can add a pproservice function that > allows you to register to receive a callback at the end of paint operations. > Then you could play with in plugin. > > BTW, as I am sure you noticed, ppro plugins extern "c" {} for dll entry > points if you are writing in c++/ Yup, C++. I eventually figured out that the exported symbol names would be mangled without that, thanks.
