> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Jean-Marc, I do not think that this is correct. When you enter
Jürgen> "4nonsense" into the paragraph vspave widget, you get
Jürgen> 4pheight% (even though the %-items are excluded from the
Jürgen> unit's choice).
Oops, you
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> What were again the reasons why we have excluded the
Juergen> %-lengths from VSpace? They certainly work, and IMO at least
Juergen> \textheight is highly sensible.
I guess \textheight is the only sensible one. You should
> "José" == José Abílio Oliveira Matos <[EMAIL PROTECTED]> writes:
José> Clearly if I implement this feature it will have a lot more
José> flexibility than that. Including conditional convertions
José> depending on the version available is too easy to do.
José> Also it would allow more in
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> If that's not possible, then I'd say leave it as it is. I
Bennett> think the chances of confusion are minimal.
What is "as it is"? With the patch applied, or without? Did you see a
difference?
JMarc
Jean-Marc Lasgouttes wrote:
> Jürgen> I think that you can just revert the fix. 1.3.x worked quite
> Jürgen> well before (in contrary to 1.4)
>
> What confused me is that bug 1682 is against lyx 1.3.3...
Yes, but the definition of num_units is different ;-)
Jürgen
On Fri, Nov 12, 2004 at 03:56:20PM +0100, Jean-Marc Lasgouttes wrote:
> > "José" == José Abílio Oliveira Matos <[EMAIL PROTECTED]> writes:
>
> José> Clearly if I implement this feature it will have a lot more
> José> flexibility than that. Including conditional convertions
> José> depending
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
Jürgen> I think that you can just revert the fix. 1.3.x worked quite
Jürgen> well before (in contrary to 1.4)
>> What confused me is that bug 1682 is against lyx 1.3.3...
Juergen> Yes, but th
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
Jean-Marc> This patch makes sure that insetlatexaccents are considered
Jean-Marc> as normal letters by the code that handles words
Jean-Marc> (word-backward/forward, word-select).
This is a version of the same thing for 1.3.X,
Jean-Marc Lasgouttes wrote:
> I guess \textheight is the only sensible one.
Why shouldn't someone find \textwidth sensible? E.g., if he wants produce a
blank square (for whatever reason). But textheight is certainly the most
important one.
> You should be careful
> though about the screen rep
Jean-Marc Lasgouttes wrote:
> Indeed. So was there really a problem in lyx 1.3.3?
Can't remember. But AFAICS everything is fine now (with the reverted "fix").
Jürgen
Jean-Marc Lasgouttes wrote:
> This is a version of the same thing for 1.3.X, which also contains
> some bug fixes already present in 1.4.0cvs.
>
> Comments?
Seems the right thing to do.
Alfredo
I finally managed to install a current version of tex4ht and could test
OpenOffice.org export. The attached patch adds the necessary format and
converters (also for import via writer2latex).
It adds furthermore a viewer and editor for text files. The latter is needed
since the "open" button of the
On Mon, Nov 08, 2004 at 10:55:53PM +, Andreas Vox wrote:
> Why is everyone flame-baiting always Lars, I wonder?
Evolution.
We started off with flame-baiting everybody on Fridays and finished
with flame-baiting only Lars, but on all days of the week.
Andre'
On Wed, Nov 10, 2004 at 03:36:29PM +0100, Alfredo Braunstein wrote:
> > I guess InsetNote and InsetBranch may need that too, but I am not sure.
>
> So what's the right fix? You seem to understand this much better than I do.
I think, inheritance is the correct default and all insets unhappy with
t
On Tue, Nov 09, 2004 at 08:32:48AM +0100, Alfredo Braunstein wrote:
> now that drawSelection is separated from draw and called before it, the
> background painting of colored insets overwrites the selection.
>
> A possible way of solving this is to draw the background in
> InsetText::drawSelection
On Tue, Nov 09, 2004 at 07:37:41AM +0100, Alfredo Braunstein wrote:
> Yes, that's what you have done I think. In the case of chapter labels, it
> had the effect of drawing the word "Chapter" at the wrong coordinates:
> ascent_of_text was used to compute them.
Ah... ok. Nevertheless, I think this c
On Tue, Nov 09, 2004 at 11:39:50AM +, Andreas Vox wrote:
> Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> > I try to check if all features are still working. Haven't tried branches and
> > friends for a long time now.
>
> I'm using branches with 1.4.0cvs. 60 page DocBook document, two b
On Tue, Nov 09, 2004 at 01:38:49PM +0100, Jean-Marc Lasgouttes wrote:
> > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Lars> Yes, I know. but ideally we should not work on the translated
> Lars> name, but on some index instead.
>
> What makes it a bit complicated is that obso
On Wed, Nov 10, 2004 at 11:28:16PM +0100, Alfredo Braunstein wrote:
> [foot]--+
> |aa |
> ||bbb |
> +---+
>
> and press backspace -> crash.
>
> fix attached.
I wonder how code like this emerges in the first place...
buf.paragraph() is so obviously wrong there with all t
On Thu, Nov 11, 2004 at 09:25:57AM +0100, Alfredo Braunstein wrote:
> Should I apply this now?
Ah, yes, please.
Andre'
On Tue, Nov 09, 2004 at 04:05:28PM +0100, Jean-Marc Lasgouttes wrote:
> I know, but I am ambivalent about that. I like the fact that somebody
> outside of the LyX team can distribute a layout file and have a way to
> deprecate layouts. Such layout files exist in the beamer class, for
> example. The
Andre Poenitz wrote:
> On Tue, Nov 09, 2004 at 07:37:41AM +0100, Alfredo Braunstein wrote:
>> Yes, that's what you have done I think. In the case of chapter labels, it
>> had the effect of drawing the word "Chapter" at the wrong coordinates:
>> ascent_of_text was used to compute them.
>
> Ah... o
what's the real reason for separating drawSelection from draw in insets?
(note that I'm not talking about the separation in LyXText)
It introduces a lot of code duplication and it's less flexible than just
letting the inset do it at plasure in draw() (at worst, it could call
drawSelection as firs
Alfredo Braunstein wrote:
> I finally had a look at why the xforms frontend is slower than qt in
> CoordBranch. For some reason, XWorkarea sends every PRESS event
> inmediately followed by an unexistent RELEASE event, even with wrong
> coordinates (negatives). THis explains why selection doesn't w
24 matches
Mail list logo
