Re: r35925 - lyx-devel/trunk/src

2010-10-29 Thread Richard Heck
On 10/29/2010 07:51 PM, v...@lyx.org wrote: Author: vfr Date: Sat Oct 30 01:51:13 2010 New Revision: 35925 URL: http://www.lyx.org/trac/changeset/35925 Log: Remove saveCheckSum from Buffer::reload again. Now, the saveCheckSum call is already in Buffer::readFile, so it is not needed here anymore

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

Formats::viewURL()

2010-10-29 Thread Richard Heck
Pavel, I think you introduced this in connection with InsetHyperlink::viewTarget(). But it seems wrong to me. There's no particular reason to think that the URL in that case will actually be of type HTML, or that the viewer defined for HTML will be able to handle it. I mean, it might be that

DVI Viewer Paper Size

2010-10-29 Thread Richard Heck
Could that be removed? Does anyone use it any more? Even xdvi seems to detect paper size and such nowadays. The point of removing it is that then Formats::view() would not really need a Buffer argument. The message we write doesn't last, anyway, especially with background preview Richa

Re: r35920 - lyx-devel/trunk/src

2010-10-29 Thread Richard Heck
On 10/29/2010 03:10 PM, v...@lyx.org wrote: Author: vfr Date: Fri Oct 29 21:10:54 2010 New Revision: 35920 URL: http://www.lyx.org/trac/changeset/35920 Log: Write code in a language that everyone understands ? Does anyone have a clue why nvec is declared static here ? Or can I remove it ?

Security Question

2010-10-29 Thread Richard Heck
I've been working on the viewer code a bit, and have started to be a little concerned about the way we launch viewers and whether it is fully secure. I guess my current question concerns the Format::viewURL() routine and the way it is called from InsetHyperlink::viewTarget(). At the moment,

Re: RefStyle Patch

2010-10-29 Thread Jean-Pierre Chrétien
Jean-Pierre Chrétien a écrit : Richard Heck a écrit : Are there other things besides theorems we should define that aren't in refstyle.cfg? To be prettyref-coherent, lemmas. Lemmas and theorems are OK now (but untranslated), thanks. -- Jean-Pierre

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: Bug?

2010-10-29 Thread Stephan Witt
Am 29.10.2010 um 16:36 schrieb Richard Heck: > On 10/29/2010 10:23 AM, Jürgen Spitzmüller wrote: >> Frederick Noronha wrote: >> >>> Letterine is for creating drop caps. It works fine for me, EXCEPT when >>> there is an inverted comma in the text such as >>> >>> I’d told you >>> >> Sure, a

Bug #4624: Export with embedded bbl file

2010-10-29 Thread Richard Heck
So, here is the current status. I have a python script that works, and I can export a LaTeX file with the bbl file copied in place of the \bibliography command. The only hitch is that this only works with a single bibliography, not with multiple ones or sectioned ones. In that case, the scrip

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: [Patch] Rename "Invisible" in View menu to "Hidden|H".

2010-10-29 Thread John McCabe-Dansted
On Fri, Oct 29, 2010 at 6:00 AM, RGH wrote: > Committed, thanks. > > I'll tell you what I'd also like: A Close-this-document-set option, that > would close the master and all its children, NOT hide them. If you're > interested > > Richard Thanks for the offer. I'll consider myself lucky if I

Re: RefStyle Patch

2010-10-29 Thread Jean-Pierre Chrétien
Richard Heck a écrit : On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote: Perhaps we can do this: (i) Try to get translations from our own translators of theorem and lemma, if that covers everything prettyref does, that we can hardcode into LaTeXFeatures.cpp, so that we at least do as we

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