Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: Joseph0714 on November 04, 2015, 02:21:05 pm

Title: Small Icons/Toolbar on Surface Book
Post by: Joseph0714 on November 04, 2015, 02:21:05 pm
Hi everyone. Since I recently upgraded from my old laptop to a Surface Book, I installed C::B again. Same version and everything I had on my old laptop, but now every icon on the toolbar is really small. Even hard to see, actually. I already went to Settings->Environment->View and changed the icons to normal 22x22 and it's still way to small. Any recommendations that can help me out?

I installed DevC++ to test if I had the same issue, but it's just C::B.

EDIT: I added an image below and hopefully you can notice my issue. The Surface Book has a 3000x2000 display, if that can serve as any help.
Title: Re: Small Icons/Toolbar on Surface Book
Post by: oBFusCATed on November 04, 2015, 09:15:21 pm
Do you use any scaling?
Title: Re: Small Icons/Toolbar on Surface Book
Post by: Joseph0714 on November 05, 2015, 04:15:09 am
C::B is one of the first things I installed on it. Besides DevC++, and some other programs (antivirus, Microsoft Office, and stuff), nothing should be affecting C::B, specially since the every other programs looks fine.
Title: Re: Small Icons/Toolbar on Surface Book
Post by: oBFusCATed on November 05, 2015, 07:34:50 pm
You've not answered my question - have you change the global scaling setting in control panel or not?
Title: Re: Small Icons/Toolbar on Surface Book
Post by: Joseph0714 on November 05, 2015, 09:51:33 pm
My bad. But no, I have not done that.

EDIT: The Surface Book has the size of text, apps, and others at 200%, which is the recommended setting. I changed it to 250% and 300% but still they appear to be rather small.
Title: Re: Small Icons/Toolbar on Surface Book
Post by: oBFusCATed on November 06, 2015, 12:41:30 am
Unfortunately I have no hipdi machine, where I can test things.
But looking at this topic https://groups.google.com/forum/#!topic/wx-users/GE8snC1zwPc it seems that the problem partially a wx issue and partially an application issue.