Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Summary display chopped
#1
cannot expand summary window.
see png


Attached Files Thumbnail(s)
   

.htm   DESKTOP-4NB88KG.HTM (Size: 168.51 KB / Downloads: 1)
Reply
#2
Are you perhaps running HWiNFO in Compatibility mode, or with custom High-DPI settings ?
HWiNFO is High-DPI aware and it should work well on such systems (using display resolution scaling), but if you change the compatibility settings, this could cause such issues.
Reply
#3
(12-30-2017, 08:22 PM)Martin Wrote: Are you perhaps running HWiNFO in Compatibility mode, or with custom High-DPI settings ?
HWiNFO is High-DPI aware and it should work well on such systems (using display resolution scaling), but if you change the compatibility settings, this could cause such issues.

No. but fixed with this setting see attached. Now grainy but not chopped.


Attached Files Thumbnail(s)
   
Reply
#4
(12-30-2017, 09:25 PM)Dasboot Wrote:
(12-30-2017, 08:22 PM)Martin Wrote: Are you perhaps running HWiNFO in Compatibility mode, or with custom High-DPI settings ?
HWiNFO is High-DPI aware and it should work well on such systems (using display resolution scaling), but if you change the compatibility settings, this could cause such issues.

No. but fixed with this setting see attached. Now grainy but not chopped.

ips monitor 1920 x 1200 n  NVidia 960 gtx win 10 pro 64 1709 rs3
Reply
#5
It should not be grainy, but sharp.
What scaling does your display use ?
Will switching the Override High DPI scaling to Application help?
Reply
#6
(12-30-2017, 09:30 PM)Martin Wrote: It should not be grainy, but sharp.
What scaling does your display use ?
Will switching the Override High DPI scaling to Application help?

1920 x 1200               125% DELL U2415
USING APPLICATION SUMMARY IS CHOPPED AS IT IS WITHOUT COMPATIBILITY USED.
NOT THAT BAD (GRAINYNESS) LIVABLE
Must be partially caused by video card as my work machine has a 2560 x 1440 at 150% monitor and does not need compatibility to display full summary.
Reply
#7
(12-30-2017, 09:30 PM)Martin Wrote: It should not be grainy, but sharp.
What scaling does your display use ?
Will switching the Override High DPI scaling to Application help?

I have the exact same problem on Windows 10 LTSB 1607
I am missing the option to set the override via context menu in compatibility tab.
So i was forced to set it via the registry.

There are 3 available options that can be set in the registry. Here is more information regarding that.
https://superuser.com/questions/1230346/...ne/1230356
https://blogs.technet.microsoft.com/mspf...prise-way/

Sideupload of screenshot, because the php code broke even though the picture size was under 500kb: https://imgur.com/a/099Je
(cropped on here)

I think this could be easily resolved by making the window sizeable (or at least an option that makes it sizeable).
It is not dpi aware on the windows but only on text. Which makes the text sharp but not viewable since the window doesn't recognize the dpi scaling.

   

My scaling is a custom scaling of 170%.


Attached Files
.dbg   HWiNFO64.DBG (Size: 93.93 KB / Downloads: 1)
Reply
#8
Well, this is really interesting because I'm not sure why this is happening..
Can you please try to revert to original options so that the summary screen will be chopped and then disable the "Remember Preferences" option in HWiNFO to see if that will fix it ?
Reply
#9
(01-05-2018, 12:24 PM)Martin Wrote: Well, this is really interesting because I'm not sure why this is happening..
Can you please try to revert to original options so that the summary screen will be chopped and then disable the "Remember Preferences" option in HWiNFO to see if that will fix it ?

Thanks for the quick reply.
Ok. I'm amazed and confused that this worked so controllable Big Grin Huh .

It is the "Remember Preferences" option that breaks the window somehow. I can replicate it as soon as I activate/deactivate it. If it is not active the window isn't chopped and works perfect.

Do you want the debug file or does that give you enough information? Curious to know, it is kinda stuck at the loading screen when "enumerating buses". Not sure if it is supposed to be that way.

   
Reply
#10
Thanks for the feedback. That means the newly introduced feature, which is preserving window position of the summary window is the problem.
But I'm quite puzzled by this because I tested this on several machines with scaling and haven't seen such a problem.
Please try the following: click the "Reset Preferences" button and then enable "Remember Preferences" again. On the first run it should be OK, then please close HWiNFO and start again. Will it be chopped now ?
Reply
#11
[quote pid='16688' dateline='1515179751']
MartinThanks for the feedback. That means the newly introduced feature, which is preserving window position of the summary window is the problem.
But I'm quite puzzled by this because I tested this on several machines with scaling and haven't seen such a problem.
Please try the following: click the "Reset Preferences" button and then enable "Remember Preferences" again. On the first run it should be OK, then please close HWiNFO and start again. Will it be chopped now ?
[/quote]

Ah. I think I found the culprit. So resetting and remembering works. Until I change the dpi again, then hwinfo "remembers" the old dpi setting since this is what it's supposed to be doing. Thus the window gets chopped.

I increased my dpi for this test to 200% after resetting and remembering at 175%. Now it gets chopped by about 25%.
I'm not sure how you would implement this feature. Hwinfo needs to somehow recognize that the dpi scaling has been changed/reset. Then I think the problem might be resolved.
Or I think if it is not used somewhere else, just not save the dpi setting and let it calculate it each time? So never remember this feature.
I'm not sure what you use to build hwinfo but within c# you could also utilize autosize/autoscale
https://msdn.microsoft.com/en-us/library...osize.aspx
https://msdn.microsoft.com/en-us/library...emode.aspx

Or of course wmi/.Net, but you might get different results with different hardware configurations.


Hope that helps Big Grin

   
Reply
#12
Ah yes, that explains it ! If you close HWiNFO with a certain DPI scaling and then change it, HWiNFO restores the window to coordinates based on previous DPI setting.
Let me think about how to solve this...
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)