Bug 24013 - arduino GUI unusable on HiDpi screens and old, please update
Summary: arduino GUI unusable on HiDpi screens and old, please update
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Yann Cantin
QA Contact:
URL: https://www.arduino.cc/en/Main/Releas...
Whiteboard: MGA7TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-15 18:05 CET by Christian Lohmaier
Modified: 2020-01-14 22:20 CET (History)
3 users (show)

See Also:
Source RPM: arduino-1.6.5-5.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Christian Lohmaier 2018-12-15 18:05:41 CET
Description of problem:
Arduino-IDE's UI in the version shipped with Mageia currently (1.6.5) doesn't have any scaling functionality, so on high-dpi screens the actual editor is scaled 100%, while the rest of your desktop might be scaled 200% or more, resulting in tiny/unusable text.

Later versions of the IDE (starting with 1.6.8 - released in March 2016) provided a setting in preferences to adjust the scaling. (see release notes in URL)

Please update to current 1.8.x version. Since 1.8.6 it should be able to auto-detect a proper value ~reliably.
Comment 1 Marja Van Waes 2018-12-16 16:52:13 CET
Assigning to the registered maintainer, CC'ing all packagers collectively, because I don't think I've seen Yann Cantin since 2016.

Assignee: bugsquad => yann.cantin
CC: (none) => marja11, pkg-bugs

Comment 2 Morgan Leijström 2019-01-14 16:37:04 CET
Yes the menu text are really tiny, and nonaliased, so ugly. Some words we have to guess.  Anybody know when 1.9.0 is out? It have been in beta about a year... Could be good to have in mga7.

CC: (none) => fri

Comment 3 Morgan Leijström 2020-01-14 22:20:46 CET
Latest upstream stable is 1.8.10

I suggest to update.

Whiteboard: (none) => MGA7TOO
Summary: arduino GUI unusable on HiDpi screens => arduino GUI unusable on HiDpi screens and old, please update


Note You need to log in before you can comment on or make changes to this bug.