Click here to Skip to main content
15,907,183 members

Comments by Dhiraj Pallin (Top 6 by date)

Dhiraj Pallin 6-May-13 10:24am View    
Deleted
Ok I will review my practices and bring them in-line with acceptable use. Please note that my intention in pressing the Accept button for my own solution was merely an attempt to let people know that I no longer needed help. I.e. I thought it would be bad to leave my question open and unresolved if I had, in my mind, solved it. I simply didn't want people to waste their time trying to help me for a problem I had already resolved.
Dhiraj Pallin 24-Apr-13 20:23pm View    
Hmm actually. It seems that LoadIcon() is an obsolete function and I should be using LoadIconMetric() or LoadImage(). That could be the problem.
Dhiraj Pallin 18-Mar-13 19:34pm View    
Has MS changed it in recent versions of Windows without updating the documentation?
Dhiraj Pallin 18-Mar-13 11:59am View    
On even further investigation. It seems that _any_ Win32 project I create in VS 2010 has IsProcessDPIAware() returning TRUE. This seems fairly in conflict with the WinAPI documentation. Any ideas?
Dhiraj Pallin 18-Mar-13 11:35am View    
On further investigation, it seems that IsProcessDPIAware() is returning TRUE. This is strange because:
1) I have not called SetProcessDPIAware() anywhere in my program.
2) Manifest Tool -> Input and Output -> Enable DPI Awareness is set to No in Visual Studio.
3) There is nothing in my Manifest file relating to DPI Awareness
4) 'Disable Display Scaling on High DPI Settings' is not ticked in the Compatiblity properties of the executable.

So I have no idea where or how it's getting enabled.