Juergen Spitzmueller wrote:
> Andre Poenitz wrote:
>> So a good check is always math-in-math-in-note-in-table-in-table. ÂIf
>> something works in this scenario it is fairly safe to assume it works
>> everywhere.
>
> This works too.
Thanks Juergen, Martin and Andre. I'll commit this tonight (gott
Andre Poenitz wrote:
> So a good check is always math-in-math-in-note-in-table-in-table. If
> something works in this scenario it is fairly safe to assume it works
> everywhere.
This works too.
Jürgen
On Sun, Mar 20, 2005 at 03:47:59PM +0100, Juergen Spitzmueller wrote:
> Alfredo Braunstein wrote:
> > I attach a tentative solution (make setPos not descend), tested only
> > once ;-). Feedback greatly appreciated
>
> Works fine here too.
In such cases please also check whether it works with a ma
Alfredo Braunstein wrote:
> I attach a tentative solution (make setPos not descend), tested only
> once ;-). Feedback greatly appreciated
Works fine here too.
Jürgen
On Sun, Mar 20, 2005 at 01:48:08PM +0100, Alfredo Braunstein wrote:
> Juergen Spitzmueller wrote:
>
> > Martin Vermeer wrote:
> >> I think I know where the problem is, not how to fix it :-(
> >
> > Me too. It seems that MOUSE_MOTION moves inside nested insets despite of
> >
> > // only accept mo
Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
>> I think I know where the problem is, not how to fix it :-(
>
> Me too. It seems that MOUSE_MOTION moves inside nested insets despite of
>
> // only accept motions to places not deeper nested than the real anchor
> if (bvcur.anchor_.hasPart(c
On Tue, Mar 15, 2005 at 12:08:04AM +0200, Martin Vermeer wrote:
> On Mon, Mar 14, 2005 at 03:32:28PM +0100, Juergen Spitzmueller wrote:
> > Martin Vermeer wrote:
> > > I think I know where the problem is, not how to fix it :-(
> >
> > Me too. It seems that MOUSE_MOTION moves inside nested insets d
On Mon, Mar 14, 2005 at 03:32:28PM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > I think I know where the problem is, not how to fix it :-(
>
> Me too. It seems that MOUSE_MOTION moves inside nested insets despite of
>
> // only accept motions to places not deeper nested th
On Mon, Mar 14, 2005 at 03:32:28PM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > I think I know where the problem is, not how to fix it :-(
>
> Me too. It seems that MOUSE_MOTION moves inside nested insets despite of
>
> // only accept motions to places not deeper nested th
Martin Vermeer wrote:
> I think I know where the problem is, not how to fix it :-(
Me too. It seems that MOUSE_MOTION moves inside nested insets despite of
// only accept motions to places not deeper nested than the real anchor
if (bvcur.anchor_.hasPart(cur)) {
No idea why.
Jürg
Martin Vermeer wrote:
> Not really. I think I know where the problem is, not how to fix it :-(
Too bad.
Jürgen
On Mon, Mar 14, 2005 at 11:42:02AM +0100, Juergen Spitzmueller wrote:
> This is probably related to the problem we detected when selected nested
> insets inside tables (problem with LFUN_MOUSE_MOTION). I think Martin has an
> idea how to fix this.
>
> Jürgen
Not really. I think I know where the
This is probably related to the problem we detected when selected nested
insets inside tables (problem with LFUN_MOUSE_MOTION). I think Martin has an
idea how to fix this.
JÃrgen
Helge Hafting wrote:
> Lyx may crash when selecting nested tables:
>
> * Selecting two side-by-side tables works wel
Lyx may crash when selecting nested tables:
* Selecting two side-by-side tables works well.
* Selecting a whole table that happens to contain
another table in a cell seems to work. But, using
bold or italic does not apply to all the cells in
the table(s) thus selected. Both tables had some
em
14 matches
Mail list logo
