Page 2 of 2

Re: file open/save dialogue with Alzheimers

Posted: Tue Nov 19, 2019 8:55 pm
by freman
Well I don't regard it as solved. Linking in an outside dlg lib is a work around which does nothing to redress the short coming of the internal qt dialogues I highlighted.

The FC dialogue behaviour seems seriously deficient and I don't recall qt4 build being like this. It is striking how inefficient it is compared to what I was used to on the qt4 master builds I was using this summer. It is unfortunate to see software going backwards as it moves on to newer and presumably more fully featured versions.

Re: file open/save dialogue with Alzheimers

Posted: Wed Nov 20, 2019 1:51 pm
by DeepSOIC
Yea, Qt5 feels like a step back sometimes. Reminds me of all the struggle I had with gesture nav style. With qt4, pretty much no gesture support, so I rolled my own relatively painlessly (but windows-only). With qt5, there is, but it's really broken, which made me jump hoops to make it work.

Then that radeon driver incompatibility.
Also, some icons don't render as nicely.
Also PySide2 problems, I had trouble accessing QApplication singleton.

Re: file open/save dialogue with Alzheimers

Posted: Wed Nov 20, 2019 3:09 pm
by freman
Yes, I had bunch of PySide2 errors earlier. I didn't have time to pay any more attention to it.

FC does seem more stable here on qt5/py3 for the moment : only a couple of crashes, compared every 5min before !! Maybe qt4 builds had degraded because no one on the team was using it any more and were not testing the "default" qt4 builds.

Do you know whether the last used list is under API control or do we just have to put up with what it does ? qt4 seemed very sensible and I rarely had any complaint. Is this degradation during porting FC to qt5 or degraded out-of-the-box functionality inherited from qt libs?

Is it possible to have a second instance of the dialogues as I suggested, or is there just one global one served up on demand? I think font choices needs to be treated as a separate situation to user's own files. Polluting the recently used path dropdown between the two serves neither need very well.