On Sat, Apr 22, 2006 at 06:42:53PM -0500, Garst R. Reese wrote:
> Martin Vermeer wrote:
>
> >On Thu, Apr 20, 2006 at 10:28:51PM -0500, Garst R. Reese wrote:
> >
> >
> >>Martin Vermeer wrote:
> >>
> >>
> >I don't agree. You're right in that the only place where a
> >_correspondence_ is defined between the old numerical parameters and the
> >new character ones is, precisely, lyx2lyx. And this correspondence
> >should be _semantically correct_, i.e. 0123 -> ctbs. (Right? You have
> >1.3.7 installed, so you can verify that truly 0 = center, 1 = top.)
> >
> >
> Yes, but why does src/insets/insetminipage.h have
>
> 33 enum InnerPosition {
> 34 inner_center,
> 35 inner_top,
> 36 inner_bottom,
> 37 inner_stretch
> instead of
> 33 enum InnerPosition {
> 34 inner_top,
> 35 inner_center,
> 36 inner_bottom,
> 37 inner_stretch
> ?This is 1.3.7 code right? Just proves my point: center == 0. > If this order is changed and lyx_1_4.py is changed to match than 1.3.7 > still works. ... > Thanks for the pointers. After looking at the relevant files in 1.4.1, > and the insetminipage > files in 1.3.7, I think that both patches to 1.4.1 should be applied. I > tried this and did not have a problem with it. You, of course, know > much better than I and I thank you for sharing. You're welcome! Understanding the lyx2lyx logic requires a fair amount of doublethink. Actually Georg understands this stuff much better than I and the good news is he agreed with my analysis (and offered proof) - Martin
pgpoGutWqkNwK.pgp
Description: PGP signature
