[Solved]Open Project fails miserably in Lazarus 3.0, QT5...KIO

[cdbc]

Hi
PCLinuxOS fully updated, x11, kwin, kde - qt 5.15.6, healthy system.
@Juha:

@cdbc, I don't understand how <OtherUnitFiles... etc./> setting in a project info file (*.lpi) could affect KDE's KIO system. Do you mean you cannot change it because of the KIO problem?

I mean: I have an existing project latest touched by 2.2.6 where everything is fine, in 'project options'->'paths'->'other unit files' the different unit locations are listed properly. (btw. I have both installed side by side, 2.2.6 & 3.0)
Then I open the project in 3.0: 'project options'->'open project'->[KIO error].
Then I do: 'project options'->'close project'->'small open project form'->'open project'-> project opens, but cannot compile, because it can't find used units. Then 'project options'->'paths'->'other unit files' = '' ->[...]->KIO error.
I had a look at the lpi file before in 'kate', it was fine... and after 'kio-choke' in 3.0 the section mentioned is simply missing.
When I get a project compiled in 3.0 and run it, there are just the problems reported => slow(>3 secs) and cpu-usage-peak, but no KIO error.
I've removed all samba & nfs connections, but the problem persists in lazarus...
Regards Benny

[cdbc]

Hi
In the attached screenshot, one can see some anomalies, with regard to text - codepage  - utf16 - utf8 or something, tried to make an arrow 
Regards Benny

[dsiders]

Hi
In the attached screenshot, one can see some anomalies, with regard to text - codepage  - utf16 - utf8 or something, tried to make an arrow 
Regards Benny

The font does not have glyphs for '(' or ')'? Really? They appear in the window title bar...

[zeljko]

Yeah, that's pretty wierd 

[dbannon]

dbannon, windows postitions are about wayland implementation in qt5, that should be much better with Qt6 wayland.
KIO error raises only under KDE plasma, not under Gnome, Cinnamon etc.

Yes, zeliko, I agree with both points. And I don't use KDE myself. And my own app, tomboy-ng seems to behave quite well under KDE using Qt5.

All the same, KDE is widely used, we cannot just say it does not work well under KDE. And if these problems start appearing in apps made using LCLqt5, its going to be serious.

Davo

[JuhaManninen]

I mean: I have an existing project latest touched by 2.2.6 where everything is fine, in 'project options'->'paths'->'other unit files' the different unit locations are listed properly. (btw. I have both installed side by side, 2.2.6 & 3.0)
Then I open the project in 3.0: 'project options'->'open project'->[KIO error].
Then I do: 'project options'->'close project'->'small open project form'->'open project'-> project opens, but cannot compile, because it can't find used units. Then 'project options'->'paths'->'other unit files' = '' ->[...]->KIO error.
I had a look at the lpi file before in 'kate', it was fine... and after 'kio-choke' in 3.0 the section mentioned is simply missing.

It means the project was saved at some point with an empty "other unit files" value. Strange. It should not be saved when you just open it.
Or, did the IDE ask if you want to save a changed project and then you clicked "Yes"?

[cdbc]

Hi Juha
Nope, no asking, no saving; it just chokes on the kio and you can click cancel.
You cannot use any dialog to fill in values in the IDE and in addition, the clipboard is broken, if I copy text from, say a backup lpi to insert in the 'other units' field, I get nothing; I have to type in the unit-locations by hand, then I can work with and compile the project?!? "Here be dragons" springs to mind ...or "Gremlins". If I get this far, compilation that is, the application runs fine and the dialogs, if any, work fine, looking different but ok.fine...
It's like the IDE just throws in a blank lpi...
Regards Benny

[Josh]

just an idea, probably will not doing anything.

in 2.2.6 version can you set project compatibilty to maximum, then save project, and then try to open in laz 3.99, does it help?

[cdbc]

Hi
@Josh: It was a good idea, but sadly... No Dice!
It's like the IDE only reads the lpr file... No meta-data.
Regards Benny

[cdbc]

Hi
@zeljko & @Juha: Is it possible to swap 'dialogs.pp'? e.g.: take the one in 2.2.6 and put it in 3.0, since the 3.0 is in a writable directory...?
And the recompile Lazarus?!?
Regards Benny

[JuhaManninen]

@zeljko & @Juha: Is it possible to swap 'dialogs.pp'? e.g.: take the one in 2.2.6 and put it in 3.0, since the 3.0 is in a writable directory...?
And the recompile Lazarus?!?

I don't know. You can try.

[zeljko]

Hi
@zeljko & @Juha: Is it possible to swap 'dialogs.pp'? e.g.: take the one in 2.2.6 and put it in 3.0, since the 3.0 is in a writable directory...?
And the recompile Lazarus?!?
Regards Benny

Don't do that. Open lcl/interfaces/qt5/qtwsdialogs and inside
TQtWSFileDialog.CreateHandle() change:

  QFileDialog_setOption(QFileDialogH(FileDialog.Widget),
    QFileDialogDontUseNativeDialog, False);

to

  QFileDialog_setOption(QFileDialogH(FileDialog.Widget),
    QFileDialogDontUseNativeDialog, True);

Do same thing inside TQtWSSelectDirectoryDialog.CreateHandle(), set bool to True.
Now rebuild and it'll work ok with normal Qt5 dialogs.

[zeljko]

I've lost about 3hrs and could not find anything in Lazarus or LCL what can trigger KIO error.  It's just random and just inside IDE.
Used QT_DEBUG_PLUGINS=1 ./lazarus to check if there's something wrong in some of plugins, found exactly nothing.
Googling about such problem give me nothing .... so if anyone have any idea what's the problem here pls write.
Important thing: KIO error is written in console imediatelly after creation of QFileDialog handle, so later procs like UpdateProperties() etc does not have anything with this error.

[zeljko]

I've found where is problem !
IDE options -> Window

Uncheck all checkboxes which caption starts with "IDE title...".
Now save, try to open Open or Save dialog from IDE under KDE.
It is something about changing x11 window title (but that's what Qt does, not LCL)   
There's even bug somewhere which was opened by Alexey Torgashin about changing window titles under x11.

[zeljko]

Actually unchecking "IDE title shows project directory" fixes problem. That have something to do with KDE and it's file dialogs which uses title of app to check if it contains valid filename or path