Re: #8187: APA layout provides invalid styles

2012-07-12 Thread Maaneli D
Thanks, I did not initially use the fixed version when trying to include the graph. However, after using the fixed version, it worked, although I now have a couple questions about the fixed version.  First, although the graph shows up on the PDF, I'm not sure how to format it such that I can ce

Re: #8187: APA layout provides invalid styles

2012-07-12 Thread Uwe Stöhr
Am 11.07.2012 04:20, schrieb Maaneli D: I'm using the Lyx APA format, and I am trying to include a Microsoft Excel graph as a graphic using the "insert figure float" option. The Lyx editor allows me to input the graph into the figure box, but when I try to compile with "View PDF", it fails and

Re: Undo.cpp reports an error on trunk

2012-07-12 Thread Pavel Sanda
Richard Heck wrote: >> This leads to the harmless message above, but more importantly, it means >> that the undo stack is lost every time a file is saved-as. This looks like >> a regression to me. >> >> Richard, would it seem right to add a parameter to Buffer::reload asking >> to preserve the u

LyX, XeTeX, bidi and Hebrew

2012-07-12 Thread Ronen Abravanel
Hello to you all, as the Hebrew support of LaTeX is not developed for the last several years, I decided to try and export Hebrew document to PDF using XeTeX, where the grate Bidi packge by Vafa Khalighi is under active development, and merged in polyglossia. LyX 2.0 support XeTeX support, but the

cannot upload files to bugzilla?

2012-07-12 Thread Liviu Andronic
Dear all I am trying to upload a file to Bugzilla [1] but it always fails (I tried in Midori and Opera) with the same error message: "You did not specify a file to attach." I'm pretty sure that I did specify a file. Is this a known issue, and could I work around it? Regards Liviu [1] https://bug

Re: Undo.cpp reports an error on trunk

2012-07-12 Thread Richard Heck
On 07/12/2012 07:31 AM, Jean-Marc Lasgouttes wrote: Le 11/07/2012 23:05, Scott Kostyshak a écrit : git bisect leads me here: bbbc2b654175edbccb1ce54ae6dbb15f8a042360 which is related to this ticket: http://www.lyx.org/trac/ticket/8159 I am not surprised that this change leads to this kind of

Re: regression bug: "Go to label" broken in read-only documents

2012-07-12 Thread Jean-Marc Lasgouttes
Le 07/07/2012 00:13, Uwe Stöhr a écrit : In branch we have a regression bug that the "Go to label" feature broken in read-only documents: http://www.lyx.org/trac/ticket/8177 I just had a quick look but as I don't know this part of code. Could anybody else please have a look? See my comment the

Re: Undo.cpp reports an error on trunk

2012-07-12 Thread Jean-Marc Lasgouttes
Le 11/07/2012 23:05, Scott Kostyshak a écrit : git bisect leads me here: bbbc2b654175edbccb1ce54ae6dbb15f8a042360 which is related to this ticket: http://www.lyx.org/trac/ticket/8159 I am not surprised that this change leads to this kind of problems (which are harmless AFAICS). What happens

Re: questions and proposal regarding enum FuncAttribs

2012-07-12 Thread Jean-Marc Lasgouttes
Le 12/07/2012 09:44, Scott Kostyshak a écrit : It seems that there are many LFUNs that would fall under the description of the "Argument" flag (currently help-open is the only LFUN to specify it). If this flag were accurately used, would it be desired to have a centralized checking of an empty ar

RE: StatWeave integration

2012-07-12 Thread Scott Kostyshak
From: Brian Quistorff [bquisto...@gmail.com] Sent: Wednesday, July 11, 2012 10:03 AM >Would these be good to put in the stock LyX distribution? I would like to see this module make it in to the stock LyX distribution. I think many people could be interested. However, I think the unofficial polic

questions and proposal regarding enum FuncAttribs

2012-07-12 Thread Scott Kostyshak
I've found uses only of the following FuncAttribs values (from grepping for the funcHasFlag function): AtPoint, ReadOnly, NoBuffer, NoInternal The following values are not being used at all: Argument, NoUpdate, SingleParUpdate. Are they still left around because they might be useful in the future