On Sun, Oct 19, 2003 at 07:59:12PM +0200, Juergen Spitzmueller spake thusly:
> I finally found the time.
> The ui is slightly different to xforms. Here's a screenshot:
> http://home.t-online.de/home/juergen.sp/branch.png
> Please let me know, if there are any objections or if I can apply this.
On Sun, Oct 19, 2003 at 06:32:15PM +0100, John Levon spake thusly:
> Can't we make this a little helper function ? rowBreakPoint is bad
> enough already ...
Concretely, how? Anonymous namespace, and then what?
Anything that makes things cleaner is welcome...
About the remaining problems... ma
On Sun, Oct 19, 2003 at 06:32:15PM +0100, John Levon spake thusly:
> On Sun, Oct 19, 2003 at 08:40:26PM +0300, Martin Vermeer wrote:
>
> > Would it be possible at this point to force the *row* that a displayed
> > math inset is on, to be aligned centre? Then (1) the offset_ hack in
> > formula.C
I finally found the time.
The ui is slightly different to xforms. Here's a screenshot:
http://home.t-online.de/home/juergen.sp/branch.png
Please let me know, if there are any objections or if I can apply this.
There is one problem left:
the branches color does not immediately change on screen. XF
Angus Leeming wrote:
> I hope that's lib/configure rather than $top/configure. The effect
> shouldn't be compiled into LyX.
Exactly. ... it would be so nice if some autoconfigure-knowledgeable good
soul had a look (existence of srcltx.sty/availiability of --source-specials
option to latex)...
>
On Sun, Oct 19, 2003 at 08:40:26PM +0300, Martin Vermeer wrote:
> Would it be possible at this point to force the *row* that a displayed
> math inset is on, to be aligned centre? Then (1) the offset_ hack in
> formula.C will no longer be needed, and (2) also the cursor will be
> positioned correct
On Sun, Oct 19, 2003 at 04:33:41PM +0100, John Levon spake thusly:
...
> On Sun, Oct 19, 2003 at 02:45:07PM +0300, Martin Vermeer wrote:
>
> > 1) The empty line below the inset is still there... I don't really
> > understand it.
>
> I somehow introduced this when hacking rowBreakPoint. ii.e. l
On Sun, Oct 19, 2003 at 02:45:07PM +0300, Martin Vermeer wrote:
> 1) The empty line below the inset is still there... I don't really
> understand it.
I somehow introduced this when hacking rowBreakPoint. ii.e. looking
there is where it is generated. But be careful ! It's hell to hack
john
--
K
On Sat, Oct 18, 2003 at 12:35:41AM +0200, Alain Castera wrote:
> > I would be all for "Default" if we had instant-apply in our dialogs. But
> > we do not. So I'd probably want to avoid it.
> Sorry, I don't understand your point, what do you mean by "instant apply" ?.
Instant apply is where any ch
On Sun, Oct 19, 2003 at 02:45:07PM +0300, Martin Vermeer spake thusly:
...
> > Would that be a clean enough solution if it works?
>
> Forget it... works kind-of, but not well enough (i.e. just as poorly
> as fudging the width in metrics).
>
> 1) The empty line below the inset is still there...
On Fri, Oct 17, 2003, John Levon wrotes :
> I would be all for "Default" if we had instant-apply in our dialogs. But
> we do not. So I'd probably want to avoid it.
Sorry, I don't understand your point, what do you mean by "instant apply" ?.
"Default" is the usual setting, as we use a "document pr
On Sat, Oct 18, 2003 at 03:10:58PM +0300, Martin Vermeer spake thusly:
...
> I plan to try adding code testing the inset's display() and then
> setting 'thiswidth' to the text width if true (at around line 723).
> In that way we have the 'width fudge' back - i.e., we rely on the
> existing line
12 matches
Mail list logo
