kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

Hi Mark,

SetProcessDpiAware (Now SetProcessDpiAwareness) can be overidden by
including a manifest that says the app is not DPI aware - and
wxWidgets with bitmap icons certainly isn't DPI aware - god knows why
they thought they were!

Anyway, I've attached a manifest file which may or may not help you
out - but give it a go, it's the correct (MS) way of setting the DPI
awareness anyway and you can just sit it alongside the exe as far as
I'm aware...

Best Regards,

Brian.


On 28 November 2015 at 21:23, Mark Roszko <mark.roszko@xxxxxxxxx> wrote:
> KiCad is graphically really broken on high DPI screens like my Surface
> Book and Surface Pro. (I literally just got a Book a few days ago so I
> never knew)
>
> On the high DPI display, it gets really bad with say the pcbcalculator
> where the images are tiny and unreadable.
>
>
> But if anything should be a "blocker" we should commit the change I
> suggested here to at least enable GAL to function on high DPI:
> https://bugs.launchpad.net/kicad/+bug/1519590
>
>
> Cairo is also broken but I haven't had to the time to debug what is
> bugging it out.
>
> Windows is supposed to be able to scale UI (which it does, everything
> else that I have that isn't KiCad functions perfectly, QT apps, etc),
> from what I am reading wxWidgets was setting a flag that it was DPI
> aware and thus Windows doesn't scale UI. In 3.1.x they apparently
> removed it but right now on 3.0.x I am not sure what is going on.
>
>
>
> High DPI screens are only going to get more common, if we want to push
> off fixing it for next year then its fine. But the surfaces are really
> exploding in popularity :3
>
>
>
>
>
> On Sat, Nov 28, 2015 at 3:03 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>> If there is any reason not to roll out the stable release tomorrow,
>> speak now or forever hold your peace.  I will roll it out tomorrow
>> evening assuming there are no serious bugs between now and then.  If you
>> have any last minute bug fixes, please submit or commit them.
>>
>> If you have any developers that need to be added to the credits in the
>> about dialog, please make list with the authors name and email address
>> and send them to me directly to avoid posting email addresses to the
>> mailing list.  I will add them to the about dialog before I roll out the
>> stable release.  Please keep in mind that credits should be given to
>> developers who have contributed more than just a couple of patches.
>>
>> For repo maintainers, I am going to use tag "4.0.0" to tag the product
>> repo.  Please use the same tag so packagers only need to define a single
>> tag in their build scripts.
>>
>> Hopefully all goes well and tomorrow we will have a new stable release.
>>
>> Cheers,
>>
>> Wayne
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
> Mark
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

Attachment: kicad.exe.manifest
Description: Binary data