Page MenuHomeAleph Objects Inc

Scale button text
Closed, ResolvedPublic

Description

when selecting the scale option, the text protrudes from the box:

Event Timeline

karrad created this task.Sep 21 2018, 8:46 AM
karrad triaged this task as Normal priority.
karrad created this object with edit policy "Cura LulzBot Edition (Project)".

@karrad, I think this little fix can help. But the reason of such problems may be a different font DPI.

@TKostennov It brought it back into line for that box, but it appears to have had negative effects elsewhere:

Please revert this commit, the change to other headers is worse than having the scaling somewhat outside of the box

@karrad This fix does not affect any other labels and windows, it just resize scale tool window. Can you add configuration of you machine?

karrad added a subscriber: alexei.Oct 9 2018, 8:57 AM

@TKostennov Good call, this just happening on kairuku:

@alexei I got a warning about no super user access when pulling hardware, can you add anything else @TKostennov may need?

karrad closed this task as Resolved.Oct 17 2018, 7:51 AM

Going to close this one out, after checking on a few different stations it does not appear to be affecting anyone else.

alexei reopened this task as Open.Mar 7 2019, 9:44 AM

@TKostennov ,
Multiplier introduced in rU16a07bb5cde8 is causing QML binding loop error. Could you please submit a fix to master branch?

@alexei,
The original problem was associated with different dpi (especially with a low) and non-adaptive interface. The layout was changed, it seemed to be ok.
I had no problems on Debian Stretch and Ubuntu 16.04 (0.75, 1, 1.25 screen scale), but can anyone test it please?
I push it to separate branch (T3706) to avoid critical bugs in master.

karrad claimed this task.Mar 15 2019, 1:27 PM
karrad added a subscriber: TKostennov.

@TKostennov,

It looks ok for me, merged this fix to master.

alexei reassigned this task from karrad to TKostennov.Mar 21 2019, 8:38 AM
alexei closed this task as Resolved.
alexei added a subscriber: Yahuba.

@TKostennov ,
@Yahuba confirmed that there are no issues, closing this as resolved.