topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Tuesday March 19, 2024, 3:20 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Jesper Hertel [ switch to compact view ]

Pages: [1] 2 3 4 5next
1
I have the same problem. The thumbnails only refresh if I open the screenshot folder in Windows Explorer. Then they immediately update in Windows Explorer, and then the updated thumbnails are there again in Screenshot Captor after pressing F5 in Screenshot Captor to refresh. But Screenshot Captor cannot "itself" any longer make thumbnails when taking new screenshots.

That's a pretty big problem, as the thumbnails are quite important for navigation.

I'm using Windows 10 Home (10.0.19043, i.e. 21H1).

Did anyone find a permanent solution that doesn't involve resetting all settings, including settings that have nothing to do with this?

I did install Google Drive recently – could that be the culprit? I don't remember if the problem started at that point, but it could be, since I just remember installing Google Drive during the last 4-6 months and also that the problem with Screenshot Captor appeared within the same time frame. It could also be unrelated.

2
So the only two magnification combinations that give correct workspace snapshots are:

100% internal, 100% TV
125% internal, 100% TV
-Jesper Hertel (May 06, 2016, 08:26 PM)
In other words, currently I can choose any magnification on my internal screen, but selected region capture and workspace capture only works if my TV is on 100% magnification.

I wish I had more magnifications to choose from than 100% and 125% on my internal monitor so I could test more, but Windows doesn't supply more.

3
Sadly I will have to go to bed now. As you perhaps noticed on the snapshot file names it has become rather late now here in Europe and I need my beauty sleep. :)

4
So the only two magnification combinations that give correct workspace snapshots are:

100% internal, 100% TV
125% internal, 100% TV

5
is there ANY magnification above 100% with two monitors where a workspace capture is correct?
You mean any combination where at least one of the magnifications are above 100%?

If that is what you mean, there is one and only one of those 7 combinations where the workspace capture is correct: 125% internal magnification, 100% TV magnification:
Screenshot - 2016-05-07 , 03_19_34, 125%, 100%, workspace, complete.jpg

It should be said that the only available magnification choices are:
Internal: 100% or 125%.
External TV: 100%, 125%, 150%, 175%.

That gives 8 combinations, of which 7 are combinations where at least one of the magnifications are above 100%.

6
125% internal, 125% TV, workspace capture, polar bears – incomplete:
Screenshot - 2016-05-07 , 03_10_36, 125% internal, 125% TV, workspace, incomplete.jpg

7
Switched TV background back to polar bears to make screenshots comparable, repeating some screenshots:

125% internal and 150% TV, single screen capture of internal monitor – incomplete:
Screenshot - 2016-05-07 , 03_04_22, 125% internal, 150% TV, single screen capture of internal monitor, incomplete.jpg

125% internal and 150% TV, single screen capture of TV monitor – incomplete and includes part of internal screen:
Screenshot - 2016-05-07 , 03_04_31, 125% internal, 150% TV, single screen capture of TV screen, incomplete and includes part of internal.jpg

8
One subtlety about testing this is that it may be that SC has to be restarted after making magnification changes in order to not cause spurious problems.
I actually never restarted Screenshot Captor as part of the testing. I will continue not to do that to make results comparable. But if you ask, I can restart.

is there a scenario where having the two screens at the SAME magnification still has a problem? 
Yes, for instance 125% and 125%.

Workspace capture using 125% and 125% (Windows changed the TV desktop background to horses now):
Screenshot - 2016-05-07 , 02_45_11, 125% internal, 125% TV, workspace, incomplete.jpg

And lastly, can you tell me if for example the 125+150 case above, if you do single-screen (monitor) captures, are the individual monitor captures also incomplete?
Yes, they are also incomplete.

125% internal and 150% TV:

Internal monitor, single screen capture – incomplete:
Screenshot - 2016-05-07 , 02_47_39, 125% internal, 150% TV, single screen capture of internal screen, incomplete.jpg

External TV monitor, single screen capture – incomplete and includes part of internal screen (!):
Screenshot - 2016-05-07 , 02_55_57, 125% internal, 150% TV, single screen capture of TV screen, incomplete and includes part of internal.jpg

9
To follow up on previous questions before returning to your most recent answer:

