@GillMcC: Thanks for describing the problem as you experience it in your workflow. That makes sense to me now (my apologies, but I didn't understand it very well, before).
I have tried to replicate the problem - using Excel as you do - on my own laptop, but cannot.
My display details - from
System Information (
Summary --> Advanced window - Hotkey is Ctrl+Alt+S):
Item -------------Value----------------------------------
Name Intel(R) HD Graphics 520
PNP Device ID PCI\VEN_8086&DEV_1916&SUBSYS_80A4103C&REV_07\3&11583659&0&10
Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description Intel(R) HD Graphics 520
Adapter RAM 1.00 GB (1,073,741,824 bytes)
Installed Drivers igdumdim64,igd10iumd64,igd10iumd64,igd12umd64,igdumdim32,igd10iumd32,igd10iumd32,igd12umd32
Driver Version 21.20.16.4727
INF File oem125.inf (iSKLD_w10_DS section)
Colour Planes Not Available
Colour Table Entries 4294967296
Resolution 1366 x 768 x 60 hertz
Bits/Pixel 32
Memory Address 0x92000000-0x92FFFFFF
Memory Address 0xA0000000-0xAFFFFFFF
I/O Port 0x00005000-0x0000503F
IRQ Channel IRQ 4294967289
Driver c:\windows\system32\driverstore\filerepository\ki124769.inf_amd64_e5e7af49c5a8fe4b\igdkmd64.sys (21.20.16.4727, 10.58 MB (11,093,992 bytes), 2017-10-12 10:44)
Name NVIDIA GeForce 940M
PNP Device ID PCI\VEN_10DE&DEV_1347&SUBSYS_80A4103C&REV_A2\4&2155344C&0&00E0
Adapter Type GeForce 940M, NVIDIA compatible
Adapter Description NVIDIA GeForce 940M
Adapter RAM (2,147,483,648) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvldumd.dll
Driver Version 22.21.13.8569
INF File oem121.inf (Section028 section)
Colour Planes Not Available
Colour Table Entries Not Available
Resolution Not Available
Bits/Pixel Not Available
Memory Address 0x93000000-0x93FFFFFF
Memory Address 0x80000000-0x8FFFFFFF
Memory Address 0x90000000-0x91FFFFFF
IRQ Channel IRQ 4294967285
Driver c:\windows\system32\driverstore\filerepository\nvhm.inf_amd64_f0b2a5e1e71031b3\nvlddmkm.sys (22.21.13.8569, 14.90 MB (15,620,208 bytes), 2017-10-16 01:18)
The key measures there for my laptop display are presumably:
- Resolution 1366 x 768 x 60 hertz
- Bits/Pixel 32
...compared to yours for the
HP Spectre 360 with a high resolution monitor, which are:
- Resolution 3840 x 2160 x ?? hertz
- Bits/Pixel ??
...the implication being that your screen clips of the same bit of screen display will contain more than twice as much data as mine are likely to contain.
So you are probably stuck with it, unless someone is able to offer up a fix.
An example of the times where this (excessive image size) is a problem for me is when I am inserting images for posts into a DCF discussion thread.
I have a relatively speedy workaround for this. I use
irfanview in my workflow to rapidly resize the image (as necessary), without it delaying/interrupting my workflow.
This is described here:
Re: Modify your screen capture/management tools for optimum efficiency of use.As you will see, it all hinges around making use of
CHS (Clipboard Help & Spell), to realise the potential optimum. Once the penny dropped in my head, all I had to do was to reorganise my workflow to achieve that result.
I say "once the penny dropped", because
it had taken me some time to realise what was possible and how it could save my time and improve my overall management of screen captures, and
yet it had been staring me in the face for ages.It's very simple, but I guess it's not really all that obvious.