Talk:KDEConnect: Difference between revisions
No edit summary |
(→Page broken: new section) |
||
| Line 6: | Line 6: | ||
This is not the right place to discuss - chances that a KDEConnect developer will notice a feature request here is not great. The best way is probably to make a feature request on [https://bugs.kde.org bugzilla]. | This is not the right place to discuss - chances that a KDEConnect developer will notice a feature request here is not great. The best way is probably to make a feature request on [https://bugs.kde.org bugzilla]. | ||
[[User:Claus chr|Claus chr]] ([[User talk:Claus chr|talk]]) 08:22, 31 May 2023 (UTC) | [[User:Claus chr|Claus chr]] ([[User talk:Claus chr|talk]]) 08:22, 31 May 2023 (UTC) | ||
== Page broken == | |||
If I go to https://userbase.kde.org/KDEConnect, I get a pink box with the following error | |||
> [fe207a0d9d835c0ef7a8e13a] 2024-04-05 21:21:15: Fatal exception of type "TypeError" | |||
Revision as of 21:22, 5 April 2024
KDEConnect is still missing a very useful feature, luckily already implemented in GSConnect: Dial-up. When the PC user clicks on a "tel:" hyperlink, and this link type is associated with " KDEConnect", then it should, like GSConnect, transfer the phone number mentioned in the link to the smartphone dial-up application, display it and stay waiting for the push on the (green) dial-up button. I hope that, because this feature exists already in GSConnect, copying the code into KDEConnect would not be a big deal and can hence be quickly implemented. PS. I'm not sure this is the right place to discuss this. Please advice.
This is not the right place to discuss - chances that a KDEConnect developer will notice a feature request here is not great. The best way is probably to make a feature request on bugzilla. Claus chr (talk) 08:22, 31 May 2023 (UTC)
Page broken
If I go to https://userbase.kde.org/KDEConnect, I get a pink box with the following error
> [fe207a0d9d835c0ef7a8e13a] 2024-04-05 21:21:15: Fatal exception of type "TypeError"