Welcome Guest. Please Login or Register. Apr 5th, 2018, 10:28pm
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
Re: Transparent that ain't
« Reply #2 on: May 31st, 2015, 05:20am »
No, I haven't. The problem isn't that I want to include a dialog box or any of the other things those procedures are supposed to deal with, but I can certainly try methods two and four (I don't particularly want the mouse pointer, as in method three).
Curiously, when I tried PrtScr I got the underlying screen but not what I had scribbled on top of it, yet when my son tried it, it all worked perfectly. I can only assume that PrtScr works differently in XP (which I am still using) and 8.1, which is what he has.
Logged
rtr2 Guest
Re: Transparent that ain't
« Reply #3 on: May 31st, 2015, 07:03am »
No, I haven't. The problem isn't that I want to include a dialog box or any of the other things those procedures are supposed to deal with
What they are "supposed" to deal with is unimportant; they are window capture routines that may solve your problem. Try them anyway.
Quote:
I can only assume that PrtScr works differently in XP (which I am still using) and 8.1
That's possible. DWM introduces an extra 'layer' of buffering between an application and the screen which can introduce incompatibilities. For example my 'magnifier' application does not - and cannot be made to - run in Windows 8/8.1
Sadly if PrtScr fails in XP then any method you try may fail too. Another nail in the coffin for that OS.
Logged
