[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-core-dev] Build on Windows
|
>
> Yup, that's pretty much exactly what I'm seeing. For small builds with no
> errors, I'd prefer to see something while I'm waiting. At 512 characters,
> it could be a few files into the build before I see anything.
>
> I can see that if you were asyncExec'ing each line, you'd have problems
> since this can end up queing up quite a few Runnables. However, I notice
> that there is a syncExec there right now. Did this not solve the problem on
> its own? This should theoretically let the pipes fill up while waiting for
> the UI to update.
>
IIRC.
Yes the syncExec() should have fix it, but when doing testing on Eclipse/GTK
it was still slow ... very slow, since the write() affected directly
the IDocument, so to help improve, the bufferring was added.
However on Windows, things were fine, I do not remember
on Motif but I think it was acceptable.
The Eclipse/gtk was our benchmark by being the slowest platform.
> As another solution, I was thinking of using a sync object and making sure
> only one Runnable got enqueued at a time. Thoughts?
>
Remove the buffering and see how it behaves for you.
Maybe the 2.1/SWT/GTK improves the IDocument/fonts problems.
