[kio-extras] [Bug 411291] filenamesearch is very slow

2020-01-04 Thread Postix
https://bugs.kde.org/show_bug.cgi?id=411291 Postix changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=411291 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Mark
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #8 from Mark --- (In reply to Kai Uwe Broulik from comment #7) > #include "slavebase.moc" at the end and it should just work Ha, smart! Oke, so I've got that to work somewhat, but this isn't easy by far. The tricky thing is the slot

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #7 from Kai Uwe Broulik --- #include "slavebase.moc" at the end and it should just work -- You are receiving this mail because: You are watching all bug changes.

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Mark
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #6 from Mark --- (In reply to Kai Uwe Broulik from comment #5) > It surely won't change ABI because it's the Private part. The only downside > I can see is some overhead of QObject creation? But then, how many of those > objects will we

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #5 from Kai Uwe Broulik --- It surely won't change ABI because it's the Private part. The only downside I can see is some overhead of QObject creation? But then, how many of those objects will we have anyway? -- You are receiving this

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Mark
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #4 from Mark --- (In reply to Kai Uwe Broulik from comment #3) > You could make SlaveBasePrivate a QObject. Hmm, i wonder if that's acceptable? Well, i can try if it works at all ;) -- You are receiving this mail because: You are

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #3 from Kai Uwe Broulik --- You could make SlaveBasePrivate a QObject. -- You are receiving this mail because: You are watching all bug changes.

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Mark
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #2 from Mark --- (In reply to Kai Uwe Broulik from comment #1) > Obvious solution: listEntries handling in a thread in SlaveBase :P Exactly my thought! And i actually have a threaded version - somewhat - working here locally, but that on

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=411291 --- Comment #1 from Kai Uwe Broulik --- > You will get the entry as soon as there is a new match (triggering the 300ms > interval) or till finished() is called. That is also an issue if you enter a folder with a slow mount inside. KIO goes like:

[kio-extras] [Bug 411291] filenamesearch is very slow

2019-08-26 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=411291 Kai Uwe Broulik changed: What|Removed |Added CC||fa...@kde.org, |