José Matos wrote:
> It is in my todo list and I intend to finish it soon.
Excellent.
Jürgen
On Sunday 11 November 2007 12:52:20 Jürgen Spitzmüller wrote:
> 4333 cri lyx crashes when opening 1.4.3. file with index containin...
> 4346 cri Synchronizing insets crash when two windows open
>
> I hope that Abdel and José, as the experts in the respective area, will
> find time to have a
> Two solutions:
> 1) for each and every "visual" action verify that this action is triggered
> the same way if this inset is also displayed in another view.
>
> 2) understand that "visual" action is *visual* and do not try to modify the
> other view to behave the same. This means that insets sho
Helge Hafting wrote:
Abdelrazak Younes wrote:
This patch (for trunk) mostly fixes the problem. The downside is that
the inset is not automatically "uncollapsed" when you leave the inset
after an automatic opening. The inset might also refuse to collapse if
the cursor is within it in another
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
We are already pretty close to a release: we have fixed the
regressions introduced with 1.5.2 (pixmap cache, AMS classes) and
several other things, including 9 critical bugs. So 1.5.3svn is
s
Abdelrazak Younes wrote:
> With this patch yes. But we can also move the opening/closing to the
> LFUN themselves which would be easy.
I see.
> > If I had the choice (and it boils down to an either/or), I'd rather do
> > without mouse hover.
>
> No, mouse hover is just a symptom. Multiple views s
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
This patch (for trunk) mostly fixes the problem. The downside is that
the inset is not automatically "uncollapsed" when you leave the inset
after an automatic opening. The inset might also refuse to collapse if
the cursor is within it in another
Pavel Sanda wrote:
This patch (for trunk) mostly fixes the problem. The downside is that the
inset is not automatically "uncollapsed" when you leave the inset after an
i'm still puzzled by the way lyx opens insets when more windows are involved.
how it should ideally behave ?
for example (in 1
Abdelrazak Younes wrote:
> This patch (for trunk) mostly fixes the problem. The downside is that
> the inset is not automatically "uncollapsed" when you leave the inset
> after an automatic opening. The inset might also refuse to collapse if
> the cursor is within it in another view.
So we end up
> This patch (for trunk) mostly fixes the problem. The downside is that the
> inset is not automatically "uncollapsed" when you leave the inset after an
i'm still puzzled by the way lyx opens insets when more windows are involved.
how it should ideally behave ?
for example (in 1.5.2):
1. launch
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
We are already pretty close to a release: we have fixed the
regressions introduced with 1.5.2 (pixmap cache, AMS classes) and
several other things, including 9 critical bugs. So 1.5.3svn is
significantly ahead of 1.5.
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I had a look to 4346. It's due to the autoOpen flag which is decided at
metrics time. It basically decides to open the inset if the cursor is
inside.
Does autoOpen interact with mouse hover, or why does it have an impact here?
Mouse hover tr
Abdelrazak Younes wrote:
> I had a look to 4346. It's due to the autoOpen flag which is decided at
> metrics time. It basically decides to open the inset if the cursor is
> inside.
Does autoOpen interact with mouse hover, or why does it have an impact here?
Jürgen
Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
We are already pretty close to a release: we have fixed the
regressions introduced with 1.5.2 (pixmap cache, AMS classes) and
several other things, including 9 critical bugs. So 1.5.3svn is
significantly ahead of 1.5.2, IMHO.
Therefore, I do
Jürgen Spitzmüller wrote:
We are already pretty close to a release: we have fixed the regressions
introduced with 1.5.2 (pixmap cache, AMS classes) and several other things,
including 9 critical bugs. So 1.5.3svn is significantly ahead of 1.5.2, IMHO.
Therefore, I don't want to hold back the r
We are already pretty close to a release: we have fixed the regressions
introduced with 1.5.2 (pixmap cache, AMS classes) and several other things,
including 9 critical bugs. So 1.5.3svn is significantly ahead of 1.5.2, IMHO.
Therefore, I don't want to hold back the release very much longer. How
16 matches
Mail list logo
