On Saturday 29 October 2011 14:43:20 Milian Wolff wrote:
On Saturday 29 October 2011 09:25:03 Thiago Macieira wrote:
On Saturday, 29 de October de 2011 04:38:00 Milian Wolff wrote:
1) When does it manifest? Apparently when using QUrl(...)
directly, if I'm not mistaken. But what if we use
On Saturday, 29 de October de 2011 14:43:20 Milian Wolff wrote:
Right, but you should agree that relative remote adresses can only occur in
a browser context. At least in KDevelop + Kate I don't see any way for a
user to provide a relative url, so I hope that the existing codebase will
work
On Sunday, 30 de October de 2011 18:45:32 Kevin Kofler wrote:
not parse it is a URL. KUrl's constructor calls fromPathOrUrl, so it will
try to guess according to some heuristics.
No, it doesn't.
Right, it doesn't call that function, but it does try to detect a path and set
appropriately.
Thiago Macieira wrote:
2. heuristically (replacing the current KUrl::KUrl and
KUrl::fromPathToUrl): * absolute paths should be file paths
* relative paths should be file paths (!) (currently, they're URLs)
* everything with a URL scheme (protocol) should be a URL
I disagree and will not
On Sunday, 30 de October de 2011 22:34:48 Kevin Kofler wrote:
You keep claiming this is not needed or useful, but how else would you
suggest handling the use case of a network-transparent file dialog (or file
That's QUrl::fromUserInput, which makes no claim to what it considers. It's
just a
On 10/27/2011 11:35 PM, Thiago Macieira wrote:
On Thursday, 27 de October de 2011 23:17:49 Milian Wolff wrote:
On Thursday 27 October 2011 21:11:11 Thiago Macieira wrote:
On Thursday, 27 de October de 2011 13:32:51 Rex Dieter wrote:
See also,
http://bugs.kde.org/285028
( and
A Divendres, 28 d'octubre de 2011, Thiago Macieira vàreu escriure:
On Friday, 28 de October de 2011 10:41:36 Sebastian Trüg wrote:
So, to be honest, the bug already existed in your code if you're
finding these problems now. I just made it blatantly clear, and
it's been there for a year
Albert Astals Cid wrote:
Personally i find it another joke in the history of Qt, saying you
maintain API and ABI (that you do) but then making functions behave
totally different from one version to another is just plain useless.
+1
You just CANNOT change the behavior of an existing function
On Friday 28 October 2011 17:30:44 Kevin Kofler wrote:
Albert Astals Cid wrote:
Personally i find it another joke in the history of Qt, saying
you maintain API and ABI (that you do) but then making functions
behave totally different from one version to another is just
plain useless.
+1
On Friday, 28 de October de 2011 17:43:32 Kevin Kofler wrote:
Thiago Macieira wrote:
Which is quite wrong already. From Qt 4.8 on, this returns empty in all
cases, showing that you parsed the URL wrongly. It should be easier to
spot where you made the mistake because you don't have to use
On Saturday 29 October 2011 00:05:18 Thiago Macieira wrote:
On Friday, 28 de October de 2011 17:43:32 Kevin Kofler wrote:
Thiago Macieira wrote:
Which is quite wrong already. From Qt 4.8 on, this returns empty in all
cases, showing that you parsed the URL wrongly. It should be easier to
Milian Wolff wrote:
Could someone maybe explain a few points on this issue for me?
1) When does it manifest? Apparently when using QUrl(...) directly, if
I'm not mistaken. But what if we use KUrl?
KUrl uses QUrl behind the scenes for several cases.
-- rex
On Thursday, 27 de October de 2011 13:32:51 Rex Dieter wrote:
See also,
http://bugs.kde.org/285028
( and https://bugreports.qt.nokia.com/browse/QTBUG-22382 )
In Qt 4.8, QUrl.toLocalFile now seems, by design, to return NULL for urls
lacking any scheme. Discovered this the hard way figuring
Thiago Macieira wrote:
On Thursday, 27 de October de 2011 13:32:51 Rex Dieter wrote:
See also,
http://bugs.kde.org/285028
( and https://bugreports.qt.nokia.com/browse/QTBUG-22382 )
In Qt 4.8, QUrl.toLocalFile now seems, by design, to return NULL for urls
lacking any scheme. Discovered
A Dijous, 27 d'octubre de 2011, Thiago Macieira vàreu escriure:
On Thursday, 27 de October de 2011 13:32:51 Rex Dieter wrote:
See also,
http://bugs.kde.org/285028
( and https://bugreports.qt.nokia.com/browse/QTBUG-22382 )
In Qt 4.8, QUrl.toLocalFile now seems, by design, to return NULL
On Thursday, 27 de October de 2011 22:31:15 Albert Astals Cid wrote:
Personally i find it another joke in the history of Qt, saying you maintain
API and ABI (that you do) but then making functions behave totally
different from one version to another is just plain useless.
Right. So we should
A Dijous, 27 d'octubre de 2011, Thiago Macieira vàreu escriure:
On Thursday, 27 de October de 2011 22:31:15 Albert Astals Cid wrote:
Personally i find it another joke in the history of Qt, saying you
maintain API and ABI (that you do) but then making functions behave
totally different from
On Thursday 27 October 2011 21:11:11 Thiago Macieira wrote:
On Thursday, 27 de October de 2011 13:32:51 Rex Dieter wrote:
See also,
http://bugs.kde.org/285028
( and https://bugreports.qt.nokia.com/browse/QTBUG-22382 )
In Qt 4.8, QUrl.toLocalFile now seems, by design, to return NULL for
On Thursday, 27 de October de 2011 23:17:49 Milian Wolff wrote:
On Thursday 27 October 2011 21:11:11 Thiago Macieira wrote:
On Thursday, 27 de October de 2011 13:32:51 Rex Dieter wrote:
See also,
http://bugs.kde.org/285028
( and https://bugreports.qt.nokia.com/browse/QTBUG-22382 )
19 matches
Mail list logo