1. in the config where selected region has a problem, can i confirm that the "capture entire workspace" capture works as expected, and captures entire workspace?
I cannot confirm that, as shown in my previous post.

2. again in config where selected region has a problem, if you nevertheless trigger a selected region capture, and try to select the entire visible (zoomed) workspace, from top left to bottom right, what does the resulting image look like?

Zoom settings: 100% internal, 150% TV:

Workspace screenshot – incomplete:
Screenshot - 2016-05-07 , 02_28_38, 100% internal, 150% TV, workspace, incomplete.jpg

Trying to select entire workspace using selected region capture from upper left on internal screen to lower right on external TV (with no zoom problem this time!) – more incomplete, the lower part of the internal screen is now also missing:
Screenshot - 2016-05-07 , 02_28_57, 100% internal, 150% TV, selecting entire workspace as region, incomplete but different.jpg

10
I've been operating under the assumption that the other capture modes (capture screen, workspace) worked fine and it was just selected region that was broken.
I actually had the same assumption – apparently I never checked or noticed that until now.

11
Jesper can you go to a configuration where selected region captures give bad zoomed result, and then just try taking a normal Capture Screen capture on each monitor and post the results?
Sorry for the late reply, I have been both sleeping and busy. :)

The complete workspace screenshots are actually incomplete when the problem is there. I took these complete workspace screenshots when having my 1920x1080 TV connected (through HDMI). The internal screen is to the left, the TV is to the right. Only the last of these three screenshots is correct and complete:

125% zoom on internal screen, 150% external TV, problem is there, workspace screenshot is incomplete:
Screenshot - 07-05-2016 , 01_57_58 125% zoom on internal screen, 150% external TV, incomplete.jpg

100% zoom on internal screen, 150% external TV, problem is there, workspace screenshot is incomplete:
Screenshot - 07-05-2016 , 01_58_31 100% zoom on internal screen, 150% external TV, incomplete.jpg

100% zoom on internal, 100% on external TV, problem is not there, workspace screenshot is complete:
Screenshot - 07-05-2016 , 02_02_33, 100% internal, 100% external, complete.jpg

(I had to use lossy JPG as lossless PNG was too large, but that is hopefully not a problem in this case.)

12
But if I only connect my TV and arrange my internal monitor (1) and TV (2) like this (i.e. align their tops):
Screenshot - 05-05-2016 , 00_56_50.png

then it works, with a zoom of 150% on my TV.

So I guess my workaround is to align the tops of my internal screen and my TV.

I still don't understand why it is like that, though.

13
I tried many different arrangements of my three external monitors now, and none of the arrangements gives any problems – if both externals monitors are connected.

The problem is only there now when I connect only my TV. Then the zoom on the TV makes problems.

If I connect only my VGA connected monitor, the zoom on the internal monitor makes problems – no matter how I arrange the two monitors. Even if I put the VGA connected monitor to the right (virtually), it makes no change.

I can't find heads or tails in this.

14
When I connect my VGA monitor, it becomes the topmost screen (here it is number 2, and the TV is number 3):
Screenshot - 05-05-2016 , 00_36_00.png

And then it works.

But this works too, even though here the TV is the topmost screen:
Screenshot - 05-05-2016 , 00_37_49.png

And this works too:
Screenshot - 05-05-2016 , 00_40_30.png

So I can't quite explain why it works now when I connect two monitors…

