On 19-Oct-2001 John Levon wrote:
actually, the code of the inset_owner is TEXT. And looking at
the source, I see lots of places in insettext that setInsetOwner
to the text inset. I see nowhere where the direct owner of
a Paragraph is an insetert, so of course it won't call the right
On Mon, Oct 22, 2001 at 11:41:13AM +0200, Juergen Vigna wrote:
Both should be fixed after my next commit! (actually it was REALLY easy
to fix as soon as I put my nose on the right spot ;)
great, glad I was some help for once ;)
john
--
I'm frightened of figurines.
- Pulp
On 19-Oct-2001 John Levon wrote:
> actually, the code of the inset_owner is TEXT. And looking at
> the source, I see lots of places in insettext that setInsetOwner
> to the text inset. I see nowhere where the direct owner of
> a Paragraph is an insetert, so of course it won't call the right
>
On Mon, Oct 22, 2001 at 11:41:13AM +0200, Juergen Vigna wrote:
> Both should be fixed after my next commit! (actually it was REALLY easy
> to fix as soon as I put my nose on the right spot ;)
great, glad I was some help for once ;)
john
--
"I'm frightened of figurines."
- Pulp
On 19-Oct-2001 John Levon wrote:
I already told this to people on the list various time. This is a problem
I cannot understand and is of class inheritance. In some cases instead
of calling the right functions inside the class it calls some other functions
just try to debug it and you'll see
On Fri, Oct 19, 2001 at 11:28:59AM +0200, Juergen Vigna wrote:
what functions are we talking about, in which classes ?
Easy to debug try to do the cutpaste operations in gdb and stop at the
function 'bool Paragraph::checkInsertChar(LyXFont font)' (paragraph.C)
then look which efective
On Fri, Oct 19, 2001 at 06:20:43PM +0100, John Levon wrote:
[bull]
ignore me, looking at wrong place, sorry
john
--
I'm frightened of figurines.
- Pulp
On Fri, Oct 19, 2001 at 06:23:18PM +0100, John Levon wrote:
[bull]
ignore me, looking at wrong place, sorry
actually, the code of the inset_owner is TEXT. And looking at
the source, I see lots of places in insettext that setInsetOwner
to the text inset. I see nowhere where the direct owner
On 19-Oct-2001 John Levon wrote:
>> I already told this to people on the list various time. This is a problem
>> I cannot understand and is of class inheritance. In some cases instead
>> of calling the right functions inside the class it calls some other functions
>> just try to debug it and
On Fri, Oct 19, 2001 at 11:28:59AM +0200, Juergen Vigna wrote:
> > what functions are we talking about, in which classes ?
>
> Easy to debug try to do the cut operations in gdb and stop at the
> function 'bool Paragraph::checkInsertChar(LyXFont & font)' (paragraph.C)
> then look which
On Fri, Oct 19, 2001 at 06:20:43PM +0100, John Levon wrote:
> [bull]
ignore me, looking at wrong place, sorry
john
--
"I'm frightened of figurines."
- Pulp
On Fri, Oct 19, 2001 at 06:23:18PM +0100, John Levon wrote:
> > [bull]
>
> ignore me, looking at wrong place, sorry
actually, the code of the inset_owner is TEXT. And looking at
the source, I see lots of places in insettext that setInsetOwner
to the text inset. I see nowhere where the direct
On Mon, Oct 15, 2001 at 09:35:28AM +0200, Juergen Vigna wrote:
When Text is pasted from the outside into an ERT inset it remains black.
It will be red after the next reload, though...
I already told this to people on the list various time. This is a problem
I cannot understand and is of
On Mon, Oct 15, 2001 at 09:35:28AM +0200, Juergen Vigna wrote:
> > When Text is pasted from the outside into an ERT inset it remains black.
> > It will be red after the next reload, though...
>
> I already told this to people on the list various time. This is a problem
> I cannot understand and
14 matches
Mail list logo
