Turns out that setting the desktop env isn't enough we also need to
manually ensure kwalletd is started. As we can't tell steam to run
multiple commands, people will need a small wrapper script that
does this.
Apparently on windows `Qt.inputMethod.visible` is always true when an input method is installed. Also on windows even after removing the check enter is still consumed by the input method, not nheko.
* First draft of unread line feature.
* Minor visual fix.
* Removed unnecessary ternary operator.
* Extended unread line functionality to work on minimised window or focusing another window.
* Fix for unread line not showing when last read message is hidden.
* Minor performance improvement. Fix for misbehaving event2order DB at application start.
* Fix for possible performance issues when user has joined a large number of rooms.
* Fix for breaking macos and clazy builds.
* Changed on windows focus function to refresh unread line if room is unread.
* Unread line is removed when user sends a message.
* Linting.
* Fixed unread line to work in standalone room windows.
* Switch isRoomUnread for index 0.
* Merged try/catch blocks.
* Fix for crash on opening a room invite.
* Call fullyReadEventId function when used instead of storing it and passing it through.
* Function that was meant to sync the unread line was relying on an async function, oops.
* Linting again.
* More linting...
* Minor changes.
Nheko is very chatty in its log output, generating log noise (which
complicates diagnostics) and needless disk writes (which affect power
consumption and SSD life). This patch introduces command line options
and environment variables to control log levels and output type.
The old --debug command line option still works, at least for now.
It is overridden by the new command line options when they are used.
Partially addresses #665.
This reverts commit e6b6a76437,
because it broke compatibility with clang-format 11 (which is current
on some linux distros) and because it didn't achieve its original
goal. See PR #1166 for discussion.
This addresses a few problems with reaction colors:
- The state-checking conditionals for reaction text, background, and border
were inconsistent, making it difficult to choose colors for each state
(normal, hovered, and self reactions) that worked well in all themes.
- The QPalette::Highlight color was being misused as a text/foreground color.
This color role is intended for background areas. It has little contrast
against the background in themes like KDE Plasma's Breeze High Contrast,
so using it for text and icons makes those things difficult to read.
https://doc.qt.io/qt-5/qpalette.html#ColorRole-enum
- The reaction border was drawn in the same color as normal text, making it
so bright in some dark themes that it distracted from reading nearby text.
FixesNheko-Reborn/nheko#1159
Nicolas Werner
Marcus
Jason Volk
q234rty
Sebastian Spaeth
Weblate
Hiers
Forest
Zirnc
Hiers
Forest