Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Chat text area cursor activates on an inactive window. #437

Open
Chiitoo opened this issue Jan 13, 2025 · 1 comment
Open

[Bug]: Chat text area cursor activates on an inactive window. #437

Chiitoo opened this issue Jan 13, 2025 · 1 comment
Labels
bug Bug fix for the user, not a fix to a build script
Milestone

Comments

@Chiitoo
Copy link

Chiitoo commented Jan 13, 2025

Contact Details (e.g. Tox ID or email)

No response

qTox Version

v1.18.2-1-gc3922d64

Commit Hash

c3922d6

Toxcore Version

0.2.20

Qt Version

6.8.1

Steps to reproduce

  1. Start qTox.
  2. Enable User Interface / Contact list / Multiple windows mode.
  3. Enable User Interface / New message / Open window.
  4. Open a chat with a contact.
  5. Make the window inactive by activating some other application window.
  6. Receive a message to the aforementioned chat window.
  7. Observe the blinking text cursor activating even though the window itself is still not the active window.

Observed Behavior

Cursor in the text area appears and starts blinking, as if the window was activated.

Expected Behavior

Cursor in the text area does not appear and start blinking until the window is activated.

Reproducibility

Always

Operating System

Other (please specify)

Operating System version/distro/name/etc.

Gnetoo Linux and Windows

Relevant log output

No response

@Chiitoo Chiitoo added the bug Bug fix for the user, not a fix to a build script label Jan 13, 2025
@iphydf
Copy link
Member

iphydf commented Jan 13, 2025

Even worse for me. I tested this with Multiple windows mode off, but opening a chat in a separate window (right click on the chat in the list, open in new window). Now, I can observe this behaviour, but also the window gets resized to some default value. Always the same. If the window was small at first, it'll be bigger. If it was bigger, it'll be smaller.

@iphydf iphydf added this to the v1.18.x milestone Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug fix for the user, not a fix to a build script
Development

No branches or pull requests

2 participants