Update for those watching: I have just posted a new version of the script to Invent which uses vswhere.exe to locate the installed versions of Visual Studio. I'll be abandoning this revision since IMO vswhere is the best way forward. Check it out here: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/259

In T10232#242791, @vibhav wrote:

isnt the keyboard ui, the native keyboard that is set in android?

In T10650#240171, @cubix wrote:

Alright. Are we supposed to refresh it then everytime? Or if the count of messages decreases - a workaround maybe?

In T10650#239972, @cubix wrote:

Also is this an issue of the desktop app or the android kde connect app?

In T10650#239878, @cubix wrote:

Since, I'm new, can you help me out on how to go about this issue. It would be of immense help if you can mentor me a bit.

In T10650#239900, @aniketkumar wrote:

In T10650#239889, @cubix wrote:

Does the deleting here refer to deleting for everyone or just deleting from the phone?

Deleting from the phone as well as from the SMS App's cache on the desktop.

In D17908#674690, @Petross404 wrote:

Is vswhere included when VS is installed? Unless the user explicity installs it, it shouldn't exist. Am I wrong here?

In D17908#674685, @Petross404 wrote:

Do we want to ship this with KDevelop? So that the .bat script can rely on this utility?

Actually, we have just disabled the task tracker on Gitlab because it was too easy for users to confuse with bug reports. Please keep working here until we know where to migrate :)

Although, we're migrating away from Phabricator to GitLab, so it would probably be best to open this as an issue on the KDE Connect GitLab.

This looks nice! It's probably a lot more user-friendly than just dropping the user onto a blank screen. One thing I don't like is that the onboarding screens leave out features (SMS sync, for one, but also imagine any future features which get added).

SMS app is released! There are still some rough edges. Whenever my life settles down, I'll keep polishing.

I think a new conversation button is OK, but it would be cooler to have it integrated into the current search bar.. After all, when you click the "New Conversation" button, you are just going to get a GUI panel which is basically a list of contacts with a search bar at the top!

As far as I am aware, nobody is currently working on this. Please feel free to give it a try!

In D25228#561319, @apol wrote:

Okay, makes sense to me

In D25228#560423, @asturmlechner wrote:

Is it really necessary to split KF5 dependencies in two parts here? I don't see this being done anywhere else, KF5_MIN_VERSION is always global.

Change version to 5.62 since that is the version bump after Aleix's changes to add editable contacts

Does kdeconnect.app have to be renamed to kdeconnect-app.app? Can it just stay with the old name?
( I guess I don't know what that part does. If it's not user-visible then I don't think it matters)

In D22727#513842, @dfaure wrote:

The truth is stronger than "I would not recommend".
put() in SlaveBase-derived classes is called by the KIO library (TransferJob), so you CANNOT change the meaning of the arguments. It's part of the API/ABI for all slaves, and this cannot change until KF6.

Since KNotifications on Windows is so far only used by you anyway, I say it's fine to merge. @broulik, any objections?

In D22727#510698, @brute4s99 wrote:

In D22727#505540, @dfaure wrote:

But, wait, this code is mixing "int permissions" (*) with the QFileDevice enum, that doesn't make any sense to me.

(*) this comes from KIO::put, which takes unix permissions on unix, not sure what it takes on Windows...

This doesn't match: unix permissions are octal (e.g. group read is 040 in octal), QFileDevice enum is hex (0x040).

Okay. I'm still unable to understand where/ how sftp::put() is called, or I would change everywhere it is called, to Qt way of permission extraction.

This task was completed by 779997337179e035a13b277784d40e67d4fe765e and 5dc65ee9094d12d06cbf2f96b68b4d71bebd9142

In T9676#174752, @khanaasif wrote:

Hi. I'd like to work on this one as well. But I'm new to KDE and also am a relative beginner in programming. I had a question - how should I start to dive into the code from on cgit. Thank you.

I noticed a couple of places where the cmake file could be simplified so make those changes and then let's land this monster

In D17790#506079, @Inoki wrote:

Is this good to ship?

Since there is a dylib duplicated link error caused by qca-qt5 on macOS(when we use Craft to pack KDE Connect with qml files), this will be helpful for all qml apps we have up to now :)

We have done a little bit more on mDNS on our Gitlab. Feel free to check it out! Android C++

We have done a little bit more on mDNS on our Gitlab. Feel free to check it out! Android C++

The SMS app has a runtime dependency on kpeoplevcard as well

Mostly resolved. The actual conversation shows a nice spinner when waiting for messages. The conversation list still doesn't show anything, but also I have trouble reproducing a case where it loads slowly so I think it will be okay