You might try putting each table in a separate minipage (box),
making the box widths equal.
Paul
Hi,
I'd like to know what is the best recommended way to support
multi-threading in LyX, as of now. I thought using Qt (i.e., QThread &
related) is the most straightforward thing, as we already depend on Qt.
However, I noticed the m4/lock.m4 configure options such as
"--enable-threads":
-
Il 07/11/2011 14:46, Tommaso Cucinotta ha scritto:
However, now I broke compilation of lyxclient which complains with
errors about not knowing anything about #include and you can
imagine what else...
this is fixed in the attached refined version of the "SMP debugging" patch.
Interestingly, bo
On 06. nov. 2011 23:19, Peter Kümmel wrote:
[...]
Takes it so long to generate the latex file? Then no processes are used,
so nothing could be stopped.
In a real-life scenario, the document (and included figure files) may
reside on a slow file server on a sometimes heavily congested network.
R
Il 07/11/2011 10:55, Lars Gullik Bjønnes ha scritto:
Tommaso Cucinotta writes:
| +#include
| +#include
| +#include
| +#include
| +#include
Oh. how I dislike the Qt-fication of lyx...
I know, but as Qt is a strong dependency, it is anyway ok to rely on its
portable
extra features, right ? Fo
Il 07/11/2011 10:47, Lars Gullik Bjønnes ha scritto:
Hmm.. if an earlier match is found, the rest of the workers should be
stopped. That is not really hard to do.
Indeed, my plan is to let the other threads self-stop (checking from
time to time the abort/stop condition). Sending a signal to a
Tommaso Cucinotta writes:
| Hi,
>
| I just "enjoyed" extending the Find Advanced feature to exploit multi-cores.
>
| It exploits QThreadPool to create "worker" threads (as many as the
| underlying
| physical CPUs detected by QThreadPool). Each thread searches in a single
| paragraph, then "querie
Tommaso Cucinotta writes:
| Hi,
>
| I just "enjoyed" extending the Find Advanced feature to exploit multi-cores.
>
| It exploits QThreadPool to create "worker" threads (as many as the
| underlying
| physical CPUs detected by QThreadPool). Each thread searches in a single
| paragraph, then "querie
Hi,
I just "enjoyed" extending the Find Advanced feature to exploit multi-cores.
It exploits QThreadPool to create "worker" threads (as many as the
underlying
physical CPUs detected by QThreadPool). Each thread searches in a single
paragraph, then "queries" the next paragraph to be searched fr
