Messages

1

DcUpdater / Re: DcUpdater fails when checking for updates

« on: June 26, 2017, 09:48 AM »

I had tried that ;-) with both "DcUpdater Warning" and "No valid packages found" but found nothing... because there was nothing to find....

Maybe the help text could be improved to mention that phrases can be found using quoting?

2

DcUpdater / Re: DcUpdater fails when checking for updates

« on: June 26, 2017, 08:37 AM »

Before posting, I tried every possible search variant, including "Advanced Search" (https://www.donationcoder.com/forum/index.php?action=search;advanced). The only methods I found there are "Match all words" and "Match any words", no "exact (sub)string match."

Did I miss anything?

3

DcUpdater / Re: DcUpdater fails when checking for updates

« on: June 26, 2017, 12:06 AM »

Everything went back to normal after I manually updated DcUpdater, and retried a few times the download of the ScreenShotCaptor installer.

Thank you so much for your friendly  help.

4

DcUpdater / Re: DcUpdater fails when checking for updates

« on: June 23, 2017, 04:44 AM »

well... search engines are supposed to allow you to find what you're looking for with any string found in the actual text...

Seems the search engine for this forum is very poor--or I don't know how to use it...

5

DcUpdater / Re: DcUpdater fails when checking for updates

« on: June 23, 2017, 02:11 AM »

I have manually installed DcUpdater 1.32.01 and the problem seems to have disappeared (the actual updating of ScreenShotCaptor seems to face a slow download issue, I'll report back on this when I'm back home this evening).

P.S. how comes searching the forum for "No valid packages found" or for "DcUpdater Warning" didn't give me the answer (if there is a "string match" search option I couldn't find it)?

6

DcUpdater / DcUpdater fails when checking for updates

« on: June 22, 2017, 11:56 PM »

Hi,

When I ask ScreenShotCaptor to check for updates, I get: "DcUpdater Warning: No valid packages found (with current search restrictions)".

In the operation log I find the following:

Code: Text [Select]

1. ERROR: Config File '-dontofferdcupdaterpage' could not be loaded by TinyXml lib - Failed to open file
2. ScreenshotCaptor: needs check
3. DcUpdater Program: needs check

Any clue?

7

Screenshot Captor / Re: ScreenshotCaptor now prevents CPU from going to low-power mode

« on: June 13, 2014, 12:11 AM »

Any  news?

8

Screenshot Captor / Re: ScreenshotCaptor now prevents CPU from going to low-power mode

« on: May 27, 2014, 02:18 AM »

The "memory" option, as expected, doesn't affect the polling.

You don't need to poll to discover changes in a directory: use FindFirstChangeNotification (http://msdn.microsof...364417(v=vs.85).aspx) to get notified when something happens in the screenshot folder.

9

Screenshot Captor / ScreenshotCaptor now prevents CPU from going to low-power mode

« on: May 26, 2014, 02:23 PM »

Hi,

While investigating my laptop's power consumption using "powercfg /energy" I noticed that ScreenshotCaptor is now listed as one of the processes that use the CPU in such a way that prevents it from being switched to its lowest-power mode. This was not the case previously (before 4.8?).

Process Explorer seems to reveal some sort of polling: see the huge number of cycles and context switches in the attached screenshot.

Can you please look into this (and fix the issue)?

Best regards,

Stéphane.

10

Screenshot Captor / Re: Screenshot Captor Early Beta Release: v4.6.4 Beta - Sep 11, 2013

« on: August 31, 2013, 01:54 AM »

It seems this update fixes the problem with regional settings: I've set my machine to half a dozen different country settings, and ScreenShotCaptor correctly starts up and preserves settings e.g. the position of the main window (haven't tested further, though).

While I'm at it, I want to report a slight but visually annoying case issue: in the "copy to clipboard" menu on the systray icon, the word "bitmap" starts with an uppercase "B" whereas all other choices are in lowercase. Similarly, in the "To clipboard" menu of the post-capture dialog, "Image" and "File" start with an uppercase letter, whereas "path "starts with a lowercase "p." This should be aligned IMVHO.

HTH

11

Screenshot Captor / Errors when .ini number format doesn't match current regional settings

« on: July 30, 2013, 02:22 PM »

Hi,

I'm hereby resurrecting an old thread about the same topic.

The current implementation of ScreenShot Captor yields fatal errors such as:

---------------------------
Screenshot Captor
---------------------------
'1.0' is not a valid floating point value.
---------------------------
OK   
---------------------------

if the .ini file contains numbers represented using a format different from the current "regional settings."

This problem will occur whenever the user changes the settings.

With my developer hat on, my feeling is that this should not be, because the user-configurable number formatting settings are related to UI, i.e. it specifies how the user wants to enter data, and how the system should present numbers displayed to the user--not how applications should internally represent information that the user will never see.

So I would suggest that the code be modified so that the encoding of numbers (or dates, or time, or whatever) in the configuration file(s) be independent from the input / display settings the user might want to choose.

What do you think?

12

Screenshot Captor / Re: Strange problem with default screenshot directory on network drive

« on: April 29, 2013, 12:39 AM »

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 ;-)

13

Screenshot Captor / Strange problem with default screenshot directory on network drive

« on: April 28, 2013, 01:13 AM »

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?

14

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: March 29, 2013, 07:26 AM »

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...

15

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: March 29, 2013, 05:34 AM »

works for me too, 64-bit Windows 7 Pro

Filename is

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

16

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: March 28, 2013, 11:16 AM »

OS is 64-bit Windows 7 Pro

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

What are you running?

17

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: March 28, 2013, 09:59 AM »

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...)

18

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: March 28, 2013, 07:59 AM »

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.

19

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: February 20, 2013, 04:18 AM »

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?

20

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: February 20, 2013, 12:19 AM »

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

Wrong URL, I would say 

21

DcUpdater / Re: DcUpdater reports incorrect version of installed app

« on: February 19, 2013, 09:52 AM »

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.... 

22

DcUpdater / Re: DcUpdater reports incorrect version of installed app

« on: February 19, 2013, 07:18 AM »

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: https://www.donation...hotcaptor/index.html
DcUpdate File: C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate
Remote Version File: https://www.donation.../pad/versioninfo.xml
Remote Update File: https://www.donation...nshotCaptorSetup.exe


3.08.01 is reported as:

ScreenshotCaptor:
WebPage: https://www.donation...hotcaptor/index.html
DcUpdate File: C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor\ScreenshotCaptor.dcupdate
Remote Version File: https://www.donation.../pad/versioninfo.xml
Remote Update File: https://www.donation...nshotCaptorSetup.exe

How do I get things back straight?

Isn't a bug still lurking somewhere?

23

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: February 19, 2013, 07:12 AM »

you probably meant "if I can improve that" 

24

Screenshot Captor / Re: "Incorrect" filename for "Grab selected region"

« on: February 19, 2013, 07:02 AM »

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).
 

25

Screenshot Captor / "Incorrect" filename for "Grab selected region"

« on: February 19, 2013, 06:47 AM »

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?