Fwd: LyXAction, LyXFunc

2010-02-08 Thread Manoj Rajagopalan
Hi all, Re-sending. I am trying to understand the LyX flow of control. Appreciate any help. Apologies for the duplicate. Thanks, Manoj -- Forwarded Message -- Subject: LyXAction, LyXFunc Date: Sunday 07 February 2010 From: Manoj Rajagopalan To: LyX Developer List Hi all

Re: about the libintl version in the LyX windows installer

2010-02-08 Thread Joost Verburg
On 2/8/2010 7:40 PM, Uwe Stöhr wrote: > Looks like I didn't receive it. Could you try to send it again? Thx. I uploaded it now: http://www.fkurth.de/uwest/LyX/libintl-0.17-windows-3.zip I don't see a MSVC project for gettext itself in there, just a sample MSVC application that uses gettext.

Re: about the libintl version in the LyX windows installer

2010-02-08 Thread Uwe Stöhr
I forgot to link the bug report where we found out that the old gettext version 0.15 in the LyX Windows installers cause the language change bug: http://www.lyx.org/trac/ticket/5034 regards Uwe

Re: [patch] implement multirow support - request for help

2010-02-08 Thread Uwe Stöhr
> Attached is what I currently have to support multirows. > > There is currently one issue I cannot solve: The metrics and drawing > of the cells that are part of a multirow is broken. The drawing of > the first multirow cell is however correct. I failed to figure out > this problem and therefore

Re: \middle

2010-02-08 Thread Uwe Stöhr
> This can be implemented, see > http://www.lyx.org/trac/ticket/1632 > > eTeX is now actually part of every LaTeX distribution, so we can indeed start implement \middle. Implementing this requires more work and testing than I thought. I'm therefore postponing this. But maybe another one likes t

Bug 6412 and changeset 31451

2010-02-08 Thread BH
As I just noted on Trac (bug 6412), the problem I've had on Mac with inserting citations, changes to the document preamble, etc. is the result of changest 31451. Abdel, can you take a look? http://www.lyx.org/trac/ticket/6412 BH

Re: about the libintl version in the LyX windows installer

2010-02-08 Thread Uwe Stöhr
> Looks like I didn't receive it. Could you try to send it again? Thx. I uploaded it now: http://www.fkurth.de/uwest/LyX/libintl-0.17-windows-3.zip > You have to tell the compiler which functions need to be exported in the DLL so they can be > called from external programs. There are also diffe

Compilation failure after r33370

2010-02-08 Thread Uwe Stöhr
Since r33370 I get this compilation error: Creating library release\lyx.lib and object release\lyx.exp InsetFloat.obj : error LNK2019: unresolved external symbol "public: virtual __th iscall lyx::InsetFloat::~InsetFloat(void)" (??1insetfl...@lyx@@u...@xz) reference d in function "public: virt

Re: 1.6.5 mathed crash