15
First of all, I tried restarting my computer, and the problem was back :(. Or rather, the problem is there when I only connect my TV, but not when I connect both my TV and my VGA monitor.

Could it have something to do with the ALIGNMENT of the monitors?

Yes, you do have a point there! I tried using Control Panel to realign the monitors (this time actually realigning them, as opposed to the non-functional Settings "app"). And if I put the top of my internal monitor above the top of my TV, or precisely align the top of the internal monitor with the top of my TV, the problem is gone, even though the TV is set to 150%. TV is monitor number 2 here:
Screenshot - 05-05-2016 , 00_30_31.png

But if I place the top of the internal monitor just below the top of the TV, so the TV's top defines the top of the workspace, the problem is back:
Screenshot - 05-05-2016 , 00_28_16.png

Seems like perhaps the topmost screen (the screen with the topmost top) kind of defines the zoom for the entire window overlay? I don't quite understand it, though…

16
It seems to happen only on windows 10 when multiple monitors are set to DIFFERENT ZOOM MAGNIFICATIONS.

That is -- it's not a problem when multiple monitors have different resolutions, or when a zoom magnification other than 100% is used.

But Windows 10 introduced the ability to set magnification differently on each monitor, and having different magnifications on different monitors seems to be the problem.

Sadly, no, not in my case (the Asus laptop with two external monitors). On my computer, it seems to be related to HDMI versus VGA connection.

I made some more testing:

When I only connect my 1920x1080 external monitor (a normal monitor, not a TV) using VGA, no problems exist at all, no matter what zoom I choose for either of the two screens. They can be the same, they can be different, they can be 100%, they can be any percent, Screenshot Captor selected region capture works exactly as it should.

When I only connect my 1920x1080 external TV using HDMI, the problems are there if I choose anything else than 100% zoom for any of the screens (internal or TV). Only when both are 100%, selected region capture works. Otherwise the entire workspace is zoomed in when trying to capture a selected region.

When I plug in both of my external monitors, i.e. the 1920x1080 external normal monitor via VGA and my 1920x1080 TV via HDMI, I can choose any zoom for the VGA monitor if the internal monitor is at 100% and the TV is at 100%: Region capture just works. But if I change either the internal monitor zoom or the TV zoom to non-100%, selected region capture stops working (zooms in the entire workspace).

So it seems to be very much related to VGA versus HDMI. It works fine with VGA, but doesn't work with HDMI.

The VGA monitor is positioned to the left, the TV to the right, if that matters.

Okay…! :tellme: Now something weird just happened: I tried rearranging the monitor positions in ms-settings:display (Start, Run, type ms-settings:display, Enter) to see if right and left was involved. And while I was trying to get that to work, which it never did (Windows did not react to any monitor position changes at all, only in the graphics on the screen, but not "in real life"), suddenly Screenshot Captor's selected region capture started working again, even though my TV is at 150 % zoom now! In other words, Screenshot Captor's selected region capture now works perfectly with exactly my needed zoom settings.

Now I am both happy :) and puzzled :huh: . What happened?

It seems to be a Windows bug? Maybe related to Windows not being able to rearrange screens correctly using ms-settings:display?

Ah… The problem simply moved to my VGA monitor! If I change the zoom on the VGA monitor now, Screenshot Captor's selected region capture stops working again (zooms in too much). But I can change the zoom freely on my TV now.

My monitor arrangement is this now:
Screenshot - 04-05-2016 , 19_59_33.png

VGA monitor is number 2 to the left, internal monitor is number 1 in the middle, TV is number 3 to the right.

The zooms are 100%, 100%, 150%.

I am puzzled, but right now everything works on my computer. I don't really have any explanation though. I only rearranged the screens in ms-settings:display without any real effect on the rearrangement; the arrangement just fell back to the previous arrangement when I changed the zoom on any of the screens. But after that the problem moved to the other monitor, which solved my problem.

How that could help sitnik I don't know, as sitnik only has one monitor and maybe cannot get rid of the problem using my spells.

And anyway, there would still be a problem also for me if I wanted a different zoom than 100% on my VGA monitor now. I just happen not to want that.


Okay, now I tried detaching my HDMI TV. Now I am able to change the zoom on my external VGA again, and Screenshot Captor's selected region capture still works. Now I just can't change it for my internal display. :)

I plugged in my HDMI TV again, and then I had to set the zoom on my VGA monitor back to 100% to make selected region capture work. But my TV is still at 150%, without problems.

So, the problem is kind of solved now (for me), but not generally solved. And I only hope it still works after restarting my computer – I don't know.

17
I have the exact same problem, but on an Asus laptop to which I have connected an external monitor (actually, my TV) using HDMI.

I am using Windows 10, version 10.0.10586, 64 bit, Intel HD Graphics 520 (driver version 20.19.15.4331).

When I try to select a region using the mouse, everything is zoomed, probably around 150%, both the internal and the external monitor (so the external monitor becomes double zoomed). Therefore I can't use the "Capture selected Region" command at all. I have to capture the entire workspace and then select the region afterwards in Screenshot Captor. And that's a bummer since I used to capture selected regions a lot.

