octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54607] Native (KDE) open/save dialogs are not


From: Kai Torben Ohlhus
Subject: [Octave-bug-tracker] [bug #54607] Native (KDE) open/save dialogs are not used
Date: Wed, 14 Nov 2018 15:39:30 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36

Follow-up Comment #41, bug #54607 (project octave):

Thank you for all the feedback.

Comment #36: Now I really tried a clean installation to /usr/local, removed
everything in my home directory, especially the folder ~/.config/octave with
qtsettings (I almost stick to the default settings anyway...) But no change
:(

One observation here: when the starting first time save as-dialogue hangs (~5
minutes), or at any subsequent call (1 second), a process of 

/usr/lib64/qt5/plugins/kf5/kio/file.so

starts and vanishes some time after closing the dialogue.

Comment #39:

> ... using Gtk or non-native Qt dialogs in KDE is a pain in comparison to the
native dialogs. I think any KDE user would say similarly. 

> I really hope this improvement is not reverted. I also hope remaining issues
are fixed, of course. 

I agree with you completely, too, and want them to work.  But it is not the
case for me, so I propose an option to opt-in non-native-dialogues in the hope
this option becomes deprecate in a near future.

Comment 40: Even nothing to win here.  I tried to copy and paste the demo code
from the tutorial (disregarding any functionality) from the official tutorial
[1] into Octave [2] and recompiled.

It is like witchcraft: The stand-alone tutorial works like a charm, in Octave
[2] the very same code causes this hangs.

[1]
http://doc.qt.io/qt-5/qtwidgets-mainwindows-application-mainwindow-cpp.html
[2]
https://hg.savannah.gnu.org/hgweb/octave/file/edc02d5eeac6/libgui/src/m-editor/file-editor-tab.cc#l2178

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54607>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]