View Single Post
antman8969's Avatar
Posts: 64 | Thanked: 58 times | Joined on Jul 2010 @ United States
#8
Originally Posted by Joorin View Post
If you access a container directly (but I'm only assuming you do) without first checking its length, you will end up with, in the best case, odd results or, as in this case, failure. Typically, using an iterator is the safer bet since you then get well defined situations if it's, for example, an empty container.

So, your call to the QNetworkAcessManager instance didn't behave as you expected it to. Check what resources this class relies on. How do you instantiate it? What call did you do?

In regards to documentation, I'm not more in the know than you. Qt is a framework with lots of interesting things in it and quite a few hidden dependencies that you need to understand. Have a thorough look at the Qt documentation for network connections and look at the examples (one more time) and try to find if there are differences from your code.
I had thought I was instantiating them correctly, and making requests correctly (.get), which was supported by the application compiling and working fine on desktop...

I'll look further into the Qt classes... It would just really help if I knew the environmental differences between calling from command line vs calling from .desktop file


EDIT: http://bugreports.qt.nokia.com/browse/QTBUG-15004
I Think this bug may be related.

http://wiki.forum.nokia.com/index.ph...vice_to_reboot
This one too, as I have multiple instances of QNetworkAcessManger... although I don't know why sudo would fix it

Last edited by antman8969; 2011-02-21 at 19:01.