LineEdit Widget Error
https://github.com/slint-ui/slint/assets/111585117/8f8262e6-bdb0-43af-9ead-f223fab8ac06
Hello. Nice to meet you.
I am a Korean who is studying rust and slint.
What I'm curious about is
I typed data on the keyboard in the LineEdit window, but it doesn't appear.
However, when you click and adjust the running window sizing, you will see the text you entered in the LineEdit window.
Is it a bug?
I also noticed this issue, instantiate LineEdit as a Focusfocus object, and then focus on it
So far, this is how I resolved it
But it will always gain focus, even if other elements are clicked on
export component AppWindow inherits Window{ forward-focus: Focusfoo;}
What troubles me now is, I created a TextEdit that automatically fills in a string of keyboard characters when switching from the desktop window, Do you have this phenomenon @chlghdwns
Could you check the size of the text input? It seems to me that it is just too small to show the text.
What troubles me now is, I created a TextEdit that automatically fills in a string of keyboard characters when switching from the desktop window, Do you have this phenomenon @chlghdwns
We have confirmed that if LineEdit is designated as forward-focus first, the bug will disappear.
Could you check the size of the text input? It seems to me that it is just too small to show the text.
I didn't adjust the text size, but just created LineEdit and entered it right away.
I don't know if I understood you correctly
It looks like something is wrong and the window don't refresh.
I couldn't reproduce on X11 with the winit backend. Maybe it is Windows specific?
@chlghdwns 안녕하세요. 한국인 Slint + Rust 사용자입니다. 혹시 Windows 10 사용중이신가요? 저도 비슷한 버그를 확인했습니다만, 오직 Windows 10에서만 문제가 발생하고 있습니다(11에서는 문제가 없었습니다).
참고로 제 경우에는 Window의 init callback에서 아래의 내용을 추가하는 걸로 문제를 해결했습니다.
export component AppWindow inherits Window {
init => {
connection-info.focus();
}
}
@ogoffart @teminian
네. 저는 윈도우 10에서 구현했을때 이렇게 작동이 안되었습니다. 11에서는 정상작동한다고 하니 아마도 윈도우 10이랑 11의 차이에서 구현의 문제가 있는거 같네요
Yes. When I implemented it on Windows 10, it didn't work like this. It says it works fine on 11, so maybe there's a problem with implementing it on the difference between Windows 10 and 11