The normal zoom on my internal laptop monitor is 100%. The normal zoom on my TV is 150%.

The internal monitor has a resolution of 1366x768. The external TV monitor is 1920x1080.

If I set the zoom on my external TV monitor to 100%, so both screens are at 100%, the problem is gone. But then it is really hard to read any text on my TV as it is 8 feet away.

I am using Screenshot Captor 4.16.1.0.

18
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 14, 2013, 09:12 AM »
thank you for not giving up and becoming angry with frustration, as i would have done in your shoes.  your discovery may help others.
Oh, I would never be angry with such a wonderful program as Clipboard Help+Spell. :-) I use it all the time and it is extremely helpful to me! I only become sad when it is ill :(. I am so happy it recovered now! :)


However, if Jesper Hertel's PresetViews have somehow been set to do this, then I wonder whether this could be an undocumented feature in CHS
Yes, either that, or the program gets confused by some obscure error in the presetviews data due to a possible corruption and something fails that is not supposed to fail.

19
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 13, 2013, 07:08 PM »
Ahhhhh.... I found the problem!

The gremlins were in the PresetView folder!

When I deleted the PresetView folder from C:\Users\Jesper\Documents\DonationCoder\Clipboard Help+Spell and replaced it with a fresh PresetView folder from the well functioning portable version, everything worked normally again! The clips became black and not grey, and they were deletable again!

If you are curious, I attach the bad version of PresetViews. Only the files Last.preset.dock and Last.preset.grid differs in binary content from their well-functioning counterparts.

Thank you so much for helping me find the problem by asking all those good questions and make me test all the different combinations!

Maybe the problem started because I have had to brutally kill Clipboard Help+Spell so many times when it conflicted with LibreOffice and made both programs freeze (another problem that I have kind of repressed in despair). During those cold, brutal killings, the PresetView files might have been badly injured...

20
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 13, 2013, 03:58 PM »
Ok it's definitely the clip database then.
Maybe you are right, but how can that be when the problem is there too when I use a completely fresh, new, empty database (cf. comment #16 above)?

Have I already asked about the Recycle bin group in your CHS? Are there items in it?
Yep, and I can't delete them. I get a warning about permanent deletion, but when I say Yes to that, nothing happens, nothing is deleted from the Recycle bin.

Do you have a Recyle Bin group and then a group inside the Recycle bin group called "Ungrouped"?
Yep!

21
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 12, 2013, 09:43 PM »
Sorry for the late reply – we had big internet connection problems here the past few days, so no matter how much I wanted to answer, I couldn't.

do you have a configdir.ini in your installed CHS directory? if so delete it. and try again.
I did. All in it was commented out (it was a default version from 2008). But I removed it anyway and restarted Clipboard Help+Spell. No change.

copy the entire Clipboard Help and Spell directory from your installed Program Files\ directory (even the copy with the old database), and copy it to a directory in your documents subdirectory.
I did. No change. Still can't delete clips.

22
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 09, 2013, 10:49 AM »
Not even when I copy both the Database directory and the ClipboardHelpAndSpell.ini file to the installed version's directory (C:\Users\Jesper\Documents\DonationCoder\Clipboard Help+Spell) does it work.

Isn't that weird?

And the two ClipboardHelpAndSpell.exe files for the installed version and the portable version are binary identical – I just checked that. And they are both dated 2013-06-12 18:13:46 (well, one of them have the time 18:13:48).

23
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 09, 2013, 10:37 AM »
Hm, when I tried to copy the ClipboardHelpAndSpell.ini for the non-working installed version to the portable version directory, so the portable version would use that, the portable version still works and I can delete clips with that...

So then what can it be?

I would rather use an installed version of Clipboard Help+Spell than the portable one, so that I get the semi-automatic updates through DcUpdater...

24
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 09, 2013, 10:34 AM »
And here it is for the portable version that works.

25
Clipboard Help+Spell / Re: Cannot delete single clips
« on: October 09, 2013, 10:33 AM »
Here is my ClipboardHelpAndSpell.ini file for the normal installation (which does not work).

Pages: [1] 2 3 4 5next