Messages

1

Screenshot Captor / Re: Active Window capture includes shadow in Windows 10 w/ Aero Glass cap disabled

« on: March 14, 2017, 09:01 AM »

Okay, looks like that worked.  Let me know...

2

Screenshot Captor / Re: Active Window capture includes shadow in Windows 10 w/ Aero Glass cap disabled

« on: March 14, 2017, 09:00 AM »

Sorry for the terrible delay.  I didn't get a notification about this and haven't come back to check on it until today.

Okay, let me try the attachment again.

3

Screenshot Captor / Re: prt sc not working

« on: March 14, 2017, 08:55 AM »

Just following up.  I don't remember when the issue stopped, but I haven't had this problem in a while.  One day it just resumed functionality.

For those who are discussing Fn+PrtScrn, that should merely generate a Print Screen keyboard scancode.  It's a simulated switch in the device driver, but it should work like regular print screen.  No reason for it to act any differently.

At least that's how it should work...

4

Screenshot Captor / Re: prt sc not working

« on: August 26, 2016, 12:20 PM »

I had issues with Windows 7 but have had lots more with Windows 10.  I'm now using Startup Delayer, a free startup launcher that can load things when I boot up after everything else has loaded to launch Screenshot Captor, as well as several other apps.  I get the impression that when Windows processes autoruns it hasn't loaded all the credentials yet.  On two occasions, the *.INI setting files for portable apps like Screenshot Captor got reset to factory defaults, as if the system didn't think the app should have rights to the folder it's in.  After several hours of research I finally gave up and went with the startup delay app because nothing else worked consistently for everything.

Simple things, like the Startups folder under the Start menu just flat don't do anything anymore.  Stuff I put in there had no effect.  Some of this could also be due to corporate IT policies, I don't know, but it's a great waste of time trying to resolve things like this.

<rant>
I have tinkered with Linux on several occasions but at this rate, and especially as Microsoft migrates to a monthly fee licensing model, Linux is looking better all the time.
</rant>

5

Screenshot Captor / Active Window capture includes shadow in Windows 10 w/ Aero Glass cap disabled

« on: August 26, 2016, 11:48 AM »

Note: Related post (closed, can't reply to it):  https://www.donation...ex.php?topic=42196.0

Recently I started seeing shadows when capturing an Active Window (like a dialog) in Windows 10.  See attached.
[ Invalid Attachment ]

An option was added to SSC years ago to get around this which I have disabled.  I see another option that I've never used and tried it but it didn't have an effect either.  See attached.
[ Invalid Attachment ]

I suppose this is due to the fact that Microsoft appears to be bent on breaking fundamental architectural standards (their Microsoft Dynamics CRM app randomly shows a system modal dialog that says "I'm doing something" then automatically closes, preventing anything from being done in any app and when it's done the original keyboard focus is not restored so you have to go click the active app again).  Okay, not going to rant, but 

Not a show stopper, but I have to manually clean the dialog up by trimming the extra stuff off the edges.

I took a look at the message dialog box used in the first screen capture and here's what I'm seeing with respects to the parentage:

[Select]

HWND [511EC]
PID [000003F0]
Title [Sample Windows 10 Dialog]
Class [#32770]

#32770's children:
    Child #1: HWnd=511D4 Class=Button Title=OK
    Child #2: HWnd=813F6 Class=Static Title=None
    Child #3: HWnd=611E8 Class=Static Title=Note the shadow is coming through although Arrow Glass Transparency option is disabled.

It's been a while since I snooped around in the OS, so... Using a window inspection tool I wrote years ago that does a system WindowFromPoint() call iirc, I think the OS has expanded the non-client region of the window for painting shadows.  The NCR used to just consist of the window's border area.

Anyway, I dug through all the SSC options again and can't find anything that can resolve this.

6

Screenshot Captor / Re: prt sc not working

« on: August 26, 2016, 11:08 AM »

Quick note about this problem.  I started seeing this in Windows 10 fairly recently (today 2016.08.26).

Some of Microsoft's Office 365 apps are trapping all keystrokes and telling the OS that the keypress event has been handled, so the global handler doesn't get it.  I see this on some web sites too.

In Win32 at least, shouldn't be different in Win64, the only time an app should flag a keystroke event as handled is if it is an app-specific keystroke and the window is active.  Otherwise the app is supposed to tell the OS effectively "OK I'm done with it, pass it on" and not "eat" the keyboard message.

Anyway, one thing to try is to make sure you're running Screenshot Captor as administrator.  This appears to be required in order for global hotkeys to work as they used to.  My workplace has strict policies and I think their restrictions have sometimes caused this to happen.  It's not happening since I forced the app to load with administrator privs (I only have "local admin" privs on this workstation, incidentally).

You can also try setting the "compatibility mode" option in the properties dialog for the shortcut.  If you don't use a shortcut to start SSC, create one.