Re: Inset handling question

2010-10-29 Thread Andre Poenitz
On Fri, Oct 29, 2010 at 03:23:52AM +0200, Uwe Stöhr wrote: > Thanks, I used this for the fix: http://www.lyx.org/trac/changeset/35894 > > One last question: How do I explicitly specify that the "0" in my > patch is a pointer? 0 (and any integral constant expression that evaluates to zero such as

Re: Inset handling question

2010-10-29 Thread Vincent van Ravesteijn
Op 29-10-2010 17:17, Richard Heck schreef: On 10/29/2010 10:53 AM, Vincent van Ravesteijn wrote: Op 29-10-2010 16:22, Richard Heck schreef: On 10/29/2010 09:20 AM, Uwe Stöhr wrote: > With classes, this happens whenever one class has a constructor that > takes some other type as an argument

Re: Inset handling question

2010-10-29 Thread Richard Heck
On 10/29/2010 10:53 AM, Vincent van Ravesteijn wrote: Op 29-10-2010 16:22, Richard Heck schreef: On 10/29/2010 09:20 AM, Uwe Stöhr wrote: > With classes, this happens whenever one class has a constructor that > takes some other type as an argument. So, for example, suppose we > have: > >

Re: Inset handling question

2010-10-29 Thread Vincent van Ravesteijn
Op 29-10-2010 16:22, Richard Heck schreef: On 10/29/2010 09:20 AM, Uwe Stöhr wrote: > With classes, this happens whenever one class has a constructor that > takes some other type as an argument. So, for example, suppose we > have: > > class A { >A(); >A(int); >}; > > So

Re: Inset handling question

2010-10-29 Thread Richard Heck
On 10/29/2010 09:20 AM, Uwe Stöhr wrote: > With classes, this happens whenever one class has a constructor that > takes some other type as an argument. So, for example, suppose we > have: > > class A { >A(); >A(int); >}; > > So class A has two constructors: A default one,

Re: Inset handling question

2010-10-29 Thread Uwe Stöhr
> To maybe explain a little more... Thank you. > With classes, this happens whenever one class has a constructor that > takes some other type as an argument. So, for example, suppose we > have: > > class A { >A(); >A(int); >}; > > So class A has two constructors: A defaul

Re: Inset handling question

2010-10-29 Thread José Matos
On Friday 29 October 2010 02:33:58 Vincent van Ravesteijn wrote: > Some code uses NULL to somehow indicate a null pointer, sometimes you > see (Inset *) 0, but in the end a pointer is just a number and a number > can be 0 I guess. Not according to Bjarne Stroustroup. :-) "No object is allocatte

Re: Inset handling question

2010-10-28 Thread Richard Heck
On 10/28/10 9:42 PM, Uwe Stöhr wrote: Some code uses NULL to somehow indicate a null pointer, sometimes you see (Inset *) 0, but in the end a pointer is just a number and a number can be 0 I guess. Usually we just do:... Thanks for the explanation. To maybe explain a little more, C++ will

Re: Inset handling question

2010-10-28 Thread Uwe Stöhr
Am 29.10.2010 03:33, schrieb Vincent van Ravesteijn: One last question: How do I explicitly specify that the "0" in my patch is a pointer? I mean "0" could also refer an int or double. The compiler doesn't complain and "0" is the default return value of innerInsetOfType but I'm wondering why t

Re: Inset handling question

2010-10-28 Thread Vincent van Ravesteijn
One last question: How do I explicitly specify that the "0" in my patch is a pointer? I mean "0" could also refer an int or double. The compiler doesn't complain and "0" is the default return value of innerInsetOfType but I'm wondering why this works. There is also a small section on this in

Re: Inset handling question

2010-10-28 Thread Uwe Stöhr
The DocIterator stuff is documented somewhere in the Wiki. You must read that before doing anything else. Indeed! I found this page: http://wiki.lyx.org/Devel/Diagrams and I understand now a lot more. Many thanks Pavel, for your devel Wiki pages! This explains also my question from the last pos

Re: Inset handling question

2010-10-28 Thread Abdelrazak Younes
On 10/28/2010 10:03 AM, Abdelrazak Younes wrote: On 10/28/2010 01:51 AM, Uwe Stöhr wrote: > You can just use the Cursor starting at position 0... I don't understand yet how the cursor stuff works. I can move the cursor stepwise through the table cells but how do I move it outside of the table

Re: Inset handling question

2010-10-28 Thread Abdelrazak Younes
On 10/28/2010 01:51 AM, Uwe Stöhr wrote: > You are going forward... you should go backward. Ah, OK. When I replace "++it" by "--it" the compiler quites with the message that there are unresolved externals because a variable beginning with "--" doesn't exist. Then it is declared but not imple

Re: Inset handling question

2010-10-27 Thread Uwe Stöhr
> You are going forward... you should go backward. Ah, OK. When I replace "++it" by "--it" the compiler quites with the message that there are unresolved externals because a variable beginning with "--" doesn't exist. This is strange because I thought that -- can be used the same way as ++. >

Re: Inset handling question

2010-10-26 Thread Abdelrazak Younes
On 10/26/2010 02:40 AM, Uwe Stöhr wrote: In order to fix http://www.lyx.org/trac/ticket/6585 I need to check in InsetTabular if the table is inside a float. i thought I can do this by iterating the insets starting with the table inset down to the outer insets. if one of the outer insets is a