2010-02-08 Thread Vincent van Ravesteijn
Joost Verburg schreef: Hi, I was just typing some math and 1.6.5 crashed with the following assertion: lyx-1.6.5\src\support\lassert.cpp(21): ASSERTION pos < size() VIOLATED IN lyx-1.6.5\src\mathed\MathData.cpp:56 Does anyone know whether this may be related to a known bug (I couldn't fin

Another Lyx Error Detected

2010-02-08 Thread Lara Pagano
Hello again, Another problem I am having is with too many floating figures. I have a large document with anywhere from 3-100 figures within each chapter. I keep getting the error regarding too many floats. I worked around this issue by placing /clearpage every so often to make it produce a PDF.

1.6.5 mathed crash

2010-02-08 Thread Joost Verburg
Hi, I was just typing some math and 1.6.5 crashed with the following assertion: lyx-1.6.5\src\support\lassert.cpp(21): ASSERTION pos < size() VIOLATED IN lyx-1.6.5\src\mathed\MathData.cpp:56 Does anyone know whether this may be related to a known bug (I couldn't find this assertion in trac)?

Re: Lyx Bug detected

2010-02-08 Thread Vincent van Ravesteijn
Vincent van Ravesteijn schreef: Lara Pagano schreef: Hi, I was working on my Thesis document within Lyx and it crashed all of a sudden. I got an error saying: Lyx: SIGSEGV signal caught. I am not sure what to do because I can go into the document for maybe 1 or 2 minutes before it crashes a

Re: Lyx Bug detected

2010-02-08 Thread Vincent van Ravesteijn
Lara Pagano schreef: Hi, I was working on my Thesis document within Lyx and it crashed all of a sudden. I got an error saying: Lyx: SIGSEGV signal caught. I am not sure what to do because I can go into the document for maybe 1 or 2 minutes before it crashes again. I can not recall changing an

Lyx Bug detected

2010-02-08 Thread Lara Pagano
Hi, I was working on my Thesis document within Lyx and it crashed all of a sudden. I got an error saying: Lyx: SIGSEGV signal caught. I am not sure what to do because I can go into the document for maybe 1 or 2 minutes before it crashes again. I can not recall changing anything within the docum

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread Jürgen Spitzmüller
John McCabe-Dansted wrote: > On Mon, Feb 8, 2010 at 9:37 PM, Jürgen Spitzmüller wrote: > > + for (i = 0; i < num_lines; ++i) { > > (attached) and committed. Jürgen

Re: about the libintl version in the LyX windows installer

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 06:10 PM, Joost Verburg wrote: On 2/7/2010 10:25 PM, Uwe Stöhr wrote: I found another repository that includes an MSVC project file. That's the ZIP-file I sent you. (Unfortunately I cannot find the link to it any longer.) Looks like I didn't receive it. Could you try to send it a

Re: about the libintl version in the LyX windows installer

2010-02-08 Thread Joost Verburg
On 2/7/2010 10:25 PM, Uwe Stöhr wrote: I found another repository that includes an MSVC project file. That's the ZIP-file I sent you. (Unfortunately I cannot find the link to it any longer.) Looks like I didn't receive it. Could you try to send it again? Thx. > I remember trying this one bef

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread John McCabe-Dansted
On Mon, Feb 8, 2010 at 9:37 PM, Jürgen Spitzmüller wrote: > +       for (i = 0; i < num_lines; ++i) { (attached) -- John C. McCabe-Dansted Index: mathed/MacroTable.h === --- mathed/MacroTable.h (revision 33347) +++ mathed/MacroTabl

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread Jürgen Spitzmüller
John McCabe-Dansted wrote: > see attached. Thanks, Looks good from my POV. Final nitpick: > + for (i=0;i

Re: Wishlist: groups for "program listings" similiar to "graphics groups"

2010-02-08 Thread Bo Peng
> After applying lots of such settings over and over, a grouping would > be useful, in the same manner as for graphics. When several listings belong > to the same group, changing settings for one changes the settings for all in > that group. And new code snippets just need to be added to the correc

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread John McCabe-Dansted
On Mon, Feb 8, 2010 at 7:43 PM, Jürgen Spitzmüller wrote: > John McCabe-Dansted wrote: >> Something like the attached then? > > Sort of, yes. Although I would, to be in line with what we have, do in > MathMacroTemplate::write > >        int i = 0; > [...] see attached. -- John C. McCabe-Dansted

Re: [PATCH] Re: Language detection [was: offtopic blog]

2010-02-08 Thread Jürgen Spitzmüller
Jürgen Spitzmüller wrote: > Here's the patch. polished version that also handles multipart documents. Jürgen Index: src/Buffer.h === --- src/Buffer.h (Revision 33363) +++ src/Buffer.h (Arbeitskopie) @@ -375,6 +375,8 @@ /// bool

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread Jürgen Spitzmüller
John McCabe-Dansted wrote: > Something like the attached then? Sort of, yes. Although I would, to be in line with what we have, do in MathMacroTemplate::write int i = 0; [...] if (os.latex()) { // writing .tex. done. os << "\n";

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread John McCabe-Dansted
On Mon, Feb 8, 2010 at 4:30 PM, Jürgen Spitzmüller wrote: > John McCabe-Dansted wrote: >> Do you mean something like the writeLaTeX function in BufferParams.cpp >> that has TexRow passed in, and itself calls "texrow.newline();"? > > I mean, make the write function an int and then call texrow.newli

Re: r33302 - lyx-devel/trunk/src

2010-02-08 Thread Jean-Marc Lasgouttes
Tommaso Cucinotta writes: > Jean-Marc Lasgouttes wrote: >>> Would the attached patch make sense to both of you? >>> > I had worked to a smaller patch concerning only regexp, in which I had > introduced a REGEXP_CODE, and was using such code in insetAllowed(), > and I could see regexp insets

Re: r33362 - lyx-devel/trunk/src/frontends/qt4/ui

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 11:52 AM, lasgout...@lyx.org wrote: Author: lasgouttes Date: Mon Feb 8 11:52:16 2010 New Revision: 33362 URL: http://www.lyx.org/trac/changeset/33362 Log: fix compilation with qt 4.2 Thanks. Abdel.

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Pavel Sanda
Abdelrazak Younes wrote: >> 4.4 was supposed to be 4.2 compatible (4.3 was not on contrary). >> my point was that your xml line will be problem even if we switch >> to 4.4. >> > > I would be surprise if so. Else Nokia has made a big mess with Qt4.5 you are probably right. anyway using qt 4.2 d

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 10:27 AM, Pavel Sanda wrote: Abdelrazak Younes wrote: On 02/08/2010 09:54 AM, Pavel Sanda wrote: Abdelrazak Younes wrote: Hum... couldn't we just forget about 4.2? I know, this fix is not a big this doesnt solve much. you will have problem to compil

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Pavel Sanda
Abdelrazak Younes wrote: > On 02/08/2010 09:54 AM, Pavel Sanda wrote: >> Abdelrazak Younes wrote: >> >>> Hum... couldn't we just forget about 4.2? I know, this fix is not a big >>> >> this doesnt solve much. you will have problem to compile it even under >> 4.4. >> >> my 'solution' is to

[PATCH] Re: Language detection [was: offtopic blog]

2010-02-08 Thread Jürgen Spitzmüller
Jürgen Spitzmüller wrote: > > Agreed. However, currently language switching is far too cumbersome: > > > > a) Edit>Text-style>Custom>...>select from an "endless" list, or > > > > b) M-x language ... (where you need to know the correct name of the > > desired language) > > I

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 09:54 AM, Pavel Sanda wrote: Abdelrazak Younes wrote: Hum... couldn't we just forget about 4.2? I know, this fix is not a big this doesnt solve much. you will have problem to compile it even under 4.4. my 'solution' is to have qt 4.2 locally compiled without instalation

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread Jean-Marc Lasgouttes
John McCabe-Dansted writes: > Also... I was thinking that it should be possible to define a > texrowStream object encapsulates an odocstream and a TeXRow and > automatically calls newline() whenever a newline is written to it, but > presumably there is some reason why this approach was not taken.

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Pavel Sanda
Abdelrazak Younes wrote: > Hum... couldn't we just forget about 4.2? I know, this fix is not a big this doesnt solve much. you will have problem to compile it even under 4.4. my 'solution' is to have qt 4.2 locally compiled without instalation and run its designer for .ui work. pavel

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 09:48 AM, Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: Hum... couldn't we just forget about 4.2? I know, this fix is not a big effort but I have to install compile and install Qt 4.2, and then do this change for every dialog I touch... fastidious :-/ Some people (J

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Jürgen Spitzmüller
Abdelrazak Younes wrote: > Hum... couldn't we just forget about 4.2? I know, this fix is not a big > effort but I have to install compile and install Qt 4.2, and then do > this change for every dialog I touch... fastidious :-/ Some people (Jean-Marc amongst them, IIRC) still run 4.2. Jürgen

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 09:31 AM, Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: So the fix is only to revert that line? I think you also need to adapt the geometry or sizeHint settings. Hum... couldn't we just forget about 4.2? I know, this fix is not a big effort but I have to inst

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Jürgen Spitzmüller
Abdelrazak Younes wrote: > So the fix is only to revert that line? I think you also need to adapt the geometry or sizeHint settings. Jürgen

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread Jürgen Spitzmüller
John McCabe-Dansted wrote: > Do you mean something like the writeLaTeX function in BufferParams.cpp > that has TexRow passed in, and itself calls "texrow.newline();"? I mean, make the write function an int and then call texrow.newline() accordingly in the buffer function. Jürgen

Re: r33351 - in lyx-devel/trunk/src: frontends/qt4 frontends/qt4/ui insets

2010-02-08 Thread Abdelrazak Younes
On 02/08/2010 03:18 AM, Pavel Sanda wrote: Modified: lyx-devel/trunk/src/frontends/qt4/ui/BoxUi.ui == --- lyx-devel/trunk/src/frontends/qt4/ui/BoxUi.ui Sun Feb 7 21:25:53 2010(r33350) +++ lyx-devel/trunk/s

Re: [Patch] Possible fix for 6502: ... LaTeX Errors Dialog highlighting wrong line.

2010-02-08 Thread John McCabe-Dansted
On Mon, Feb 8, 2010 at 3:12 PM, Jürgen Spitzmüller wrote: > John McCabe-Dansted wrote: >> It is just a missing "d->texrow.newline();". >> >> The attached patch adds this back in. I've tested this patch against >> branch and trunk. Shall we apply this to trunk now? > > Looks much better. > > Howeve