I'm wondering if this could be somewhat possible.
It would involve hacking and patching VB6 (hopefully just in memory so the runtime DLLs do not need to be touched on disk).
This question is intended to the ones that have knowledge exploring the VB6 internals (The Trick, wqweto...).
The idea is that VB6 already uses Single types for al twips based properties, but the "only" problem is that the twips-per-pixel calculation is somewhere rounded to integers.
This, as we all know, cause problems is some DPI settings, that are used more and more as time goes on. And if ultra-hight DPI monitors become common, at some point it will be a major issue for VB6 programs. And it will most probably happen, the only question is when.
The idea of the question is if it could be feasible to find where this rounding occurs and correct it (surely in more than one place, but probably not many).
It would involve hacking and patching VB6 (hopefully just in memory so the runtime DLLs do not need to be touched on disk).
This question is intended to the ones that have knowledge exploring the VB6 internals (The Trick, wqweto...).
The idea is that VB6 already uses Single types for al twips based properties, but the "only" problem is that the twips-per-pixel calculation is somewhere rounded to integers.
This, as we all know, cause problems is some DPI settings, that are used more and more as time goes on. And if ultra-hight DPI monitors become common, at some point it will be a major issue for VB6 programs. And it will most probably happen, the only question is when.
The idea of the question is if it could be feasible to find where this rounding occurs and correct it (surely in more than one place, but probably not many).