search

godotengine / godot

Godot Engine – Multi-platform 2D and 3D game engine
https://godotengine.org
MIT License
90.23k stars 21.04k forks source link

GDScript code hint doesn't match my current typing(hint lags some distance behind) some time #53384

Closed kalenclark closed 1 year ago

kalenclark commented 3 years ago

Godot version

v4.0.dev.custom_build [66ab3ce95]

System information

Pop! OS (Linux, X11 window system)

Issue description

I just disabled some modules like mobile_vr, GDNative... I did not modify any core code, I tried Godot 3.x from official site and this problem disappeared If I type in "VideoStream", it should highlight "VideoStream" in code hint, but instead, I got only "VideoStre" highlighted in the hint as img below shows Screenshot from 2021-10-04 18-00-21

Steps to reproduce

Just open Godot 4, create a GDScript and type in "VideoStream"

Minimal reproduction project

No response

EricEzaM commented 3 years ago

Hmm, is the hint lagging, or is the completion popup just offset an incorrect amount? I'm on Win 10

See how mine is in line with the V and yours isnt? image

Although to be fair the popup being offset does not cause any issues for me. image

kalenclark commented 3 years ago

Hmm, is the hint lagging, or is the completion popup just offset an incorrect amount? I'm on Win 10

See how mine is in line with the V and yours isnt? image

Although to be fair the popup being offset does not cause any issues for me. image

I'm considering the background that indicates current matching state For example, if I type in "VideoStream", it should highlight "VideoStream" in code hint, but instead, I got only "VideoStre" highlighted in the hint as my img shows

akien-mga commented 1 year ago

I can't reproduce this on Mageia 9 Linux / KDE on X11 with either 4.0-stable or 4.1-beta3.

The issue might have been that the background rectangle was not drawn with the right size. This could be due to not properly handling DPI scaling, but for me the bug is still not reproducible with 100%, 75% or 125% editor scaling.

So I'm assuming this was fixed before 4.0-stable. Please let us know if you still reproduce the issue.