QuasselDroid-ng issueshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues2022-01-10T05:16:58Zhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/242Indicate Here/Away presence when viewing query/PM2022-01-10T05:16:58ZShane SynanIndicate Here/Away presence when viewing query/PM### Discussion
Quasseldroid should show some sort of "Here/Away" presence indication when viewing a query/private message. This would make it easier to tell if the person you're talking to has gone away in the middle of writing a long ...### Discussion
Quasseldroid should show some sort of "Here/Away" presence indication when viewing a query/private message. This would make it easier to tell if the person you're talking to has gone away in the middle of writing a long message, etc.
### Ideas
* A green circle/yellow triangle/gray X/whatever somewhere near the buffer name
* Mimics Quassel desktop
* Should follow Material design/icons
* Italicize the buffer name for users that are away
* Might be easier and more obvious, but might not look nice - not sure
* Something else..?1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/240Query with services cause unneeded notifications2022-01-10T05:17:08ZJim RamsayQuery with services cause unneeded notificationsIf I'm in a query chat with an IRC service, such as `/query nickserv` and say `help`, I get a flurry of notifications even though I'm in the chat buffer where those messages are coming in.
I don't need or want a notification for message...If I'm in a query chat with an IRC service, such as `/query nickserv` and say `help`, I get a flurry of notifications even though I'm in the chat buffer where those messages are coming in.
I don't need or want a notification for messages I'm actively reading.1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/238Pressing Up arrow key clears current/unsent message without saving it to mess...2022-01-10T05:17:20ZShane SynanPressing Up arrow key clears current/unsent message without saving it to message history### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message ...### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message in the input history)
4. Type another, different message, but don't send it
5. Press the Up arrow key
6. Observe the results
7. Press the Down arrow key
8. Observe the results
### Expected
* After pressing the Up arrow, the current message is replaced with the most recently sent message
* After pressing the Down arrow, the most recently sent message is replaced with the unsent, still-being-composed message
This matches the behavior of Quassel desktop.
### Actual
* :heavy_check_mark: After pressing the Up arrow, the current message is replaced with the most recently sent message
* :x: After pressing the Down arrow, the most recently sent message is replaced with.. **nothing - the unsent, still-being-composed message is now lost**
### Details
Quasseldroid [v1.3.3](https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/b622ad63056b6054b06e09f8e1f1ef2b0c3aaf9a )
Using a USB keyboard with the USB OTG adapter that comes in the Pixel box, on Android 11, Pixel 4 XL.
*Priority is set to high due to the potential to lose chat messages in the middle of writing them on ChromeOS or with a USB/Bluetooth keyboard. This may be a smaller impact, though.*1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/237Up/down arrow keys don't move cursor in multi-line message edit mode2022-01-10T05:17:24ZShane SynanUp/down arrow keys don't move cursor in multi-line message edit mode### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message ...### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message in the input history)
4. Expand the message input box to switch to multi-line edit mode
5. Type a long enough message that it wraps across several lines (e.g. copy-paste a few words)
6. With the input caret/cursor on the bottom, press the Up arrow key
7. Observe the results
### Expected
The input caret/cursor navigates upwards through the text, as happens with e.g. QKSMS on Android or Quassel desktop and Kate on KDE.
Only when the input caret/cursor is at the very top of the message (or anytime in single-line edit mode) should the message history be accessed.
### Actual
Quasseldroid interprets the up arrow as a request to switch to the message history, despite being in multi-line edit mode.
### Details
Quasseldroid [v1.3.3](https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/b622ad63056b6054b06e09f8e1f1ef2b0c3aaf9a )
Using a USB keyboard with the USB OTG adapter that comes in the Pixel box, on Android 11, Pixel 4 XL.
*Feel free to edit the priority as desired - I'm not sure how many folks use Quasseldroid with a keyboard - ChromeOS + USB/Bluetooth keyboards on Android, possibly?*1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/233Use Tabular Numbers instead of Monospace for the time2022-01-10T05:18:15ZJanne Mareike KoschinskiUse Tabular Numbers instead of Monospace for the time```xml
<item name="android:fontFeatureSettings">tnum</item>
``````xml
<item name="android:fontFeatureSettings">tnum</item>
```1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/228Double-tap message to insert nickname re-appends nickname after every app switch2022-01-10T05:19:39ZShane SynanDouble-tap message to insert nickname re-appends nickname after every app switch## Steps
1. Connect to core
2. In `…` → `Client Settings`, under `Autocomplete`, ensure `Double tap to autocomplete` is enabled (the default)
3. Open an IRC channel and load backlog until normal chat messages are visible
* E.g. `#...## Steps
1. Connect to core
2. In `…` → `Client Settings`, under `Autocomplete`, ensure `Double tap to autocomplete` is enabled (the default)
3. Open an IRC channel and load backlog until normal chat messages are visible
* E.g. `#quasseldroid`
4. Focus the chat input box
5. Double tap a message from any user
* E.g. `Not-####` the notification bot, or `justJanne`
6. Observe the chat input box
7. Go to the home screen via the Home button/gesture
* Do not use the Back button/gesture as that will destroy the activity
8. Open Quasseldroid
9. Observe the chat input box
10. Optional: keep going to the home screen and returning to Quasseldroid, or switch apps, or lock the screen/unlock
11. Optional: to workaround the issue, switch to another buffer and back, or use the Back button/gesture to finish the activity
## Expected
Only one instance of `nickname: ` is visible, e.g. `justJanne: `.
## Actual
Every time Quasseldroid regains focus, another instance of `nickname` is appended, e.g. `justJanne: justJanne justJanne`.
## Details
Tested using Android 10 with Gboard on a Pixel 4 XL.1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/227Server Redirect Notices and User Redirect Notices should be independent2022-01-10T05:15:34ZPeGaSuSServer Redirect Notices and User Redirect Notices should be independentAs explained on IRC:
```
[12:15:49] <PeGaSuS> justJanne: I found a weird behaviour in Quasseldroid in my phone (Huawei P20 Lite). Menu > Client Settings > Message Redirection > Enable "Redirect User Notices"
[12:15:49] <PeGaSuS> Tap the ...As explained on IRC:
```
[12:15:49] <PeGaSuS> justJanne: I found a weird behaviour in Quasseldroid in my phone (Huawei P20 Lite). Menu > Client Settings > Message Redirection > Enable "Redirect User Notices"
[12:15:49] <PeGaSuS> Tap the back arrow. Menu > Client Settings > Message Redirection > "Redirect User Notices" and "Redirect Server Notices" will be enabled.
[12:15:49] <PeGaSuS> Disable "Redirect Server Notices", tap back arrow, Menu > Client Settings > Message Redirection > All redirects will be disabled
[12:17:10] <PeGaSuS> shouldn't "User Notices" and "Server Notices" be independent?
```1.6.0