El Divendres, 9 d'agost de 2013, a les 01:35:19, Jaydeep Solanki va escriure:
> On Fri, Aug 9, 2013 at 1:31 AM, Albert Astals Cid wrote:
> > El Divendres, 9 d'agost de 2013, a les 01:09:18, Jaydeep Solanki va
> >
> > escriure:
> > > forgot to attach
> >
> > Can you explain your locking, not sure
On Fri, Aug 9, 2013 at 1:31 AM, Albert Astals Cid wrote:
> El Divendres, 9 d'agost de 2013, a les 01:09:18, Jaydeep Solanki va
> escriure:
> > forgot to attach
>
> Can you explain your locking, not sure i understand it.
>
QMutexLocker will lock the mutex in its constructor and unlock it in its
de
El Divendres, 9 d'agost de 2013, a les 01:09:18, Jaydeep Solanki va escriure:
> forgot to attach
Can you explain your locking, not sure i understand it.
Cheers,
Albert
>
> On Fri, Aug 9, 2013 at 1:07 AM, Jaydeep Solanki wrote:
> > Hi,
> >
> > Finally an end to cloning and threading issue.
>
forgot to attach
On Fri, Aug 9, 2013 at 1:07 AM, Jaydeep Solanki wrote:
> Hi,
>
> Finally an end to cloning and threading issue.
> Diff attached. I have kept QElapsedTimer, just in case you if you want to
> check performance. I'll remove it and qDebug() when pushing it.
>
> *A possible improvem
Hi,
Finally an end to cloning and threading issue.
Diff attached. I have kept QElapsedTimer, just in case you if you want to
check performance. I'll remove it and qDebug() when pushing it.
*A possible improvement:*
While a non UI thread is creating a cloned object using
TextDocumentConverter::con
