On 19-Mar-2002 Angus Leeming wrote:
> Thanks. Jürgen. My question could really be rephrased as:
> why do insetgraphics and insetexternal set this explicitly in their "copy"
> c-tors (well when clone is invoked), rather than by passing this down to the
Well I could only assume old code a
On Tuesday 19 March 2002 9:57 am, Juergen Vigna wrote:
> On 18-Mar-2002 Angus Leeming wrote:
> > Why do insetexternal and insetgraphics set Inset::id_. Isn't this
> > variable used only by the text insets?
>
> Every inset has it's id! It may not be used but it should have one, just
> in case I wou
On 18-Mar-2002 Angus Leeming wrote:
> Why do insetexternal and insetgraphics set Inset::id_. Isn't this variable
> used only by the text insets?
Every inset has it's id! It may not be used but it should have one, just
in case I would have to look it up. And they also should have the posibility
Why do insetexternal and insetgraphics set Inset::id_. Isn't this variable
used only by the text insets?
Angus
On Tue, Nov 20, 2001 at 02:37:56PM +0100, Andre Poenitz wrote:
> > if you're REALLY sure that it does not change semantics in some insets!
>
> I am not going to do anything there, I was just poking around a bit. And I
> have admit that I have serious problems understanding these things out
> the
On Tue, Nov 20, 2001 at 02:31:12PM +0100, Juergen Vigna wrote:
> >are going to be edited, there is a mouseclick for you!"
>
> Probably you're right, but I wouldn't invert that right now. Only do it
> if you're REALLY sure that it does not change semantics in some insets!
I am not going to do
On 20-Nov-2001 Andre Poenitz wrote:
>
> Can anybody tell me the significance of the order of the lines 631 and 632
> of BufferView_pimpl.C?
>
> inset->insetButtonPress(bv_, xpos, ypos, button);
> inset->edit(bv_, xpos, ypos, button);
>
> Is this saying:
>
> "Hey,
Can anybody tell me the significance of the order of the lines 631 and 632
of BufferView_pimpl.C?
inset->insetButtonPress(bv_, xpos, ypos, button);
inset->edit(bv_, xpos, ypos, button);
Is this saying:
"Hey, inset, someone clicked on you" and after a while "He
On 31-Jul-2001 Danker, Dr. Timm wrote:
>>
>> Most problems we have with InsetText (and derivates) can probably be
>> fixed one and for all. So yes they have a common code base.
>>
> Is, for example, the insetminipage also somehow derived from insettext?
> Looking at the code, I only see it deri
On Tuesday 31 July 2001 13:02, Danker, Dr. Timm wrote:
> >
> > Most problems we have with InsetText (and derivates) can probably be
> > fixed one and for all. So yes they have a common code base.
> >
> Is, for example, the insetminipage also somehow derived from insettext?
> Looking at the code,
>
> Most problems we have with InsetText (and derivates) can probably be
> fixed one and for all. So yes they have a common code base.
>
Is, for example, the insetminipage also somehow derived from insettext?
Looking at the code, I only see it derived from collapsble which in turn
inherits from
On 31-Jul-2001 Michael Schmitt wrote:
> a short question from a curious user (answer with just a sentence
> or two): Do all these insets have a common code base? As you know there
> are still some repainting problems with insets and I wonder whether they
> can be fixed once for all insets.
Most
Hi,
a short question from a curious user (answer with just a sentence
or two): Do all these insets have a common code base? As you know there
are still some repainting problems with insets and I wonder whether they
can be fixed once for all insets.
Michael
--
==
On 11-Jul-2000 Baruch Even wrote:
>
> But the question remains unanswered, How do I get this bview pointer out
> of the blue? Should I save the BufferView* I get from last time and use
> that? It seems ugly to me, is there no other way to get this pointer?
>
I recently added the new TabularInse
On Tue, 11 Jul 2000, Juergen Vigna wrote:
> > 1. Marking the buffer dirty. After my inset gets changed by the dialog,
> > how should I go about notifying lyx that the data has changed? I know of
> > the markxxxDirty, but how do I get access to them? basically it amounts to
> > "how do I get a poi
On 07-Jul-2000 Baruch Even wrote:
> After some more work on the inset I've got even more questions.
>
> 1. Marking the buffer dirty. After my inset gets changed by the dialog,
> how should I go about notifying lyx that the data has changed? I know of
> the markxxxDirty, but how do I get access t
After some more work on the inset I've got even more questions.
1. Marking the buffer dirty. After my inset gets changed by the dialog,
how should I go about notifying lyx that the data has changed? I know of
the markxxxDirty, but how do I get access to them? basically it amounts to
"how do I get
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> This this is very close. Please have a go. (We also have other
Lars> insets where this excact samt thing need to be fixed.)
URL inset comes to mind.
JMarc
Angus Leeming <[EMAIL PROTECTED]> writes:
| What you (Lars) are suggesting is the GUI-Independence way of doing
| things. Ie,
| FormCitation and InsetCitation are separate classes.
|
| Pressing Insert->Citation Reference will launch a signal to show the citation
| dialog (FormCitation). Nothing
> | if (c == LyXParagraph::META_INSET) {
> | Inset const * tmpinset = row->par()->GetInset(pos);
> | if (tmpinset) {
> | tmpinset->draw(bview, font, offset+row->baseline(), x,
> |cleared);
> | }
> |
Angus Leeming <[EMAIL PROTECTED]> writes:
| if (c == LyXParagraph::META_INSET) {
| Inset const * tmpinset = row->par()->GetInset(pos);
| if (tmpinset) {
| tmpinset->draw(bview, font, offset+row->baseline(), x,
|
JMarc> I do not really know, but I'd like to point out that it is a common
JMarc> problem for the insets. We should really find a fix.
There are people out there who are FAR more knowledgeable than me. Could I have
comments on the following scheme please.
It seems to me that the place to check w
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Hi. I'm trying to fix a small bug in the citation dialog.
Angus> Namely, an empty inset can hang around after the user has
Angus> returned from the citation dialog without entering anything.
Angus> Prompted by Jean-Marc (a long tim
Hi.
I'm trying to fix a small bug in the citation dialog. Namely, an empty inset
can hang around after the user has returned from the citation dialog without
entering anything. Prompted by Jean-Marc (a long time ago, admittedly) I
thought I'd fix this.
To do so, I modified a function citation_cb
24 matches
Mail list logo
