On Sat, Mar 27, 2004 at 11:34:02PM +0100, Alfredo Braunstein wrote:
Andre Poenitz wrote:
Same behaviour.
I just figured out that it works, but somehow takes a larger amount of
time _per file_ in each interaction. A 'cvs commit' is actually quite
fast, but 'cvs update' takes about 10s
On Sat, Mar 27, 2004 at 10:37:37PM +, Angus Leeming wrote:
Alfredo Braunstein wrote:
Andre Poenitz wrote:
On Sat, Mar 27, 2004 at 01:42:30PM +0100, Alfredo Braunstein wrote:
btw, we should have a right past-the-end position for dociterator
(and all derivatives).
We do.
On Sat, Mar 27, 2004 at 11:35:00PM +0100, Alfredo Braunstein wrote:
Andre Poenitz wrote:
On Sat, Mar 27, 2004 at 01:42:30PM +0100, Alfredo Braunstein wrote:
btw, we should have a right past-the-end position for dociterator (and
all derivatives).
We do.
It's an empty cursor slice
Andre Poenitz wrote:
It is good enough if we are happy with input iterator semantics. No '--'
[forward iterator semantics would be more applicable here].
there. For backwards iteration we could just use another iterator class.
Yes, but why? We give up bidi iterator semantics for no reason.
Andre Poenitz wrote:
Any idea how to correct the situation without a complete new checkout?
Should I try to use the dates from CVS/Entries?
No idea... maybe touching back in time all unchanged source files?
Alfredo
Andre Poenitz wrote:
Can anybody please remind me about the where and when? I must have
missed something
I got no answers before. It would seem that there are no proposals yet :-(
Btw, I would step in for LDM Buenos Aires 2005 but my life is so uncertain
now that there are no warranties I
Patch attached FYI. Moves the code that actually dispatches the print
command from ControlPrint and into LyXFunc::dispatch. This dispatcher
receives a string of the form:
$TARGET $NAME $COMMAND
where $TARGET = printer or file
$NAME is the name of the device or file. If printing
On Sun, Mar 28, 2004 at 02:09:26PM +, Angus Leeming wrote:
Patch attached FYI. Moves the code that actually dispatches the print
Coolio, how many more of these to go before you can do the big cvs
remove ?
john
I'm moved this into the core (patch attached):
void ControlDocument::setLanguage()
{
Language const * oldL = buffer()-params().language;
Language const * newL = bp_-language;
if (oldL != newL) {
if (oldL-RightToLeft() == newL-RightToLeft()
John Levon wrote:
On Sun, Mar 28, 2004 at 02:09:26PM +, Angus Leeming wrote:
Patch attached FYI. Moves the code that actually dispatches the
print
Coolio, how many more of these to go before you can do the big cvs
remove?
I have a TODO file has been sitting in the controllers dir of
A bit late...
Angus Leeming wrote:
Furthermore, there is a leak in the code above. I think the minimal
change is:
if (from.getInset(i)) {
// the inset is not in a paragraph anymore
tmpinset = from.insetlist.release(i);
+
Alfredo Braunstein wrote:
Furthermore, there is a leak in the code above. I think the minimal
change is:
if (from.getInset(i)) {
// the inset is not in a paragraph anymore
tmpinset = from.insetlist.release(i);
+
Angus Leeming wrote:
insetlist.release(i) sets the pointer to zero, so delete becaomes a
no-op.
Good point ;-)
Alfredo
On Sun, Mar 28, 2004 at 12:09:48PM +, Angus Leeming wrote:
Gunsan wrote:
Hello.
How can I produce a sum of this kind in LyX
-
\ a*b
/
-
0an
0bm
(notice the two rows below the sum sign)
Lyx file attached. Should enable you to modify to suit.
Kayvan A. Sylvan wrote:
Hello.
How can I produce a sum of this kind in LyX
-
\ a*b
/
-
0an
0bm
Lyx file attached. Should enable you to modify to suit.
Doing the select the following and Insert-Inlined Math as
mentioned in the document, with current CVS,
This is bunch of unsorted fixes mostly to CP crashes.
+ add InsetText::insetAllowed with default to true (the main text is an
InsetText). Would this produce any undesired side-effect? This solves the
problem of insets silently dissapearing on paragraph break
I will apply this if there are no
Am Samstag, 27. März 2004 22:14 schrieb Andre Poenitz:
On Sat, Mar 27, 2004 at 04:04:58PM +0100, Georg Baum wrote:
Don't you think it's time to grow up and commit your fixes yourself? ;-}
It is a bit difficult to commit when working from Kayvans anoncvs mirror ;-)
So unless somebody gets
Georg Baum wrote:
Don't you think it's time to grow up and commit your fixes
yourself? ;-}
It is a bit difficult to commit when working from Kayvans anoncvs
mirror ;-) So unless somebody gets tired and gives me cvs access
I'll keep sending patches to the list.
It seems to me that the BufferParams may be applied to the core twice
in this block of code. Why don't we apply it once and then see if the
textclass can be switched (if so desired)? Or does switching
textclass mean that we really *do* have to apply it twice?
Angus (who is thinking of
This is all with a bang up-to-date cvs (up to and including Alfredo's
fixes 3 cp crashes, and a vanishing insets bug fix patch.)
How to reproduce it:
Open a new document. Don't name it.
Paste in:
\[\sum_{0an}a*b\]
Copy this within LyX so that your document looks like:
The patch attached adds LFUN_LANGUAGE_BUFFER and LFUN_TEXTCLASS_LOAD
and uses them to move code currently in ControlDocument back into the
core.
This should be a simple rearrangement of the code, but is stuff with
which I'm not very familiar, so if anyone wants to step forward and
test it, that'd
I've already noted that a graphics inset doesn't resize itself when
the graphic is loaded. (Example is a graphic inset in the cell of a
tabular inset.)
First the process:
A graphics inset starts the process of loading an external graphic
file in its draw member function. Thereafter, it receives
Angus Leeming wrote:
1. Why no checks for whether any drawing should be actually
performed?
Because it updates the 'visible' paragraphs only and that should be
fairly efficient.
2. Where do I start if I want the inset to redraw itself
with the new, corrected metrics info?
Further
On Sat, Mar 27, 2004 at 11:34:02PM +0100, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > Same behaviour.
> >
> > I just figured out that it "works", but somehow takes a larger amount of
> > time _per file_ in each interaction. A 'cvs commit' is actually quite
> > fast, but 'cvs update'
On Sat, Mar 27, 2004 at 10:37:37PM +, Angus Leeming wrote:
> Alfredo Braunstein wrote:
>
> > Andre Poenitz wrote:
> >
> >> On Sat, Mar 27, 2004 at 01:42:30PM +0100, Alfredo Braunstein wrote:
> >>> btw, we should have a right past-the-end position for dociterator
> >>> (and all derivatives).
On Sat, Mar 27, 2004 at 11:35:00PM +0100, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > On Sat, Mar 27, 2004 at 01:42:30PM +0100, Alfredo Braunstein wrote:
> >> btw, we should have a right past-the-end position for dociterator (and
> >> all derivatives).
> >
> > We do.
> >
> > It's an
Andre Poenitz wrote:
> It is good enough if we are happy with input iterator semantics. No '--'
[forward iterator semantics would be more applicable here].
> there. For backwards iteration we could just use another iterator class.
Yes, but why? We give up bidi iterator semantics for no reason.
Andre Poenitz wrote:
> Any idea how to correct the situation without a complete new checkout?
> Should I try to use the dates from CVS/Entries?
No idea... maybe touching back in time all unchanged source files?
Alfredo
Andre Poenitz wrote:
> Can anybody please remind me about the where and when? I must have
> missed something
I got no answers before. It would seem that there are no proposals yet :-(
Btw, I would step in for LDM Buenos Aires 2005 but my life is so uncertain
now that there are no warranties
Patch attached FYI. Moves the code that actually dispatches the print
command from ControlPrint and into LyXFunc::dispatch. This dispatcher
receives a string of the form:
"$TARGET $NAME $COMMAND"
where $TARGET = "printer" or "file"
$NAME is the name of the device or file. If
On Sun, Mar 28, 2004 at 02:09:26PM +, Angus Leeming wrote:
> Patch attached FYI. Moves the code that actually dispatches the print
Coolio, how many more of these to go before you can do "the big cvs
remove" ?
john
I'm moved this into the core (patch attached):
void ControlDocument::setLanguage()
{
Language const * oldL = buffer()->params().language;
Language const * newL = bp_->language;
if (oldL != newL) {
if (oldL->RightToLeft() == newL->RightToLeft()
John Levon wrote:
> On Sun, Mar 28, 2004 at 02:09:26PM +, Angus Leeming wrote:
>
>> Patch attached FYI. Moves the code that actually dispatches the
>> print
>
> Coolio, how many more of these to go before you can do "the big cvs
> remove"?
I have a TODO file has been sitting in the
A bit late...
Angus Leeming wrote:
> Furthermore, there is a leak in the code above. I think the minimal
> change is:
>
> if (from.getInset(i)) {
> // the inset is not in a paragraph anymore
> tmpinset = from.insetlist.release(i);
Alfredo Braunstein wrote:
>> Furthermore, there is a leak in the code above. I think the minimal
>> change is:
>>
>> if (from.getInset(i)) {
>> // the inset is not in a paragraph anymore
>> tmpinset = from.insetlist.release(i);
>> +
Angus Leeming wrote:
> insetlist.release(i) sets the pointer to zero, so delete becaomes a
> no-op.
Good point ;-)
Alfredo
On Sun, Mar 28, 2004 at 12:09:48PM +, Angus Leeming wrote:
> Gunsan wrote:
>
> > Hello.
> > How can I produce a sum of this kind in LyX
> >
> > -
> > \ a*b
> > /
> > -
> > 0 0
> >
> > (notice the two rows below the sum sign)
>
> Lyx file attached. Should enable you
Kayvan A. Sylvan wrote:
>> > Hello.
>> > How can I produce a sum of this kind in LyX
>> >
>> > -
>> > \ a*b
>> > /
>> > -
>> > 0 > 0 Lyx file attached. Should enable you to modify to suit.
> Doing the "select the following and Insert->Inlined Math" as
> mentioned in the
This is bunch of unsorted fixes mostly to C crashes.
+ add InsetText::insetAllowed with default to true (the main text is an
InsetText). Would this produce any undesired side-effect? This solves the
problem of insets silently dissapearing on paragraph break
I will apply this if there are no
Am Samstag, 27. März 2004 22:14 schrieb Andre Poenitz:
> On Sat, Mar 27, 2004 at 04:04:58PM +0100, Georg Baum wrote:
>
> Don't you think it's time to grow up and commit your fixes yourself? ;-}
It is a bit difficult to commit when working from Kayvans anoncvs mirror ;-)
So unless somebody gets
Georg Baum wrote:
>> Don't you think it's time to grow up and commit your fixes
>> yourself? ;-}
> It is a bit difficult to commit when working from Kayvans anoncvs
> mirror ;-) So unless somebody gets tired and gives me cvs access
> I'll keep sending patches to the list.
It seems to me that the BufferParams may be applied to the core twice
in this block of code. Why don't we apply it once and then see if the
textclass can be switched (if so desired)? Or does switching
textclass mean that we really *do* have to apply it twice?
Angus (who is thinking of
This is all with a bang up-to-date cvs (up to and including Alfredo's
"fixes 3 c crashes, and a vanishing insets bug fix" patch.)
How to reproduce it:
Open a new document. Don't name it.
Paste in:
\[\sum_{0
The patch attached adds LFUN_LANGUAGE_BUFFER and LFUN_TEXTCLASS_LOAD
and uses them to move code currently in ControlDocument back into the
core.
This should be a simple rearrangement of the code, but is stuff with
which I'm not very familiar, so if anyone wants to step forward and
test it, that'd
I've already noted that a graphics inset doesn't resize itself when
the graphic is loaded. (Example is a graphic inset in the cell of a
tabular inset.)
First the process:
A graphics inset starts the process of loading an external graphic
file in its draw member function. Thereafter, it receives
Angus Leeming wrote:
> 1. Why no checks for whether any drawing should be actually
> performed?
Because it updates the 'visible' paragraphs only and that should be
fairly efficient.
2. Where do I start if I want the inset to redraw itself
> with the new, corrected metrics info?
Further
46 matches
Mail list logo