Topics - sba [ switch to compact view ]

Pages: [1] 2 3 • next
1
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?



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

3
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?

4
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?

5
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?

Pages: [1] 2 3 • next
Go to full version