On Friday, January 14, 2011 20:53:07 Aaron J. Seigo wrote:
> hi...
>
> i just came across this in kstandarddirs.cpp:
>
> if (dirs.isEmpty()) {
> qFatal("KStandardDirs: The resource type %s is not
> registered", type);
> } else {
> path = rea
hi...
i just came across this in kstandarddirs.cpp:
if (dirs.isEmpty()) {
qFatal("KStandardDirs: The resource type %s is not
registered", type);
} else {
path = realPath(dirs.first());
}
isn't this is a bit heavy handed? for me
On Friday, January 14, 2011 13:58:34 Dawit A wrote:
> Can the warning message below be commented out if it is not critical ?
> It simply overwhelms my ~/.xsession-errors file to the point where I
> cannot look for other error messages.
>
> */KSharedDataCache: Trying to remove an entry which is alr
On Friday, 14 de January de 2011 20:28:04 Andreas Pakulat wrote:
> On 14.01.11 17:51:56, Albert Astals Cid wrote:
> > A Divendres, 14 de gener de 2011, Sebastian Trueg va escriure:
> > > However, the query parser still uses static QRegExp objects which
> > > seems
> > > a bad idea, isn't that right
On Friday, 14 de January de 2011 21:49:01 Ingo Klöcker wrote:
> On Friday 14 January 2011, Thiago Macieira wrote:
> > On Friday, 14 de January de 2011 13:46:19 Sebastian Trueg wrote:
> > > However, the query parser still uses static QRegExp objects which
> > > seems a bad idea, isn't that right?
>
On Friday 14 January 2011, Sebastian Trueg wrote:
> Hi guys,
>
> the problem is fairly simple: KIO relies on entry names to be unique.
> That makes sense since there needs to be some way to identify the items
> in a dir listing. This also worked nicely in pre-Nepomuk days.
>
> However, with the i
On Friday 14 January 2011, Thiago Macieira wrote:
> On Friday, 14 de January de 2011 13:46:19 Sebastian Trueg wrote:
> > However, the query parser still uses static QRegExp objects which
> > seems a bad idea, isn't that right?
>
> static QRegExp are a bad idea regardless of whether threading is
>
Hi guys,
the problem is fairly simple: KIO relies on entry names to be unique.
That makes sense since there needs to be some way to identify the items
in a dir listing. This also worked nicely in pre-Nepomuk days.
However, with the introduction of desktop search the filename is no
unique identifi
On 14.01.11 17:51:56, Albert Astals Cid wrote:
> A Divendres, 14 de gener de 2011, Sebastian Trueg va escriure:
> > However, the query parser still uses static QRegExp objects which seems
> > a bad idea, isn't that right?
> > Thus, I suppose it would be better to wrap them in a mutex'ed object and
Can the warning message below be commented out if it is not critical ?
It simply overwhelms my ~/.xsession-errors file to the point where I
cannot look for other error messages.
*/KSharedDataCache: Trying to remove an entry which is already
invalid. This cache is likely corrupt.
A Divendres, 14 de gener de 2011, Sebastian Trueg va escriure:
> However, the query parser still uses static QRegExp objects which seems
> a bad idea, isn't that right?
> Thus, I suppose it would be better to wrap them in a mutex'ed object and
> create that via K_GLOBAL_STATIC?
Why would you want
On Friday, 14 de January de 2011 13:46:19 Sebastian Trueg wrote:
> However, the query parser still uses static QRegExp objects which seems
> a bad idea, isn't that right?
static QRegExp are a bad idea regardless of whether threading is involved or
not.
> Thus, I suppose it would be better to wra
However, the query parser still uses static QRegExp objects which seems
a bad idea, isn't that right?
Thus, I suppose it would be better to wrap them in a mutex'ed object and
create that via K_GLOBAL_STATIC?
Cheers,
Sebastian
On 01/14/2011 01:17 AM, Thiago Macieira wrote:
> On Thursday, 13 de Jan
Am Freitag 14 Januar 2011, 01:16:07 schrieb Thiago Macieira:
> On Thursday, 13 de January de 2011 15:08:06 Aaron J. Seigo wrote:
> > On Thursday, January 13, 2011, Thiago Macieira wrote:
> > > On Thursday, 13 de January de 2011 22:43:28 Matthias Fuchs wrote:
> > > > Hi,
> > > >
> > > > There are s
14 matches
Mail list logo
