General and Desktop

Oh, I missed one requirement to close a process. Have a look at this "article on stackoverflow":http://stackoverflow.com/questions/2518160/programmatically-check-if-a-process-is-running-on-mac and try a google search on "mac check if application is running". @unclewerner: A nice side effect of the "open" command on the mac, it can handle almost everything. I'm missing it badly on my linux boxes....

Thanks, Zap. Don't sweat it too much; I may not be explaining it well, but I'm almost sure it's no big deal to do.

"Here":http://i.imgur.com/Daexy.png is a screenshot of the issue. The top is what happens the first time the list widget is shown, the bottom is what it looks like every time afterwards. Ideally I would like to have the bottom part of the screenshot occur everytime. As far as code, there's not much more than what I showed. The code iterates over all of the items to be put into the QListWidget, creating a QListWidgetItem from it, then it gets pushed into the list. Based on the screenshot, it seems like the size policy and hints are being set correctly, but just aren't being enforced until after the first time it's shown. I'm not sure what need to go in to make it work correctly.

I have solved this problem. It turns out that while I was linking in the wrong versions of the Qt dlls. I was in some cases linking in the the debug version in the release build or the release version in the debug build. Once I figured this all of the unhandled exceptions were resolved.

Thanks for the answers. they all have helped a lot.

You will most likely want your executable not to link against Qt, too. So using #ifdef on some section of the code is not enough. This is a classic job for your build system. You need to have it support two configurations, one with Qt and one without. The first builds and links the Qt files and links against Qt and the second one does not. This way you will hardly need any #ifdefs in your code (have the buildsystem define/undefine some macro based on which configuration you are in to use whenever you do need a #ifdef). How to actually do this depends heavily on the buildsystem you are using.

I solved the problem , i released the camera before the foundQrcode signal is emitted.

But my library isn't using Qt (I unchecked Qt core). In VS2008 you can change the build configuration from Win32 to x64 per project. I just realized I should have posted this in the tools section.

Hi, I didn't get any luck with my researches. Any idea anyone? Thanks

Can you not just call disconnect() from outside of the object of which you do not have source control and reconnect them via your intermediary? Or is the problem that you do not know which connections to disconnect? If so then easiest way to find out is to build modified Qt to expose the info that you need because at present I do not think that QObject exposes this information in its public interface.

(at)Gerolf: He wants to compile it with Visual Studio Add-in, but probably he doesn't know what to press/set-up... (at)jk-mk: I advise you look at function QObject::connect() with this structure: @QObject::connect(sender, signal, reciever, slot);@ Better written: "Signals & Slots":http://doc.qt.nokia.com/latest/signalsandslots.html

It was here once, where it gone?

[quote author="sigrid" date="1305810984"]./local/share/data/Trolltech/Assistant/....[/quote] Ahh... there it is! Removing that directory helped. Thanks for information!

Still looking for some more input on this matter. Anyone else have a relevant answer?

[quote author="tclin1998" date="1305739253"] My question is : Is the oldSize chunk of memory going to be recycled by Qt? Or I have to take care of it? [/quote] QImage uses "implicit data sharing":http://doc.qt.nokia.com/latest/implicit-sharing.html#implicit-data-sharing, so you don`t have to take care of it.

QPrintDialog can't be used with pdfs on Windows because it is a native print dialog and has no knowledge of Qt's PDF printer.

I changed plugin.cpp : @ #include "plugin.h" QWidget * Plugin::createWidget() { return new WidgetPlugin(); } Q_EXPORT_PLUGIN2(widgetplugin, Plugin) @ I solved the problem, now it works...

When you define own valueChanged( QString & ); you shadow original QSpinBox::void valueChanged( QString & ); That's why your slots are not invoked.

[quote author="Psychonaut" date="1305785662"]What is the result of the bug report? How long will it take to fix that problem?[/quote] That depends on how important is it deemed to be (by the maintainer of that piece of code), other priorities, and how complex the issue is, as well as how well documented and easy to reproduce the issue is. That is: there is no fixed time frame. Some bugs are never solved, some the same day.

I don't believe setting QT_BUILD_TREE correctly would resolve this as libpnp_basicictools_debug is not in any path with 'examples' in it. I've downloaded the binary version and qtdemo now runs properly.