Login with username and password (forgot your password?)

I get either the directory creation error, or the A: drive. Don't think I ever got both in sequence.

That does happen right after the machine wakes up, not when I take a screenshot after the wake up.

Probably the OS takes some time to restore the network connection, and your code's faster at... doing something ;-)

On my home desktop the "My documents" directory is stored on a network drive on my NAS. This results in Screenshot Captor defaulting to:

S:\DOC\DonationCoder\ScreenshotCaptor\Screenshots

to store the screenshots.

The behavior of the latest version with this setup is strange.

Often when the machine wakes up from hibernation I get one of the following errors:

- Error creating non-existing directory: 'S:\DOC\DonationCoder\ScreenshotCaptor\Screenshots'.
- (even weirder) "The is no disk in drive. Insert a disk in drive A: / Cancel / Try Again / Continue"

For now, I'll work around this by forcing the screenshots to be stored on a local drive, but this is inconvenient as I cannot access them anymore from my laptop...

Any clue?

Glad to have been helpful in improving the product.

Now I have to fire a new thread to complain about the UI changes  I now have to click twice to get the filename (or image) to the clipboard after a capture instead of only one previously...

works for me too, 64-bit Windows 7 Pro

Filename is

Screenshot of 'C__Windows_system32_cmd.exe' on 2013-03-29.png

OS is 64-bit Windows 7 Pro

Don't have pre-Windows 7 OSes here to test with.

What are you running?

Here's a very simple scenario I just played with 4.00

- start Notepad
- maximize it
- start CMD
- move it about the middle of the screen, in front of the maximized Notepad
- hit Alt+PrtSc
- the resulting filename is

Screenshot of 'Untitled - Notepad' on 2013-03-28.png

whereas I would expect

Screenshot of C:WindowsSystem32Cmd.exe' on 2013-03-28.png

or something.


(I hate to say, I still have no clue as to how to attach a file to a forum post here...)

I just noticed (off-topic? do you want a new thread?) that "Grab Active Window" (with the 3.15.01 beta) yields an incorrect filename for console applications: the title of the window which is just "below" the upper-left corner of the console (current) window/application is used instead.

Seems to work way better.

What's the logic? If the region intersects with a window, you use that window's caption?

What if it intersects with more than one window?

Well... the EXE is 3.08.01....

Wrong URL, I would say 

I swear I didn't intentionally install it to the incorrect directory.

Only 3.08.01 shows up in "Add or remove programs."

Did you at some point change the installation defaults?


I've uninstalled 3.08.01 using Control Panel and then renamed the

C:\Program Files (x86)\ScreenshotCaptor 

directory to

C:\Program Files (x86)\_ScreenshotCaptor

After that I reinstalled 3.08.01.

Situation's now back to normal.

Until.... 

I hate to say, but the problem's still there / back.

DcUpdater reports I have both ScreenshotCaptor 3.07.01 and 3.08.01 installed.

The one running is 3.07.01.

3.07.01 is reported as:

ScreenshotCaptor:
WebPage: http://www.donationcoder....reenshotcaptor/index.html
DcUpdate File: C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate
Remote Version File: http://www.donationcoder....aptor/pad/versioninfo.xml
Remote Update File: http://www.donationcoder....ScreenshotCaptorSetup.exe


3.08.01 is reported as:

ScreenshotCaptor:
WebPage: http://www.donationcoder....reenshotcaptor/index.html
DcUpdate File: C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor\ScreenshotCaptor.dcupdate
Remote Version File: http://www.donationcoder....aptor/pad/versioninfo.xml
Remote Update File: http://www.donationcoder....ScreenshotCaptorSetup.exe

How do I get things back straight?

Isn't a bug still lurking somewhere?

you probably meant "if I can improve that" 

Seems to be indeed something like that.

Except when the active window is a Windows Explorer window, in which case %windowtitlepure% expands to an empty string. That's also the case BTW if you capture the entire active Windows Explorer window (whereas I would expect this to be the window's caption i.e. the full path to the directory in my case).
 

Most often, when capturing a region I get a filename where %windowtitlepure% is replaced by an empty string.

Today I got something strange: this got expanded to the "massaged window title" of some window that was on my desktop, not even belonging to the app (IE) I captured a region from...

What's the official spec for how %windowtitlepure% is supposed to be expanded?

if you need a tester for preliminary builds...

I hate to say, but the problem is still there with 3.06.01...

I hate to say, but just got the problem with 3.04.01

I hate to say, but just got the problem again with 3.03.01...

BTW, where does one find the documentation for things like %windowtitlepure% or %windowtitle%?

Hi,

Just had to reconfigure the ScreenShot Captor preferences for the filenames, and hit the "Help on fields" button.

The formatting is rather poor:
- the field code and description are not separated from each other
- the descriptions should be "tab-aligned" (if you see what I mean)

More an annoyance than anything else, but improving this would "add polish" to the product 

I sometimes do yell at my monitor, too 

You're welcome.

And sorry if you get the feeling I got you frustrated. Bugs are a fact of life, we're just humans 


Have a good sleep!

I've intentionally restored the virtualstore stuff (incl. the DcUpdater file for DcUpdater claiming it's 1.28.1), installed your new build, and it does ignore the virtualstore information.

[not]

Note that in order to get your system back to normal letting DcUpdater update itself to 1.30.01 is not enough. You must delete the following two directories:

C:\Users\<user>\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor
C:\Users\<user>\AppData\Local\VirtualStore\Program Files (x86)\DcUpdater

(removing ' (x86)' if you're not running 64-bit Windows).

Otherwise, DcUpdater will keep believing 1.28.01 is installed and will reinstall 1.30.01 forever.


HTH

U're welcome.

Indeed I'd experienced this kind of problem for quite some time, but hadn't bitten the bullet 'til today.

I'm assuming a public update to DcUpdater (that it will detect ;-) ) will be online soon.