QuasselDroid-ng issueshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues2022-01-10T05:16:51Zhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/243Display inline image preview2022-01-10T05:16:51ZTrigextrigex@protonmail.comDisplay inline image previewAn inline image preview, not unlike that of another irc client like The Lounge, or like Discord's inline image previews, would be fantastic! In the IRC channel I frequent, it is very image heavy and it really is a big pain to have to man...An inline image preview, not unlike that of another irc client like The Lounge, or like Discord's inline image previews, would be fantastic! In the IRC channel I frequent, it is very image heavy and it really is a big pain to have to manually click each link, especially with multiple images in a row.
This feature would pull images from posted links in chat.
Is there any technical reason for why this hasn't been implemented yet, or has there just been no demand to?2.0.0https://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/239Reduce chat drawer grab range when expanding message compose box2022-01-10T05:17:13ZShane SynanReduce chat drawer grab range when expanding message compose box1. Connect to core, open buffer to send message
2. Expand the message box for composing messages
3. Start typing or paste a long message
4. Try to hold-select text near the left side of the screen
5. Experience fight with the chat d...1. Connect to core, open buffer to send message
2. Expand the message box for composing messages
3. Start typing or paste a long message
4. Try to hold-select text near the left side of the screen
5. Experience fight with the chat drawer
*To be filled out more if needed when not on mobile*2.0.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/236Black cursor on AMOLED theme2022-01-10T05:17:54ZPeGaSuSBlack cursor on AMOLED themeWhen editing settings on AMOLED theme, we have a black cursor on black background.
The input box while chatting works fine though, with the cursor being orange-ish.
Screenshot below:
![Screenshot_20210104_083233_com.iskrembilen.quasseld...When editing settings on AMOLED theme, we have a black cursor on black background.
The input box while chatting works fine though, with the cursor being orange-ish.
Screenshot below:
![Screenshot_20210104_083233_com.iskrembilen.quasseldroid](/uploads/c15aa3604fbec035675f72bdbae9a6eb/Screenshot_20210104_083233_com.iskrembilen.quasseldroid.jpg)2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/234Adapt font size and spacing in channel list2022-01-10T05:18:09ZJanne Mareike KoschinskiAdapt font size and spacing in channel listWe should use the new, larger presets provided by Android (16sp main, 14sp description), and additionally allow a condensed mode disabling the second line, shrinking the icons to 24dp, and reducing overall item height to 48dp (the smalle...We should use the new, larger presets provided by Android (16sp main, 14sp description), and additionally allow a condensed mode disabling the second line, shrinking the icons to 24dp, and reducing overall item height to 48dp (the smallest we can use without getting flagged by Android’s "touch target too small" warning)2.0.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/232Add means to distinguish italic formatting in CTCP ACTION (/me) messages2022-01-10T05:19:11ZShane SynanAdd means to distinguish italic formatting in CTCP ACTION (/me) messages## In brief
* Add some way of distinguishing whether italic mIRC formatting is used in a CTCP ACTION (`/me`) message
* Perhaps italicized formatting should invert to return the default-italicized text to normal?
* Or, disable use of ...## In brief
* Add some way of distinguishing whether italic mIRC formatting is used in a CTCP ACTION (`/me`) message
* Perhaps italicized formatting should invert to return the default-italicized text to normal?
* Or, disable use of italics with a setting?
## Rationale
Some folks make use of *italics* when writing their CTCP ACTION (`/me`) messages. Quasseldroid's notifications correctly show the italic formatting, but when viewing the buffer in Quasseldroid, the italics are no longer distinguishable from the default styling of CTCP ACTION messages.
This can result in losing emphasis in tone of voice or lessening creative uses of formatting in conversational messages.
## Test cases
### Steps
1. Open Quasseldroid, connect to a network
2. As another user, send this Quasseldroid client a CTCP ACTION message with italics mixed in
* E.g. `/me shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes."`
3. Observe the Android notification Quasseldroid generates
4. Observe how Quasseldroid shows the message in the buffer view
5. Optionally, observe the message in the Quassel desktop client
### Before
In steps 3 and 5, the emphasis can be seen on the word `wants`. In step 4, however, Quasseldroid does not distinguish between the italic mIRC formatted word `wants` and the rest of the auto-italicized CTCP ACTION message.
### After
In steps 3-5, it's always possible to tell some form of emphasis was placed on the word `wants`.
## Examples
### Quasseldroid notification
![Screenshot of Quasseldroid notification on Android properly showing italics in a CTCP ACTION message](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/ctcp-action-italics/Example%20-%20Quasseldroid%20notification%20view.png#v1 )
> **qdroid_examp…** \* Quasseldroid \* now
>
> shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes."
>
> `Hahaha` [auto-generated reply suggestion]
>
> `Mark Read` [button] | `Reply` [button]
### Quasseldroid buffer view
![Screenshot of Quasseldroid buffer view showing the entire CTCP ACTION message as italics](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/ctcp-action-italics/Example%20-%20Quasseldroid%20buffer%20view.png#v1 )
> **Dec 19, 2020**
>
> — *qdroid_example shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes." 04:50 PM*
### Quassel desktop
![Screenshot of Quassel desktop buffer view properly showing the italics within the CTCP ACTION message](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/ctcp-action-italics/Example%20-%20Quassel%20desktop.png#v1 )
> [4:50:14 pm] -\*- qdroid_example shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes."Future Feature Releasehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/231Make swipe left and right work from any point of the view2022-01-10T05:14:20ZToni SpetsMake swipe left and right work from any point of the viewI've noticed that it's *really* hard to get the user list or the server/channel list open with swipes because it requires you to start the swipe from the very edge of the screen.
Slack and Discord both allow you to start swiping from an...I've noticed that it's *really* hard to get the user list or the server/channel list open with swipes because it requires you to start the swipe from the very edge of the screen.
Slack and Discord both allow you to start swiping from any part of the screen (to left or right) and it will slide open either the channel or user list.
This is a small UX improvement that would make Quasseldroid immensely easier to use one handed.
Thanks!2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/230Stop marking buffer as read when full-screen message compose interface is open2022-01-10T05:19:32ZShane SynanStop marking buffer as read when full-screen message compose interface is open## In brief
* Don't mark buffers as read while the message compose interface is expanded
* Makes it possible to notice new messages, including those which would change one's reply
* Might be desirable enough to not need to become ano...## In brief
* Don't mark buffers as read while the message compose interface is expanded
* Makes it possible to notice new messages, including those which would change one's reply
* Might be desirable enough to not need to become another setting
* Tablet UI may be different (not tested)
## Example
1. Open a private message with a user you can send messages from, or visit a channel you have another account in
* Applies to both use-cases
2. Swipe up the message compose box to cover the list of chat messages
3. Imagine you're spending a long time composing a message
4. From the other user send a private message or channel highlight to this user
5. Observe how Quasseldroid handles the new message/highlight
6. Swipe down the message compose box to reveal the list of chat messages
7. Imagine you've received a message that would have changed your reply significantly
### Before
Quasseldroid marks the incoming messages as read, despite not showing the message or any notification. Time might be wasted.
### After
Quasseldroid won't mark messages as read, and won't move the marker line while the compose box is expanded. Once the compose box is no longer expanded, Quasseldroid resumes marking the active buffer as read.
### Hypothetical conversation
```
[1:23 pm] <someNick> digitalcircuit: What was your reasoning behind this change?
```
*starts writing a lengthy reply in the expanded message compose interface*
```
[1:25 pm] <someNick> digitalcircuit: Nevermind, I found your past message
```Future Feature Releasehttps://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.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/223Expanded (multi-line) message input box won't collapse with swipe down except...2022-01-10T05:20:14ZShane SynanExpanded (multi-line) message input box won't collapse with swipe down except under Send button## Steps
1. Connect to core
2. Swipe up message input box
3. Swipe down message input box by dragging `Write a message…` down
4. Observe message input box state, expanded or collapsed
5. If message input box is collapsed, swipe up m...## Steps
1. Connect to core
2. Swipe up message input box
3. Swipe down message input box by dragging `Write a message…` down
4. Observe message input box state, expanded or collapsed
5. If message input box is collapsed, swipe up message input box again
6. Swipe down message input by dragging underneath the `>` Send button
## Expected
For both steps 3 and 6, the expanded message input box collapses.
## Actual
The expanded message input box does not react to drags in step 3, but step 6 will collapse the input box.2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/219Listen to intents to restart service on app upgrade/phone reboot2022-01-10T05:20:27ZShane SynanListen to intents to restart service on app upgrade/phone reboot## In brief
* **If previously connected to core**, Quasseldroid should restart the service on app upgrades and device reboot
* * [Android 8.0+ send a broadcast `MY_PACKAGE_REPLACED`, while earlier versions send `PACKAGE_REPLACED`](htt...## In brief
* **If previously connected to core**, Quasseldroid should restart the service on app upgrades and device reboot
* * [Android 8.0+ send a broadcast `MY_PACKAGE_REPLACED`, while earlier versions send `PACKAGE_REPLACED`](https://developer.android.com/about/versions/oreo/background.html#broadcasts); both versions send `ON_BOOT_COMPLETED`
* This would be similar [to KDE Connect's handling](https://github.com/KDE/kdeconnect-android/commit/386c3cec21d64129c6dcb71fe05cb4cd0cbc2bca)Future Feature Releasehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/218Set Navigation Bar color based on theme?2022-01-10T05:21:41ZChris KrauseSet Navigation Bar color based on theme?Would it be possible to change the color of the Navigation Bar based on the current theme? I noticed that a few other apps I have do that, including QuickEdit+ which was just updated with this functionality (which is what made me think o...Would it be possible to change the color of the Navigation Bar based on the current theme? I noticed that a few other apps I have do that, including QuickEdit+ which was just updated with this functionality (which is what made me think of requesting this right now). Its most apparent on Samsung devices which by default have the Navigation bar color a light gray regardless of your dark system theme. The only way to change it is to have in app support for setting its color.Future Feature Releasehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/217reconnect jumps to latest messages2022-01-10T05:21:34Zhyperfektreconnect jumps to latest messagesIf the connection to the core is reacquired while reading in a channel, the view reloads and jumps to the latest messages.
This is undesirable especially on mobile connections, where it might happen very frequently.
Version: 1.2.24If the connection to the core is reacquired while reading in a channel, the view reloads and jumps to the latest messages.
This is undesirable especially on mobile connections, where it might happen very frequently.
Version: 1.2.242.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/249Avatar not being displayed if "<email@domain.tld> ..-. ..- -.-. -.- / -.-- --...2023-11-18T23:56:02ZPeGaSuSAvatar not being displayed if "<email@domain.tld> ..-. ..- -.-. -.- / -.-- --- ..-" is used as realnameI'm using Quassel to connect to weechat.
When setting my realname on the format `"<email@domain.tld> ..-. ..- -.-. -.- / -.-- --- ..-"` my avatar, even if set, isn't shown to myself on Quasseldroid but other clients, such as IRCCloud, a...I'm using Quassel to connect to weechat.
When setting my realname on the format `"<email@domain.tld> ..-. ..- -.-. -.- / -.-- --- ..-"` my avatar, even if set, isn't shown to myself on Quasseldroid but other clients, such as IRCCloud, are able to see it.
If I set the ralname to be `"..-. ..- -.-. -.- / -.-- --- ..- <email@domain.tld>"` then I can see my on avatar on Quasseldroid and other clients, such as IRCCloud, are able to see it too.
I don't know if the issue is the dots and dashes present in the realname that causes Quasseldroid to parse it incorrectly.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/248QD closes immediately after connecting when using Gesture Navigation2023-09-18T14:41:24ZJanne Mareike KoschinskiQD closes immediately after connecting when using Gesture Navigation