The Following User Says Thank You to detronizator For This Useful Post: | ||
![]() |
2009-11-18
, 08:09
|
|
Posts: 1,348 |
Thanked: 1,863 times |
Joined on Jan 2009
@ fr/35/rennes
|
#2
|
![]() |
2009-11-18
, 09:05
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#3
|
The Following User Says Thank You to danielwilms For This Useful Post: | ||
![]() |
2010-02-15
, 01:05
|
Posts: 1,096 |
Thanked: 760 times |
Joined on Dec 2008
|
#4
|
![]() |
2010-02-15
, 16:01
|
Posts: 19 |
Thanked: 7 times |
Joined on Jan 2010
@ dallas, tx usa
|
#6
|
![]() |
2011-04-09
, 15:03
|
Posts: 1 |
Thanked: 0 times |
Joined on Oct 2010
|
#7
|
![]() |
2011-05-11
, 21:20
|
Posts: 1 |
Thanked: 0 times |
Joined on Aug 2010
@ Lleida
|
#8
|
I'm facing a weird problem.
The SDK 1.0 (and the 1.0-update1) brought us a big deal of stability. That's cool!
But there is something weird going on in the Qt area.
I have a simple browser up that I built for experimentation purpose and I'm unable to get connectivity. I didn't try to open QSockets directly, so I don't know if it's only a problem for QWebKit (that I'm using of course) or something else.
What happens his:
1) I create the QWebView
2) I load a URL (tried different of them)
3) Messages appear on the console (I'm using /scratchbox for this):
With 4.5
Didn't try yet on hardware, though.
Thanks