CS_CLASSDC for starkits' windows?
- From: "Emmanuel Frecon" <efrecon@xxxxxxxxx>
- Date: 5 Sep 2006 00:34:01 -0700
Hello folks,
I am currently trying to understand why my script works when run from
the normal wish interpreter and why it does not when run from within a
starkit/pack. The script uses the infamous PrintWindow() function of
the Windows (XP+) API to get the content of windows that it opens and
displays them with some rotation on a Zinc canvas. This part is done
using a capture DLL of mine that I still ought to give away the source
for (not ready yet (TM) :-)).
Well, anyhow, before digging further and trying further to understand
why things are not working when running from a starkit/pack, I thought
I would ask for help here, in case anyone has encountered similar
problems in the past or knows what is going on.
Using winspy, I have been able to track down the problem to the class
properties of the windows themselves. At least, I think I have... It
seems that all windows that are opened from the starkit/pack binary
have the CS_CLASSDC flag on, while all windows that are opened from the
stardard (activestate to be precise) wish have not got that flag on.
Does anybody know why? Apparently, CS_CLASSDC is in general not a good
idea. See the following link for more information:
http://blogs.msdn.com/oldnewthing/archive/2006/06/02/614235.aspx. Is
this an optimisation of some sort? Is there anyway to turn off that
behaviour and let all windows have their own device context?
I would appreciate any help, I'm rather stuck!
/Emmanuel
.
- Follow-Ups:
- Re: CS_CLASSDC for starkits' windows?
- From: Emmanuel Frecon
- Re: CS_CLASSDC for starkits' windows?
- Prev by Date: Does scotty works with tcl 8.3 ?
- Next by Date: anyone know where I can get a tclkit with thread support
- Previous by thread: Does scotty works with tcl 8.3 ?
- Next by thread: Re: CS_CLASSDC for starkits' windows?
- Index(es):
Relevant Pages
|
