I noticed that the option (introduced recently) to avoid showing menu icons
does work but it does not seem to work for the contextual menu of cvpcb.
See attachment
[image: Inline image 1]
cheers
Fabrizio
On Thu, Mar 2, 2017 at 12:11 AM, Kevin Cozens wrote:
> On 2017-03-01 02:45 PM, Julius Sc
On 2017-03-01 02:45 PM, Julius Schmidt wrote:
Since it just scales the bitmaps it looks pretty terrible on this
display (even on the lowest scaled setting, 1.5).
Another approach is to have bitmaps for high DPI and scale them down to
the size needed on smaller screens.
--
Cheers!
Kevin.
http
On 3/1/2017 2:51 PM, Jon Evans wrote:
> I think in the "real world" people usually solve this by either using
> vector icons or (more commonly I think) using icon formats that store a
> number of different resolutions (16x16, 32x32, 48x48, etc) and picking
> the best one based on the screen DPI. (
On 3/1/2017 2:45 PM, Julius Schmidt wrote:
> I have a 2560x1440 14" display here. I have no idea what wxWidgets queries
> for "system dpi" (I'm running dwm), but I've tested the icon scaling
> setting.
Thank you for taking the time to test this Julius.
>
> Since it just scales the bitmaps it loo
I think in the "real world" people usually solve this by either using
vector icons or (more commonly I think) using icon formats that store a
number of different resolutions (16x16, 32x32, 48x48, etc) and picking the
best one based on the screen DPI. (This is how Android works).
The upside is tha
I have a 2560x1440 14" display here. I have no idea what wxWidgets queries
for "system dpi" (I'm running dwm), but I've tested the icon scaling
setting.
Since it just scales the bitmaps it looks pretty terrible on this display
(even on the lowest scaled setting, 1.5).
Obviously vectorised ico
On 3/1/2017 11:15 AM, jp charras wrote:
> Le 01/03/2017 à 15:05, Wayne Stambaugh a écrit :
>> I'm OK with making the menu icons a user option rather than a build time
>> option. I really don't have a preference on this issue so give the
>> people what they want.
>>
>> The bitmap scaling is a separ
Le 01/03/2017 à 15:05, Wayne Stambaugh a écrit :
> I'm OK with making the menu icons a user option rather than a build time
> option. I really don't have a preference on this issue so give the
> people what they want.
>
> The bitmap scaling is a separate issue and needs to be tested by users
> wi
I'm OK with making the menu icons a user option rather than a build time
option. I really don't have a preference on this issue so give the
people what they want.
The bitmap scaling is a separate issue and needs to be tested by users
with high dpi displays. I don't recall anyone reporting back o
Hi Guys,
I do not have a HDPI monitor but I just would like to add that in my
opinion it might be a good idea to have the option of showing and not
showing menu icons.
Regarding the resizing I have no opinion.
Cheers
Fabrizio
On Mon, Feb 27, 2017 at 4:34 PM, Wayne Stambaugh
wrote:
> On 2/21
On 2/21/2017 11:48 AM, Mark Roszko wrote:
> Ah.
>
> I had a better patch for this but I never submitted that scales the
> icons 100% to intended size regardless of the display DPI without the
> need for "size scale options".
> wxWidgets has the functions to calcuate the correct scale, it's just
>
Le 21/02/2017 à 17:48, Mark Roszko a écrit :
> Ah.
>
> I had a better patch for this but I never submitted that scales the
> icons 100% to intended size regardless of the display DPI without the
> need for "size scale options".
> wxWidgets has the functions to calcuate the correct scale, it's jus
Ah.
I had a better patch for this but I never submitted that scales the
icons 100% to intended size regardless of the display DPI without the
need for "size scale options".
wxWidgets has the functions to calcuate the correct scale, it's just
not exposed
to fix bitmaps in 3.0 but its in 3.1. I wro
Le 21/02/2017 à 16:35, Chris Pavlina a écrit :
> On Tue, Feb 21, 2017 at 04:30:11PM +0100, jp charras wrote:
>> Le 21/02/2017 à 16:05, Chris Pavlina a écrit :
>>> On Tue, Feb 21, 2017 at 02:57:18PM +0100, jp charras wrote:
[snip]
After changing an option, you have to quit and restart
Le 21/02/2017 à 16:05, Chris Pavlina a écrit :
> On Tue, Feb 21, 2017 at 02:57:18PM +0100, jp charras wrote:
>> [snip]
>>
>> After changing an option, you have to quit and restart Kicad, to take in
>> account the icon settings.
>
> I don't have time to test this right now, but... for me, this is
On Tue, Feb 21, 2017 at 04:30:11PM +0100, jp charras wrote:
> Le 21/02/2017 à 16:05, Chris Pavlina a écrit :
> > On Tue, Feb 21, 2017 at 02:57:18PM +0100, jp charras wrote:
> >> [snip]
> >>
> >> After changing an option, you have to quit and restart Kicad, to take in
> >> account the icon settings
On Tue, Feb 21, 2017 at 02:57:18PM +0100, jp charras wrote:
> [snip]
>
> After changing an option, you have to quit and restart Kicad, to take in
> account the icon settings.
I don't have time to test this right now, but... for me, this is
unacceptable. No option should require a restart. The fu
I recently had a look at the feasibility of enabling/disabling icons in menus
and changing icons
size, depending on the monitor size in pixels.
I cannot fully test myself the result of large pixels (looks bad on my
monitor), but is is intended
to be used only for HDPI monitors.
This is only a f
18 matches
Mail list logo
