Uwe Stöhr wrote:
Helge Hafting schrieb:
I see no problem telling users that we have some feature that
doesn't always work as intended. But they need a warning,
if we're going to provide floatflt.
But users who don't have problems with wrap floats will be spammed
with a warning that only confuses them.
I don't think anybody have "no problem" with them, because any other
editing that moves the wrap float nearer a page break can silently kill it.
This will happen to just about any such float - of course the longer ones
have more risk of getting "hit" with a break.
But in general whenever you want to use a program, you have to read a
manual how to use it. The same applies for features. Take for example
the listings feature, when you haven't read the docs, it won't work
for you.
Well, I have used it without reading the docs. So I probably didn't utilize
its many features, but I did not get something that silently disappear
when I edit a seemingly unrelated piece of the document.
For a real solution, we should use wrapfig instead of floatflt.
Wrapfig has also the advantage that it provides table wrap floats, not
only figure wrap floats.
I just posted a patch that do just that - so you got what you want.
Table wraps is not yet supported - that is for a second step. This step
just converts to wrapfig instead of floatflt - using the existing UI.
Helge Hafting
