Herbert Voss wrote:
> oh sorry, cut'n paste ... :-(
> Should be
[ snip...]
Got it.
> this is the style, where you do not need the additional \vspace
> at the end.
>
> the bug is another one:
> when I insert Format->Paragraph->Space-After->User defined a
> length like \normalbaselineskip and then ok, LyX makes
> this to \vspace{0}! This is doubled wrong. At first it short
> be \vspace{0pt} or with any other unit and second why is a
> a length with a name not accepted?
Ok, I see this too. I guess that the probalem is here, in
setVSpaceFromWidgets in QParagraph.C:
case 6:
string s;
string const length = trim(value);
if (isValidGlueLength(length)) {
s = length;
} else if (!length.empty()){
string u = trim(unit);
u = subst(u, "%%", "%");
s = length + u;
}
space = VSpace(LyXGlueLength(s));
break;
}
Apparently isValidGlueLength isn't clever enough to understand your length.
Thereafter, the fall back creates an unholy combination of
"\normalbaselineskip" + "sp"
so that the VSpace constructor has no hope in hell of doing anything with
it.
However, I think that the fundamental problem is that the parser that is
used to translate your string into a LyXGlueLength isn't powerful enough
to cope with your LaTeX skills.
Could you file a bug report on bugsilla please?
--
Angus
