2009/4/23 Jan Dubois <j...@activestate.com>: > On Wed, 22 Apr 2009, Rob May wrote: >> I think I vote for it too, although I suspect that it'll cause some >> (minor) layout problems for some people, as I'm not sure that all the >> control decorations are the same on styled/non-styled controls. > > There are some layout differences, so it will be visible in some apps.
Despite this I think it is the way forwards - perhaps we can find an easy way to disable it for those that don't want it? >> Last time I had some time to play (sadly I don't get much of that >> these days) I was looking at adding a manifest to GUI.dll - it's >> possible to add a manifest to a DLL and get the version 6 controls for >> any windows created by that DLL, even if the main APP doesn't have a >> manifest; however this depends on some stuff that's in the MS headers, >> and doesn't work with the mingw headers (and hence won't work with >> cygwin). I have a patch somewhere (but not with me at the moment). > > Interesting. I don't quite understand how this would work though, as > the names of the controls are registered globally, so I don't see how > you could mix old and new style controls inside a single process. I'm not going to pretend that I understand it all either, but it's certainly possible for a process to load both v5 and v6 controls and use both - I suspect that if one was to understand activation contexts in detail it's possible to have both sorts of contro; within the same window - not that I can think of a reason for doing that! My starting point was this documentation: http://msdn.microsoft.com/en-us/library/ms997646.aspx >> There are also some API calls that can be used to turn styling on and >> off on a per-app and per-window basis, once you've got the v6 controls >> loaded ..... I haven't yet come up with a suitable strategy for >> introducing this thought; perhaps adding a v6 manifest to perl.exe >> will force me to find time to investigate further? > > Could you find a link to some documentation about this so I can understand > how this is supposed to work? Per application: SetThemeAppProperties - http://msdn.microsoft.com/en-us/library/bb759825(VS.85).aspx Per window: SetWindowTheme - http://msdn.microsoft.com/en-us/library/bb759827(VS.85).aspx > Note that we'll also have to check with e.g. the wxPerl community, and > probably others to hear what they think about this. Of course. Perhaps the opposite of what I suggested above: use a v6 manifest, but turn off themes by default and provide an easy way to turn them on for those that want them? Regards, Rob. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Perl-Win32-GUI-Users mailing list Perl-Win32-GUI-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users http://perl-win32-gui.sourceforge.net/
