> Yes and no. the bv->text version is there where we "should" need only the > outermost LyXText. This means the function should not be dependant of > theLockingInset()! Maybe I missed some spots where I didn't understand > really what the function does. So it does not mean "will not work in a > text inset", but "should not consider theLockingInset()". In which case does an inset need information about some more or less random inset "above" it? For someone looking from a larger distance, bv->text looks as suspicious as the dreaded current_view. Andre' -- André Pönitz ............................................. [EMAIL PROTECTED]
- Re: CVS Update: lyx-devel Dekel Tsur
- Re: CVS Update: lyx-devel Juergen Vigna
- RE: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel John Levon
- RE: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel Angus Leeming
- Re: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel Andre Poenitz
- Re: CVS Update: lyx-devel Juergen Vigna
- Re: CVS Update: lyx-devel Andre Poenitz
- Re: CVS Update: lyx-devel Kayvan A. Sylvan
- Re: CVS Update: lyx-devel John Levon
- Re: CVS Update: lyx-devel Kayvan A. Sylvan
- Re: CVS Update: lyx-devel Juergen Vigna
- 666 inset vs. Latex Layout Kayvan A. Sylvan
- Re: 666 inset vs. Latex Layout Kayvan A. Sylvan
- Re: CVS Update: lyx-devel Andre Poenitz
- Re: CVS Update: lyx-devel Michael Schmitt