PDA

View Full Version : Need a help about QFileDialog



Achayan
26th August 2009, 13:52
Hi all

I have a issue with QFileDialog . When i am using QFileDialog.DontUseNativeDialog I am able to create shortcuts in side panel using setSidebarUrls(srtLink) . But if I am not using QFileDialog.DontUseNativeDialog in option I cant add any links to sideBar . But I cant use QFileDialog.DontUseNativeDialog in my source coz its crashing my parent application . Is any one have idea why we can add its in sideBar ..

Thanks in Advance

Achayan

Edit : I am using pyQt4 , python 2.5 , linux

yogeshgokul
26th August 2009, 14:11
But if I am not using QFileDialog.DontUseNativeDialog in option I cant add any links to sideBar.
This is clear, you cannot change OS's native dialog.



But I cant use QFileDialog.DontUseNativeDialog in my source coz its crashing my parent application.
So what, crashing is not a problem. It must be crashing for a reason.
Find out that reason, and use it.

Show some code to pin point crashing.

Achayan
26th August 2009, 14:30
here is the error

Signal: 6 (Unknown Signal)
Stack trace:
/lib64/libc.so.6 [0x7f0ae27a4280]
gsignal
abort
g_log
g_log
g_assert_warning
/usr/lib64/libgtk-x11-2.0.so.0 [0x360d8bcc0b]
/lib64/libglib-2.0.so.0 [0x7f0acf70f2bb]
g_main_context_dispatch
/lib64/libglib-2.0.so.0 [0x7f0acf711c0d]
g_main_context_iteration
QEventDispatcherGlib:: processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
/usr/local/qt-4.5.1/lib/libQtGui.so.4 [0x7f0ace17252f]
QEventLoop:: processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
QDialog::exec()
QFileDialog::getOpenFileName(QWidget*, QString const&, QString const&, QString const&, QString*, QFlags<QFileDialog::Option>)
/usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so [0x7f0acefed3ce]

yogeshgokul
27th August 2009, 05:54
I told you to show code no errors. BTW I cant see the errors even.;)

victor.fernandez
27th August 2009, 09:12
A backtrace would be more helpful. Run your application under gdb, then type "bt" when it crashes and post the results here. You will need to post some code, however.