[Win32] TextLayout.getBounds() calculates incorrect width on monitors with non 100% scaling
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Start by tracing TextLayout.getBounds() and TextLayout.setWidth() in SWT's Windows implementation, using the supplied standalone snippet to reproduce the issue at different monitor scaling levels. Compare the returned bounds and wrapping behavior under disabled and enabled autoscaling, including after moving the window between monitors. Done means the width from getBounds() keeps the text unwrapped in the reported Windows scenarios without breaking autoscaling behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
TextLayout.getBounds() method returns bad width on monitors with non 100% scaling. The code that I expect to work correctly is the following:
textLayout.setWidth(textLayout.getBounds().width)
When doing this I expect the text of the TextLayout to not wrap. But with certain font sizes and on monitors with non 100% scaling the text wraps. I've initially suspected fractional scaling values like 125%, but testing with 200% shows that the problem is present there too. I've tried to adjust the width by 1px and even by 2px, but it looks like this is not just an off by 1 error.
Note that I am testing this with 2 autoscale modes for the control:
- AutoscaleMode.DISABLED - the text is wrapped incorrectly
- AutoscaleMode.ENABLED - the text is correct initially, but broken when window is moved from to another monitor, for example from one with 125% to one with 100% scaling
To Reproduce
A standalone SWT snippet to reproduce the behavior:
package org.eclipse.swt.snippets;
import org.eclipse.swt.SWT;
import org.eclipse.swt.graphics.AutoscalingMode;
import org.eclipse.swt.graphics.Font;
import org.eclipse.swt.graphics.FontData;
import org.eclipse.swt.graphics.TextLayout;
import org.eclipse.swt.widgets.Control;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
public class TextLayoutBoundsBug {
public static void main(String[] args) {
Display display = new Display();
final Shell shell = new Shell(display, SWT.SHELL_TRIM | SWT.DOUBLE_BUFFERED);
shell.setText("TextLayoutBoundsBug");
shell.setAutoscalingMode(AutoscalingMode.DISABLED);
shell.setSize(1000, 1000);
Font font = shell.getFont();
FontData fontData = font.getFontData()[0];
createTextLayoutAt(shell, 10, 10, fontData, 42, "Reset", 0);
createTextLayoutAt(shell, 10, 80, fontData, 41, "Reset", 0);
createTextLayoutAt(shell, 210, 10, fontData, 42, "Download", 1);
createTextLayoutAt(shell, 210, 80, fontData, 41, "Download", 1);
createTextLayoutAt(shell, 510, 10, fontData, 42, "Download & Reset", 2);
createTextLayoutAt(shell, 510, 80, fontData, 41, "Download & Reset", 2);
shell.open();
while (!shell.isDisposed()) {
if (!display.readAndDispatch())
display.sleep();
}
display.dispose();
}
private static TextLayout createTextLayoutAt(Control parent, int x, int y, FontData fontData, int fontHeight,
String text,
int widthCorrection) {
Font derivedFont = new Font(parent.getDisplay(),
new FontData(fontData.getName(), fontHeight, fontData.getStyle()));
TextLayout textLayout = new TextLayout(parent.getDisplay());
textLayout.setFont(derivedFont);
textLayout.setText(text);
textLayout.setWidth(textLayout.getBounds().width + widthCorrection);
parent.addListener(SWT.Paint, event -> {
textLayout.draw(event.gc, x, y);
});
return textLayout;
}
}
Screenshots
- AutoscalingMode.DISABLED, 125% scaling. Text is wrapping:
- AutoscalingMode.ENABLED, 125% scaling. Text looks correct:
Then moved to monitor with 100% scaling. Text is wrapping again:
Exactly the same problem can be seen with 200% scaling so I am not including additional screenshots.
Environment:
- Select the platform(s) on which the behavior is seen:
-
- All OS
-
- Windows
-
- Linux
-
- macOS
I've tested this also on Linux with 200% scaling and it worked correctly. Didn't test macOS.
- Lenguaje dominante
- Java
- Estrellas
- 202
- Forks
- 206
- Merge medio
- 20 h 20 min
- PR fusionados (30 d)
- 113
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de eclipse-platform/eclipse.platform.swt
-
`SWT_AWT.initFrame` takes `(long, String)` in Java; the GTK native declares no `className` and the Cocoa native types it `const char *`Posiblemente ocupada @GreenFuze la tomó hace 4 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
eclipse-platform/eclipse.platform.swt#3665 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
eclipse-platform/eclipse.platform.swt#3546 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
eclipse-platform/eclipse.platform.swt#3428 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 75/100
eclipse-platform/eclipse.platform.swt#3336 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
eclipse-platform/eclipse.platform.swt#3718 ·
Los mantenedores suelen responder en 1 día
Todos los issues de eclipse-platform/eclipse.platform.swt
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
netshot-net/Netshot#413 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
scylladb/scylla-cdc-source-connector#350 ·
Los mantenedores suelen responder en 1 día
-
agent:working documentation enhancement go:build lane:needs-decision
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Sanne/incus-spawn#1435 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
area:shuffle bug priority:high requires-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
apache/datafusion-comet#7062 ·
Los mantenedores suelen responder en 1 día
-
help wanted testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
antonyrag/ragleap-core#786 ·
Los mantenedores suelen responder en 1 día