Fixes the issues I had with sftp hanging in certain situations. (I had to kill sftp.so in the past for accessing sftp shares again)

What do you want to know? Neptune & Netrunner aswell as others are using Calamares very succesfully.
You can find example configurations with branding here:
https://github.com/NeptuneOS/calamares-neptune
and here:
https://github.com/netrunner-desktop/calamares-desktop

In D11482#229987, @davidedmundson wrote:

...
Leszek which were the strings that renderered incorrectly?
Have you tried renaming your local .po file to see if it does fix things?

I don't have a dev account.

Fixed qDebug typo.

In D5572#104650, @ltoscano wrote:

@leszeklesner , do you have a commit account? If not, I can commit it (with you as author of course)

Updated to solution by qi437103 which implements a mousehelper to get the global mouse position so we can distinguish between mouse being inside the resultslistview or outside

In D5490#103680, @qi437103 wrote:

what about set moved variable according to global mousre position instead? I know this is possible with QCursor, but not sure if it's possible at qml side, though. I haven't looked at the code yet, but if there's c++ component, we can add a qobject derived class calling QCursor::pos(), and expose it to qml.

In D5490#103642, @davidedmundson wrote:

If I have the mouse outside the window, and then deliberately move the mouse in to select something, by design, this won't update the index the first time.

It'll fix your bug, sure - but we're knowingly introducing a different bug.

In D5490#103059, @lfurmetz wrote:

In D5490#103053, @anthonyfieroni wrote:

You can do this:

property bool moved: false
onMovedChanged: if (moved) {
    listView.currentIndex = index
}
onPositionChanged: {
...
moved = true;
}

I tried this, but onPositionChanged doesn't fire for me at all in qt 4.8.0.. Is this a bug?

Is it possible to attach the property __moved to the parent ListView dynamically, so it can be checked by all delegates?

In D5490#103049, @davidedmundson wrote:

Yes, and you have this boolean separately for each delegate.

So I can see how this supresses that initial selection in your bug report; but surely it will also supress every other normal case after that.

When we move from one delegate to another the first time from the point of view of the delegate we're moving into:

you get an onContainsMouseChanged -  _moved is falsed. We set it to true, but otherwise do nothing
we get a onPositionChanged - we set _moved to true

We're not going to get another onContainsMouseChanged unless there's a bug in Qt.

In D5490#103036, @davidedmundson wrote:

Yes, I can see what the code is doing, but I don't see how that means it works.

will be then set to true so that when you move the mouse on an item onContainsMouseChanged is called again and because __moved is now true sets the index accordingly.

When you move a mouse on an item (without leaving and entering again) why would onContainsMouseChanged be called again - unless you exited and left again.

In D5490#103017, @davidedmundson wrote:

Copying my reply from RB, to keep this in one place:

Sorry for being dim, but I don't understand how this is meant to work.