Re: CVS compilation
Andre Poenitz wrote: > > > ../src/lyx_main.C:635: no matching function for call to `LyXLex::IsOK > > ()' > > ../src/lyx_main.C:643: no matching function for call to `LyXLex::IsOK > > ()' > > ../src/lyx_main.C:654: no matching function for call to > > `LyXLex::GetString ()' > > Change this to '::isOk' and '::getString' and it should be ok. "isOK"is it ... Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: CVS compilation
Herbert Voss wrote: > > Michael Schmitt wrote: > > > > you need to patch lyx_main.C in order to be able to compile LyX. > > I patched and this is what happens??? > Your patch didn't take or something. I just put the indicated changes in by hand and it worked fine, changing all IsOK's to isOK and GetString to getString. Check to see what is in lyx_main.C Garst
Re: CVS compilation
> ../src/lyx_main.C:635: no matching function for call to `LyXLex::IsOK > ()' > ../src/lyx_main.C:643: no matching function for call to `LyXLex::IsOK > ()' > ../src/lyx_main.C:654: no matching function for call to > `LyXLex::GetString ()' Change this to '::isOk' and '::getString' and it should be ok. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: CVS compilation
Michael Schmitt wrote: > > you need to patch lyx_main.C in order to be able to compile LyX. I patched and this is what happens??? g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost-isystem /usr/X11R6/include -g -O -fno-exceptions -W -Wall -DLYX_DIR=\"/usr/share/lyx\" \ -DTOP_SRCDIR=\"..\" -c ../src/lyx_main.C ../src/lyx_main.C: In method `void LyX::readUIFile(const string &)': ../src/lyx_main.C:635: no matching function for call to `LyXLex::IsOK ()' ../src/lyx_main.C:643: no matching function for call to `LyXLex::IsOK ()' ../src/lyx_main.C:654: no matching function for call to `LyXLex::GetString ()' make[3]: *** [lyx_main.o] Error 1 make[3]: Leaving directory `/var/tmp/lyx/lyx-devel/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/lyx/lyx-devel/src' make[1]: *** [all-recursive-am] Error 2 make[1]: Leaving directory `/var/tmp/lyx/lyx-devel/src' make: *** [all-recursive] Error 1 Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
convenience key bindings
new standard key bindings for "math-macro-arg n". I am running out of "bindable keys" in the "M-m bind space". But I guess things like "context sensitive keybindings" are 1.3 material now... Andre' -- André Pönitz . [EMAIL PROTECTED] Index: math.bind === RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/bind/math.bind,v retrieving revision 1.5 diff -u -p -r1.5 math.bind --- math.bind 2001/07/25 12:37:41 1.5 +++ math.bind 2001/08/07 06:17:19 @@ -37,7 +37,7 @@ \bind "M-m g" "math-greek" \bind "M-m S-G""math-greek-toggle" -\bind "M-m o" "math-insert oint" +#\bind "M-m o" "math-insert oint" \bind "M-m p" "math-insert partial" \bind "M-m r" "math-insert root" \bind "M-m l" "math-limits" @@ -47,6 +47,16 @@ \bind "M-m 8" "math-insert infty" \bind "M-m v" "accent-vector" +\bind "M-m o 1""math-macro-arg 1" +\bind "M-m o 2""math-macro-arg 2" +\bind "M-m o 3""math-macro-arg 3" +\bind "M-m o 4""math-macro-arg 4" +\bind "M-m o 5""math-macro-arg 5" +\bind "M-m o 6""math-macro-arg 6" +\bind "M-m o 7""math-macro-arg 7" +\bind "M-m o 8""math-macro-arg 8" +\bind "M-m o 9""math-macro-arg 9" + \bind "M-m t t" "math-mutate dump" \bind "M-m t a" "math-mutate align" \bind "M-m t i" "math-mutate inline"
LyXLex::_I_sOk, _G_etString...
... seem to be used in lyx_main. I guess they need lower case letters at the beginning, too. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: lyx file format changes
On Mon, Aug 06, 2001 at 04:16:30PM +0200, Edwin Leuven wrote: > > So that XML parsers will handle it. (but I don't think we want to use > > xml parsers (perhaps a sax parser)) > > For what it's worth, the Qt doc states: > > The XML module provides a well-formed XML parser using the SAX2 > (Simple API for XML) interface plus an implementation of the DOM > Level 2 (Document Object Model). As I said in my earlier note, we probably don't need this degree of compliance. We already have our own custom DOM in the LyX kernel (and always have, too). The XML parser we'll need only has to handle one valid format. We can, furthermore, document that parser in XSL, thereby making LyX documents portable. As for any inverse conversions, I'm sure someone somewhere is developing an open-source XML/XSL parser that'll convert documents between DTD's. No need to duplicate those efforts --- there's more than enough for LyX do deal with. BTW: I think, with all of the file format changes, that maybe it's time to modularize the file reading/writing parts of the code and create a "translator" binary to convert from older to newer formats. That would cut down on the amount of backward-compatibility code the LyX kernel has to carry around, and will permit our users to convert their older files without too much effort. -- John Weiss "Not through coercion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: lyx file format changes
On Mon, Aug 06, 2001 at 03:27:53PM +0200, Asger K. Alstrup Nielsen wrote: > On Mon, 6 Aug 2001, John Levon wrote: > > > > No, I don't think you understand what I mean by XML-like. Let's call > > > it well-formed XML instead. > > I guess the point is that we don't want to a full-blown XML parser in LyX. > > Therefore, the LyX document format can look like XML, but there > are constraints to what the program will read. E.g. some well-formed > XML documents will be rejected by LyX. Having recently done an XML seminar at work, I can offer the following to the discussion: - Well-Formed XML: A text file following the minimal requirements for an XML document. This includes the initial "" tag, a single root-level node, no cross-nested blocks, and a few other simple rules. - Valid XML: A well-formed XML file that conforms to a known format. Thus, LyX v12.9 files will be valid XML files. For "well-formed", think "lex". For "valid", think "yacc". As for fear of an "XML parser", there are, IIRC, levels of compliance when it comes to parsers. You can write an XML parser that only reads XML files in a specific valid format. Nothing wrong there. A fully-compliant parser will also parse XSL files, enabling it to read any XML document ever written, now or in the future. That, we do not need. Once we do design an XML-based LyX format, I suggest we document the format using XSL. There's no magic around XSL: it's just an XML document that uses a format designed for defining other XML formats. I'll even volunteer to work on it (I'd like to improve my XML skills). -- John Weiss "Not through coercion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Graphic insert questions
I ineserted a 2143 byte png file into a table and got a blank box. Then I trie view ps, and got an error dialpg about a failure to file x to /tmp ... a couple of times. Then the LyX view showed an error converting file message, but the ps view came out fine. I looked in the directory (not my lyxdocs directory) containing the .png file and found a 30k+ .eps file. Going back to the lyx file I see oversized boxes with "error converting" in them. Apparently things are working better than lyx thinks. What is going on? Garst
Crash using line-delete-forward in table
I am using Lyx 1.1.6fix3. I am attaching a file that causes a Lyx crash. If I go to the first column in the first row of the table, and then issue line-delete-forward, lyx crashes. If the cursor is in the red box of the column, it does not crash, but if it before the red box, it does crash. Here is a gdb backtrace. I see in the mailing lists that someone else reported a similar problem. --- #0 0x0 in ?? () #1 0x805831f in BufferView::Pimpl::cursorToggle (this=0x8320f00) at BufferView_pimpl.C:1129 #2 0x8252a04 in SigC::ObjectSlot0_::callback ( d=0x8321934) at ../sigc++/object_slot.h:56 #3 0x8251c9e in SigC::Signal0 >::emit ( this=0x8320f1c) at ../../../sigc++/slot.h:260 #4 0x807a4fe in Timeout::emit (this=0x8320f1c) at Timeout.C:78 #5 0x807a3a5 in C_intern_timeout_cb (data=0x8320f1c) at Timeout.C:29 #6 0x822ae7f in fl_handle_timeouts () at ../sigc++/slot.h:194 #7 0x821bf63 in fl_set_idle_delta () at ../sigc++/slot.h:194 #8 0x821af0e in fl_last_event () at ../sigc++/slot.h:194 #9 0x821b798 in fl_treat_interaction_events () at ../sigc++/slot.h:194 #10 0x821b7c7 in fl_check_forms () at ../sigc++/slot.h:194 #11 0x81b79c0 in GUIRunTime::runTime () at GUIRunTime.C:79 #12 0x80cfaac in LyXGUI::runTime (this=0x82f2070) at lyx_gui.C:419 #13 0x80d1972 in LyX::LyX (this=0x8047798, argc=0x80477b8, argv=0x8047804) at ../src/lyx_main.C:168 #14 0x810c3cc in main (argc=1, argv=0x8047804) at ../src/main.C:40 #15 0x804e96e in __start () -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED]| (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 #LyX 1.1 created this file. For more info see http://www.lyx.org/ \lyxformat 218 \textclass article \language english \inputencoding auto \fontscheme default \graphics default \paperfontsize 12 \spacing single \papersize Default \paperpackage a4 \use_geometry 1 \use_amsmath 0 \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip 1in \quotes_language english \quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default \layout Title TEACH \newline Registration --- Fall Term 2001 \layout Date \SpecialChar ~ \layout Standard \begin_inset Tabular \begin_inset Text \layout Standard Parent's Names: \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \SpecialChar ~ \end_inset \begin_inset Text \layout Standard Address: \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard Telephone Number: \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard Email Address: \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard Emergency Name & \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard Phone Number: \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Text \layout Standard Home Church: \end_inset \begin_inset Text \layout Standard \end_inset \begin_inset Tex
Bug list - update again
Sorry boys, there are more bugs in the current cvs code. I wish you good luck. Michael -- == Michael Schmittphone: +49 451 500 3725 Institute for Telematics secretary: +49 451 500 3721 Medical University of Luebeck fax: +49 451 500 3722 Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de == Bug list (with some proposals for simple improvements) Please comment out (//) fixed bugs and send the file back to [EMAIL PROTECTED] * - Insert/Special character/Linebreak shows a very strange behaviour within mathed especially if you change from math formula to display formula afterwards - Is it possible to make a menu gray if all subitems are gray (as it is the case with Insert/Floats in mathed)? - When saving a document, mathed swallows all "\sum". - The current file format defines a "status" and a "collapsed" tag for ERTs; intended or faulty? - Uninitialized memory read (this one is _new_!) UMR: Uninitialized memory read This is occurring while in: XListFonts [FontNames.c] FontInfo::query() [FontInfo.C:123] FontInfo::getFontname(int) [FontInfo.h:43] FontLoader::doLoad(LyXFont::FONT_FAMILY,LyXFont::FONT_SERIES,LyXFont::FONT_SHAPE,LyXFont::FONT_SIZE) [FontLoader.C:243] lyxfont::descent(char,const LyXFont&) [FontLoader.h:49] mathed_string_height(MathTextCodes,MathStyles,const lyxstring&,int&,int&) [support.C:580] mathed_string_dim(MathTextCodes,MathStyles,const lyxstring&,int&,int&,int&) [support.C:570] MathSymbolInset::metrics(MathStyles)const [math_symbolinset.C:44] MathXArray::metrics(MathStyles)const [xarray.C:38] MathNestInset::metrics(MathStyles)const [math_nestinset.C:58] MathGridInset::metrics(MathStyles)const [math_gridinset.C:80] MathMatrixInset::metrics(MathStyles)const [math_matrixinset.C:101] InsetFormula::metrics()const [formula.C:156] InsetFormula::read(LyXLex&) [formula.C:123] InsetFormulaBase::read(const Buffer*,LyXLex&) [formulabase.C:130] Buffer::readInset(LyXLex&,Paragraph*&,int&,LyXFont&) [buffer.C:1500] Buffer::parseSingleLyXformat2Token(LyXLex&,Paragraph*&,Paragraph*&,const lyxstring&,int&,unsigned int&,LyXFont&) [buffer.C:1047] Buffer::readLyXformat2(LyXLex&,Paragraph*) [buffer.C:365] Buffer::readFile(LyXLex&,Paragraph*) [buffer.C:1542] BufferList::readFile(const lyxstring&,bool) [bufferlist.C:403] InsetInclude::loadIfNeeded()const [insetinclude.C:221] InsetInclude::validate(LaTeXFeatures&)const [insetinclude.C:405] Paragraph::validate(LaTeXFeatures&)const [paragraph.C:380] Buffer::validate(LaTeXFeatures&)const [buffer.C:3458] Buffer::makeLaTeXFile(const lyxstring&,const lyxstring&,bool,bool) [buffer.C:1959] Exporter::Export(Buffer*,const lyxstring&,bool,lyxstring&) [exporter.C:79] Exporter::Preview(Buffer*,const lyxstring&) [exporter.C:107] LyXFunc::dispatch(int,const lyxstring&) [lyxfunc.C:1053] LyXFunc::processKeySym(unsigned long,unsigned int) [lyxfunc.C:353] BufferView::Pimpl::workAreaKeyPress(unsigned long,unsigned int) [BufferView_pimpl.C:515] SigC::ObjectSlot2_::callback(void*,unsigned long,unsigned int) [object_slot.h:250] SigC::Signal2>::emit(const unsigned long&,const unsigned int&) [slot.h:456] WorkArea::work_area_handler(flobjs_*,int,int,int,int,void*) [basic_signal.h:450] C_WorkArea_work_area_handler [WorkArea.C:58] fl_handle_it [objects.c] fl_handle_object [libforms.a] fl_handle_form [forms.c] do_keyboard[forms.c] do_interaction_step [forms.c] fl_treat_interaction_events [libforms.a] fl_check_forms [libforms.a] GUIRunTime::runTime() [GUIRunTime.C:84] LyXGUI::runTime() [lyx_gui.C:316] LyX::LyX(int*,char**) [lyx_main.C:175] main [main.C:38] _start [crt1.o] Reading 1 byte from 0x1490f68 in the heap. Address 0x1490f68 is 1152 bytes into a malloc'd block at 0x1490ae8 of 1153 bytes. This block was allocated from: malloc [rtlib.o] XListFonts [FontNames.c] FontInfo::query() [FontInfo.C:123] FontInfo::getFontname(int) [FontInfo.h:43] FontLoader::doLoad(Ly
Bug list - update
Hi, enclosed please find an updated bug list. There are currently some ugly looking memory access errors. I think these should have highest priority (higher than drawing problems). As usual, the latest bugs are on top of the list. Michael -- == Michael Schmittphone: +49 451 500 3725 Institute for Telematics secretary: +49 451 500 3721 Medical University of Luebeck fax: +49 451 500 3722 Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de == Bug list (with some proposals for simple improvements) Please comment out (//) fixed bugs and send the file back to [EMAIL PROTECTED] * - Insert an ERT inside a text paragraph, delete it, undo the deletion and undo the deletion once again (even though there is nothing more to undo) FMR: Free memory read This is occurring while in: textHandleUndo(BufferView*,Undo*) [undo_funcs.C:166] textUndo(BufferView*) [undo_funcs.C:46] BufferView::menuUndo() [BufferView2.C:232] LyXFunc::dispatch(int,const lyxstring&) [lyxfunc.C:1121] Menubar::Pimpl::MenuCallback(flobjs_*,long) [Menubar_pimpl.C:581] C_Menubar_Pimpl_MenuCallback [Menubar_pimpl.C:529] fl_object_qread [libforms.a] fl_check_forms [libforms.a] GUIRunTime::runTime() [GUIRunTime.C:84] LyXGUI::runTime() [lyx_gui.C:316] LyX::LyX(int*,char**) [lyx_main.C:175] main [main.C:38] _start [crt1.o] Reading 4 bytes from 0x13f143c in the heap. Address 0x13f143c is 116 bytes into a freed block at 0x13f13c8 of 372 bytes. This block was allocated from: malloc [rtlib.o] __bUiLtIn_nEw [new1.cc:84] __builtin_new [rtlib.o] BufferView::Pimpl::Dispatch(kb_action,const lyxstring&) [BufferView_pimpl.C:2710] BufferView::Dispatch(kb_action,const lyxstring&) [BufferView.C:294] LyXFunc::dispatch(int,const lyxstring&) [lyxfunc.C:1597] _GLOBAL_.N.__Q37Toolbar5Pimpl11toolbarItem::ToolbarCB(flobjs_*,long) [Toolbar_pimpl.C:273] C_Toolbar_ToolbarCB [Toolbar_pimpl.C:284] fl_object_qread [libforms.a] fl_check_forms [libforms.a] GUIRunTime::runTime() [GUIRunTime.C:84] LyXGUI::runTime() [lyx_gui.C:316] LyX::LyX(int*,char**) [lyx_main.C:175] main [main.C:38] _start [crt1.o] There have been 15045 frees since this block was freed from: free [rtlib.o] __bUiLtIn_dElEtE [new2.cc:54] __builtin_delete [rtlib.o] InsetERT::~InsetERT() [inset.h:138] Paragraph::Pimpl::erase(int) [paragraph_pimpl.C:158] Paragraph::erase(int) [paragraph.C:468] CutAndPaste::cutSelection(Paragraph*,Paragraph**,int,int&,char,bool) [CutAndPaste.C:95] LyXText::cutSelection(BufferView*,bool) [text2.C:1709] BufferView::cut() [BufferView2.C:303] BufferView::Pimpl::Dispatch(kb_action,const lyxstring&) [BufferView_pimpl.C:2539] BufferView::Dispatch(kb_action,const lyxstring&) [BufferView.C:294] LyXFunc::dispatch(int,const lyxstring&) [lyxfunc.C:1597] LyXFunc::processKeySym(unsigned long,unsigned int) [lyxfunc.C:353] BufferView::Pimpl::workAreaKeyPress(unsigned long,unsigned int) [BufferView_pimpl.C:515] SigC::ObjectSlot2_::callback(void*,unsigned long,unsigned int) [object_slot.h:250] SigC::Signal2>::emit(const unsigned long&,const unsigned int&) [slot.h:456] WorkArea::work_area_handler(flobjs_*,int,int,int,int,void*) [basic_signal.h:450] C_WorkArea_work_area_handler [WorkArea.C:58] fl_handle_it [objects.c] fl_handle_object [libforms.a] fl_handle_form [forms.c] do_keyboard[forms.c] do_interaction_step [forms.c] fl_treat_interaction_events [libforms.a] fl_check_forms [libforms.a] GUIRunTime::runTime() [GUIRunTime.C:84] LyXGUI::runTime() [lyx_gui.C:316] LyX::LyX(int*,char**) [lyx_main.C:175] main [main.C:38] _start [crt1.o] - Add a note to an empty document; add two lines of text into the note; cut some of the text in both lines; undo the operation -> note is not drawn correctly - Add a footnote to an empty document then add some text into th
CVS compilation
Hi,
you need to patch lyx_main.C in order to be able to compile LyX.
Index: src/lyx_main.C
===
RCS file: /cvs/lyx/lyx-devel/src/lyx_main.C,v
retrieving revision 1.86
diff -u -r1.86 lyx_main.C
--- src/lyx_main.C 2001/08/03 18:28:04 1.86
+++ src/lyx_main.C 2001/08/06 21:05:57
@@ -632,7 +632,7 @@
<< " in " << ui_path << endl;
LyXLex lex(uitags, ui_last - 1);
lex.setFile(ui_path);
- if (!lex.IsOK()) {
+ if (!lex.isOK()) {
lyxerr << "Unable to set LyXLeX for ui file: " << ui_path
<< endl;
}
@@ -640,7 +640,7 @@
if (lyxerr.debugging(Debug::PARSER))
lex.printTable(lyxerr);
- while (lex.IsOK()) {
+ while (lex.isOK()) {
switch (lex.lex()) {
case ui_menuset:
menubackend.read(lex);
@@ -651,7 +651,7 @@
break;
default:
- if(!strip(lex.GetString()).empty())
+ if(!strip(lex.getString()).empty())
lex.printError("LyX::ReadUIFile: "
"Unknown menu tag:
`$$Token'");
break;
***
I have collected all warnings raised by g++ 2.95.3. There are no real
compiler warnings, just comments from you.
***
formulabase.C:121: warning: #warning This is needed as long the math
parser is not re-entrant
formulamacro.C:66: warning: #warning Need to unregister from
MathMacroTable.
formulamacro.C:76: warning: #warning This should not be needed in
reality...
math_cursor.C:1019: warning: #warning This is evil!
math_macrotable.C:63: warning: #warning who frees this?
insetbib.C:267: warning: #warning Ha, now we are mainly at 1.2.0 and it is
still here (Jug)
insetcaption.C:119: warning: #warning Implement me!
insetcaption.C:128: warning: #warning Implement me!
insetfloat.C:305: warning: #warning FIX!
insetfloatlist.C:63: warning: #warning Implement me please.
insetminipage.C:76: warning: #warning Remove this color definitions before
1.2.0 final!
insetquotes.C:260: warning: #warning How do we get the local language
here??
insettabular.C:620: warning: #warning fix scrolling when cellinset has
requested a scroll (Jug)!!!
insettabular.C:1300: warning: #warning Jrgen, please check. (Lgb)
insettext.C:68: warning: #warning this functions should probably go into
bufferview_funcs somehow (Jug)
insettext.C:2139: warning: #warning Dekel please have a look on this one
RTL? (Jug)
ImageLoaderXPM.C:65: warning: #warning This might be a dirty thing, but I
dont know any other solution.
FormFloat.C:32: warning: #warning Needs to be implemented. (Lgb)
xforms_helpers.C:42: warning: #warning Why cant this be done by a one pass
algo? (Lgb)
BufferView_pimpl.C:3222: warning: #warning Why is this code different from
specialChar() below? (JMarc)
buffer.C:305: warning: #warning And _why_ is this here? (Lgb)
lyxfunc.C:1172: warning: #warning Find another implementation here (or
another lyxfunc)!
paragraph.C:1598: warning: #warning For now we ALWAYS have to close the
foreign font settings if they are
paragraph.C:1599: warning: #warning there as we start another
\selectlanguage with the next paragraph if
paragraph.C:1600: warning: #warning we are in need of this. This should be
fixed sometime (Jug)
paragraph.C:1841: warning: #warning We should make this somewhat better,
any ideas? (Jug)
tabular-old.C:132: warning: #warning old l_getline
text.C:1024: warning: #warning Please fix me (Jug!)
text.C:1524: warning: #warning Something is rotten here! (Jug)
text.C:2275: warning: #warning Dekel please have a look on this one RTL?
(Jug)
text2.C:2144: warning: #warning I belive this code is wrong. (Lgb)
text2.C:2145: warning: #warning Jrgen, have a look at this. (Lgb)
trans.C:256: warning: #warning This code should be removed...
--
==
Michael Schmittphone: +49 451 500 3725
Institute for Telematics secretary: +49 451 500 3721
Medical University of Luebeck fax: +49 451 500 3722
Ratzeburger Allee 160 eMail: [EMAIL PROTECTED]
D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de
==
Re: Where is math_charinset.C?
* John Levon <[EMAIL PROTECTED]> [2001-08-06 17:45] schrieb: > On Mon, Aug 06, 2001 at 05:15:30PM +0200, Ronny Buchmann wrote: > > > but be careful that it doesnt merge modified files with the (older one) from >repository > > eh ? that's what you want anyway. you won't be able to commit unless you're up to >date. > yes, sorry dind't realize that someone already commited a patch which i had applied manually (and i had done some local modifications) so the merge was not as expected but nevertheless looking for merging conflicts too is quite useful cvs up 2>&1 | grep '^[C?]' > john > -- ronny
Re: Labels & citations
Michael Schmitt wrote: > > two remarks from a user's perspective: > > - Concerning your discussion this morning, I think it is a very nice >feature that references are updated if the corresponding label is >changed! I wonder if it makes sense to update references >even globally within all open documents. This would be very >useful for multipart documents. from my point of view it may be a feature but not an important one. you know, that I write a lot of stuff with lyx and I understand that global label controlling might be useful. but what are the real problems with labels? renaming -> no deleting -> might be, even though it makes no sense, because you can have so many labels as you like doublicat labels -> yes, especially in big docs the last one can be controlled by latex, also by lyx when you went into the reference menu. Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Labels & citations
Hi, two remarks from a user's perspective: - Concerning your discussion this morning, I think it is a very nice feature that references are updated if the corresponding label is changed! I wonder if it makes sense to update references even globally within all open documents. This would be very useful for multipart documents. - For multipart documents it would also make sense that the citation dialog takes into account all bibliography references of all open documents. Otherwise the user has to introduce a temporary bibliography reference in each sub-document. I think Dekel has made a proposal for this. What is the current status? If the implementation is nearly finished, I am willing to test it as much as you like if only it is included in 1.2.0 (yes, Lars, it is feature freeze, I know. But, hey, I will test it all day long :-)) Michael -- == Michael Schmittphone: +49 451 500 3725 Institute for Telematics secretary: +49 451 500 3721 Medical University of Luebeck fax: +49 451 500 3722 Ratzeburger Allee 160 eMail: [EMAIL PROTECTED] D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de ==
1.2.0cvs: Table cut and paste and redraw problems
As of latest CVS: 1) Create a table. Accept the defaults (5x5). 2) Fill the top line cells with anything, using tab to go to the next cell. 3) On the second row, as you insert characters, the red box around the cell is not drawn correctly until you enter enought characters to equal the width of the cell above. Also, try selecting text within a table cell, there are two things: *) Left-mouse-click drag does not work. *) Shift-arrow and then C-c, left-click elsewhere and C-v (this works but gives no visual feedback). -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2/28/92)
makecvs.log again
mathed Garst make[3]: Entering directory `/usr/local/garst/lyx-devel/src/mathed' make[3]: *** No rule to make target `math_bigopinset.C', needed by `math_bigopinset.lo'. Stop.
Re: lyx file format changes
John Levon wrote: > > On Mon, Aug 06, 2001 at 03:27:53PM +0200, Asger K. Alstrup Nielsen wrote: > > > One problem with XML is that a full parser carries a pretty big > > foot-print along with it, and it also introduces Yet Another > > Dependency. Finally, no good free C++ XML parsers are really available > > at this point to my knowledge. > > oh, I see. that makes sense ... > Yes indeed. I made patches on early 1.1.6 versions using libxml (DOM) for reading and SAX for output. This lead to code that was easy to write: basically I would copy the standard read or write method of a class (inset, paragraph etc.) and reorganize it a bit to use the DOM or SAX, thus leading to readXML and writeXML methodes. Using a DOM tree for input really makes things easier with current LyX code. Of course SAX would be easier if the LyX classes provided good constructors (the current ones are not meant to build complete objects since LyX fills the objects with data afterwards (with the read methods or with methods called due to user operations). Libxml is a quite big dependency. But I have seen a few new DOM parsers on freshmeat and sourceforge. As far of the status of the XML attempt is concerned : - layout and most insets worked - configure script was not updated - formula were not XML-ised at all (It looked a bit harder and somebody was reorganizing the code : is it over ?) sincerely, P.O.
Re: Where is math_charinset.C?
* John Levon <[EMAIL PROTECTED]> [2001-08-06 13:30] schrieb: > On Mon, Aug 06, 2001 at 01:14:05PM +0200, Andre Poenitz wrote: > > > > when you do "cvs commit *", it gives messages about files not in repository > > > with "cvs diff", the files are marked with '?' > > > > When I try 'cvs commit *' it gives 'Use cvs add to create...' error > > messages for every .o in the directory, too. Ok, I could filter them out > > to get only the interesting file names... > > just run : > > cvs up 2>&1 | grep ^\? > > >from the top dir but be careful that it doesnt merge modified files with the (older one) from repository "cvs -n up" is probably better -- ronny
Re: lyx file format changes
On Mon, Aug 06, 2001 at 03:27:53PM +0200, Asger K. Alstrup Nielsen wrote: > One problem with XML is that a full parser carries a pretty big > foot-print along with it, and it also introduces Yet Another > Dependency. Finally, no good free C++ XML parsers are really available > at this point to my knowledge. oh, I see. that makes sense ... john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: Quote v Quotation
On Mon, Aug 06, 2001 at 04:11:26PM +0100, Angus Leeming wrote: > On Monday 06 August 2001 16:01, Zvezdan Petkovic wrote: > > On Mon, Aug 06, 2001 at 03:52:27PM +0100, Angus Leeming wrote: > > > In the drop down list of possible layouts. > > > > > > What's the difference? > > > > > > Angus > > > > One is used for a short single paragraph quotes. The other for a > > multiple paragraph quotations. > > Thanks. Which is which? > > A I used words _quote_ and _quotation_ above. :-) -- Zvezdan Petkovic <[EMAIL PROTECTED]> http://www.cs.wm.edu/~zvezdan/
Re: Quote v Quotation
On Mon, Aug 06, 2001 at 03:52:27PM +0100, Angus Leeming wrote: > In the drop down list of possible layouts. > > What's the difference? > > Angus One is used for a short single paragraph quotes. The other for a multiple paragraph quotations. -- Zvezdan Petkovic <[EMAIL PROTECTED]> http://www.cs.wm.edu/~zvezdan/
RE: CVS Update: lyx-devel
On 06-Aug-2001 [EMAIL PROTECTED] wrote: > Log message: > Various update/redraw fixes. Cleaned up InsetERT and added a dialog for > changing between statuses. Save the statuses to file. Ok if possible it would be nice if people could try an updated version again, and see if this fixes the problem we had with crashes on insets. Also this should fix the problems we had with drawing TextInsets with background color. Please have a try and let me know. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ It's NO USE ... I've gone to "CLUB MED"!!
Quote v Quotation
In the drop down list of possible layouts. What's the difference? Angus
Re: compose key bug
On Thursday 02 August 2001 13:02, Lars Gullik Bjønnes wrote: > Angus Leeming <[EMAIL PROTECTED]> writes: > > | On Thursday 02 August 2001 12:19, Lars Gullik Bjønnes wrote: > | > Angus Leeming <[EMAIL PROTECTED]> writes: > | > > | > | When I press my compose key I get the minibuffer message "unknown > | function" > | > | and I can't create accented chars. Things work fine in other apps, so > | this > | > | appears to be a LyX problem not an X one. > | > | > | > | Do other people see this? > | > > | > If you turn on debugging... what does LyX think it sees? > | > | compose+e+' and LyX thinks that it sees eacute. The display however goes > | compose nothing > | e e > | ' e' > > and eacute is not working... bind file problem? Why would I be using a bind file for this? Surely, eacute is used to create the appropriate insetspecialchar using the cdef files. Anyway, this is not a local bind files problem. All my installed bind files are identical to those in HEAD. Things work this way whether or not I have set the preferences option "Override X dead keys". What else do I have to alter? Do things work as they should for other people? Things still seem wrong to me. If I hit the compose key, then the next two characters I hit should not be drawn on screen at all, only the translated character. (Ie, they should not be drawn on screen as e' and then translated to é.) At least, that's how other packages (kde stuff, emacs) does it. Angus
Re: lyx file format changes
On Mon, 6 Aug 2001, John Levon wrote: > > No, I don't think you understand what I mean by XML-like. Let's call > > it well-formed XML instead. > > I must admit I'm totally confused then ;) > > If it is XML, then it is well-formed XML and vice versa. So we are using > an XML format (good that's what I want ;) I guess the point is that we don't want to a full-blown XML parser in LyX. Therefore, the LyX document format can look like XML, but there are constraints to what the program will read. E.g. some well-formed XML documents will be rejected by LyX. The other way should be ok: All LyX documents would be well-formed XML documents. However, if you use a standard package to manipulate the LyX XML document, you might run into trouble. One problem with XML is that a full parser carries a pretty big foot-print along with it, and it also introduces Yet Another Dependency. Finally, no good free C++ XML parsers are really available at this point to my knowledge. Greets, Asger
Re: lyx file format changes
On Mon, Aug 06, 2001 at 02:50:13PM +0200, Lars Gullik Bjønnes wrote: > No, I don't think you understand what I mean by XML-like. Let's call > it well-formed XML instead. I must admit I'm totally confused then ;) If it is XML, then it is well-formed XML and vice versa. So we are using an XML format (good that's what I want ;) john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: Bug list
On 06-Aug-2001 Angus Leeming wrote: > Sure. I hate all this resize nonsense too. The appropriate place is probably > in FormBase, FormBaseDeprecated::show (patch please, I'm busy again!). > However, in this case Michael states that it isn't a resize problem. Maybe the icons have some sort of "transparent" background? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ When one knows women one pities men, but when one studies men, one excuses women. -- Horne Tooke
Re: lyx file format changes
On Mon, Aug 06, 2001 at 02:13:40PM +0200, Lars Gullik Bjønnes wrote: > | What ha[p[enned to the XML patches ? > > mmm... I don't want XML... but only something XML-like. why ? having something XML-like adds none of the advantages of XML[1], and all the disadvantages[2] It's like having a coat that is waterproof-like. It will be hot and uncomfy but won't keep you dry. john [1] leverage of standard tools, etc. [2] wordiness, inflexibility, etc. -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: Bug list
On Thursday 02 August 2001 20:47, John Levon wrote: > On Thu, Aug 02, 2001 at 09:37:09PM +0200, Michael Schmitt wrote: > > > > > >> - The dots dialog in the math panel is drawn accurately; at the right > > >> a fine vertical bar is not drawn > > > > >I suppose you mean inaccurately. Can you explain further, what do you > > >expect to > > >see ? I've never used this before ... > > > > See the attached screen shot. Note that I have _not_ stretched the window > > with the dots. Do you see that it is not painted correctly? You can see > > parts of the dialog below. > > hmm, what versions of xforms ? > > angus, can we disable resizing of ALL xforms dialogs ? I don't know of a single > one that resizes in any correct way !! Sure. I hate all this resize nonsense too. The appropriate place is probably in FormBase, FormBaseDeprecated::show (patch please, I'm busy again!). However, in this case Michael states that it isn't a resize problem. Angus
Re: finishing up 1.2.0
On 06-Aug-2001 John Levon wrote: >> I'm really hard trying to make the update/redraw code work correctly, >> but when I'm fixing something in one end there comes out something in >> another end. So this will need some time. > > of course the 3 or 4 tabular crashers are more important than the redraw > correctness, but it would be nice if you could get it /all/ working :)) That's the plan (and I never implied anything else :) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ If you wish to live wisely, ignore sayings -- including this one.
Re: Probelms while compiling with frontend=qt2
On Mon, Aug 06, 2001 at 12:02:50PM +0200, Pascal Francq wrote: > > messageboxes). I think we agreed on the following naming scheme (did we?): > > > QXXX.[Ch] > > > ui/QXXXDialog.[Ch] > > > QXXXDialogImpl.[Ch] > > > > gr.ed. > > So, it is better if I wait a liitle bit before starting something? You can add new dialogs (with the new names) but changing existing code would be awkward as I have to move practically every file. I should really get round to this and stop holding people up, but I have a deadline ... john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: Where is math_charinset.C?
On Mon, Aug 06, 2001 at 01:14:05PM +0200, Andre Poenitz wrote: > > when you do "cvs commit *", it gives messages about files not in repository > > with "cvs diff", the files are marked with '?' > > When I try 'cvs commit *' it gives 'Use cvs add to create...' error > messages for every .o in the directory, too. Ok, I could filter them out > to get only the interesting file names... just run : cvs up 2>&1 | grep ^\? from the top dir john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: finishing up 1.2.0
On Mon, Aug 06, 2001 at 10:07:29AM +0200, Juergen Vigna wrote: > I'm really hard trying to make the update/redraw code work correctly, > but when I'm fixing something in one end there comes out something in > another end. So this will need some time. of course the 3 or 4 tabular crashers are more important than the redraw correctness, but it would be nice if you could get it /all/ working :)) john > > Jürgen > > -- > -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ > Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] > Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 > I-39100 Bozen Web: http://www.sad.it/~jug > -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ > > The truth is what is; what should be is a dirty lie. > -- Lenny Bruce > -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: lyx file format changes
On Mon, Aug 06, 2001 at 10:05:32AM +0200, Lars Gullik Bjønnes wrote: > | that we should change format inside a "fix" release and x > 0 will be a > | fix release where ONLY bugfixes should come in! > > We could have the simple compability code in the fix releases. But not > the real format changes of course. I'd really like to see an XML format for 1.3 ... as it would make things much easier to convert in the future ... What ha[p[enned to the XML patches ? john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: Let's try again to change the matrix dialog
On Mon, Aug 06, 2001 at 10:12:54AM +0200, Juergen Vigna wrote: > Ok I modified Emmanuel's solution just a bit, are people likeing this > solution? We could use the same for tabulars and just disable the 2 looks good to me john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Re: Where is math_charinset.C?
> when you do "cvs commit *", it gives messages about files not in repository > with "cvs diff", the files are marked with '?' When I try 'cvs commit *' it gives 'Use cvs add to create...' error messages for every .o in the directory, too. Ok, I could filter them out to get only the interesting file names... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Where is math_charinset.C?
* Andre Poenitz <[EMAIL PROTECTED]> [2001-08-06 08:42] schrieb: > > One thing that would have worked is keeping a separate tree that you > > never modify, but only update and try to build that after commits... > > That's a good idea. I'll try that at least if I go away for more than a > night... when you do "cvs commit *", it gives messages about files not in repository with "cvs diff", the files are marked with '?' "cvs commit" (without '*') only uses files in repository > > Andre' > -- ronny
Re: Probelms while compiling with frontend=qt2
> So, it is better if I wait a liitle bit before starting something? No, just keep the naming scheme in mind when you decide to add stuff... gr.ed.
Re: Probelms while compiling with frontend=qt2
On Friday 03 August 2001 14:53, Edwin Leuven wrote: > > Is there enough people to work on the qt2 port. > > the more the merrier > > > I can perhaps spent a > > little of my time to try to do some port of the dailogs to qt2. > > I think John is planning to do a renaming operation in the qt2 directory so > for the moment I am not touching it (and still breeding on some > > messageboxes). I think we agreed on the following naming scheme (did we?): > > QXXX.[Ch] > > ui/QXXXDialog.[Ch] > > QXXXDialogImpl.[Ch] > > gr.ed. So, it is better if I wait a liitle bit before starting something? -- Ir Pascal Francq Researcher Université Libre de Bruxelles CAD/CAM Department Avenue F.D. Roosevelt, 50 CP 165/14 B-1050 Brussels BELGIUM Tel. +32-2-650 47 65 Fax +32-2-650 47 24 ICQ: 91206668
Re: finishing up 1.2.0
Lars Gullik Bjønnes wrote:
>
> Herbert Voss <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> | >
> | > Dekel Tsur <[EMAIL PROTECTED]> writes:
> | >
> | > | On Mon, Aug 06, 2001 at 01:29:04AM +0200, Lars Gullik Bjønnes wrote:
> | > | >
> | > | > - feature freeze as of _now_.
> | > | > - this mean that stuff like userdefinable floats will
> | > | > not be done for 1.2.0
> | > |
> | > | What about floatingfigure ? We need this for compatibility with 1.1.6
> | >
> | > At least the roumours say so...
> | > but do we really?
> | >
> | > One solution (at least one I would prefere,) is to convert
> | > floatingfigure into a regulare figure.
> |
> | sounds like a joke ... ;-)
> |
> | convert it into ert-insets and everything will be okay.
>
> that is probably harder...
maybe, but it's only a small ert in the gebinning
and one (\end{floatingfigure} or table) at the end of the paragraph
Herbert
--
http://www.educat.hu-berlin.de/~voss/lyx/
Re: math - latest cvs
Herbert Voss wrote: > > Andre Poenitz wrote: > > > > > Seems that your sources are foobar, I do not see that here. > > > > I think he has a version with the commented-out 'math_charinset.[Ch]' in > > Makefile.am > > I went back to the old makefile.am, but get always the same > error, also with a new cvs update??? okay, killed the whole math-dir -> new cvs and now it's okay. Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: math - latest cvs
Andre Poenitz wrote: > > > Seems that your sources are foobar, I do not see that here. > > I think he has a version with the commented-out 'math_charinset.[Ch]' in > Makefile.am I went back to the old makefile.am, but get always the same error, also with a new cvs update??? Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: finishing up 1.2.0
Lars Gullik Bjønnes wrote: > > Dekel Tsur <[EMAIL PROTECTED]> writes: > > | On Mon, Aug 06, 2001 at 01:29:04AM +0200, Lars Gullik Bjønnes wrote: > | > > | > - feature freeze as of _now_. > | > - this mean that stuff like userdefinable floats will > | > not be done for 1.2.0 > | > | What about floatingfigure ? We need this for compatibility with 1.1.6 > > At least the roumours say so... > but do we really? > > One solution (at least one I would prefere,) is to convert > floatingfigure into a regulare figure. sounds like a joke ... ;-) convert it into ert-insets and everything will be okay. Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
RE: Paragraph iterators
On 05-Aug-2001 Dekel Tsur wrote: > I've made a first attempt at creating paragraph iterators, and use them in > order to fix updating of references when the label is changed. > > I've created two different implementations. > In the first, we use the fact that we have a fixed structure of a document: > We have a list of paragraph, each paragraph containing a list of insets, and > each inset may contain several insettexts. Each insetext contains a list of > paragraph etc. IMO this is a nice solution I would have called getParagraph(int num) getFirstParagraph(int cell), but anyway IMO this is nice! > The second version is more general as no such assumption is made. > However, we pay a price in performance: we need to store a vector of pointers > to iterators instead of storing the iterators in vectors. > The code is a little bit ugly, but it can be improved using virtual methods > (the code should look familiar...). Too complicated for me poor being! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Kill Ugly Radio - Frank Zappa
New mathed bugs
1. Type ctrl-m x y The result is $yx$ instead of $xy$ 2. Sometimes, when quitting from LyX, LyX crashes. The problem is in mathed.
Re: finishing up 1.2.0
On 06-Aug-2001 Dekel Tsur wrote: > On Mon, Aug 06, 2001 at 01:29:04AM +0200, Lars Gullik Bjønnes wrote: >> >> - feature freeze as of _now_. >> - this mean that stuff like userdefinable floats will >> not be done for 1.2.0 > > What about floatingfigure ? We need this for compatibility with 1.1.6 What about the indented text feature? What do we read now? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ "Now here's something you're really going to like!" -- Rocket J. Squirrel
Re: finishing up 1.2.0
On Mon, Aug 06, 2001 at 01:29:04AM +0200, Lars Gullik Bjønnes wrote: > > - feature freeze as of _now_. > - this mean that stuff like userdefinable floats will > not be done for 1.2.0 What about floatingfigure ? We need this for compatibility with 1.1.6
Re: Paragraph iterators
On Mon, Aug 06, 2001 at 12:04:32AM +0200, Lars Gullik Bjønnes wrote: > | updated, so this is a bug (which should be fixed for 1.2.0). > > Perhaps... but we don't need paragraph iterators to do so. > I realize that having paragraph iterators will be nice, and that we > have several structures that could be converted to use iterators. > _but_ that conversion will not happen before 1.2.0. So for now I'd > like this fix to only traverse all the documents inset and do the > changes where needed. Both of the patches I sent work correctly and fix the bug. Why do you want to fix the bug using a hack which will be removed later? > Then we will return to the paragraph iterator approach in 1.3.0. btw. > I am planning to get rid of the paragraph linked list, and then the > paragraph iterators will need a completely different implementation, > one that even might be a lot simpler. The change would be minimal.
Re: Let's try again to change the matrix dialog
On 06-Aug-2001 Emmanuel GUREGHIAN wrote: > Juergen Vigna wrote: >> Ok now I could load them ;) >> >> What about this? > For me exactly what I needed, but the dialog size is a little larger. > Do you propose it on the mailing list ? Ok I modified Emmanuel's solution just a bit, are people likeing this solution? We could use the same for tabulars and just disable the 2 align-stuff-things (which I don't know for what they are). Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Give him an evasive answer. Magic: 13000 Internal Form Definition File (do not change) Number of forms: 1 Unit of measure: FL_COORD_PIXEL SnapGrid: 5 === FORM === Name: form_maths_matrix Width: 324 Height: 170 Number of Objects: 8 class: FL_BOX type: UP_BOX box: 0 0 324 170 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_DEFAULT_SIZE lcol: FL_BLACK label: shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: callback: argument: class: FL_VALSLIDER type: VERT_NICE_SLIDER box: 10 30 35 130 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Rows shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_rows callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_VALSLIDER type: HOR_NICE_SLIDER box: 50 30 260 25 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Columns shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_columns callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_BUTTON type: RETURN_BUTTON box: 55 130 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: OK shortcut: ^M resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_ok callback: C_FormBaseDeprecatedOKCB argument: 0 class: FL_BUTTON type: NORMAL_BUTTON box: 142 130 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Apply|#A shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_apply callback: C_FormBaseDeprecatedApplyCB argument: 0 class: FL_BUTTON type: NORMAL_BUTTON box: 230 130 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Cancel|^[ shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_cancel callback: C_FormBaseDeprecatedCancelCB argument: 0 class: FL_CHOICE type: NORMAL_CHOICE box: 52 91 122 30 boxtype: FL_FRAME_BOX colors: FL_COL1 FL_BLACK alignment: FL_ALIGN_TOP_LEFT style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Vertical align|#V shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: choice_valign callback: C_FormBaseDeprecatedInputCB argument: 0 class: FL_INPUT type: NORMAL_INPUT box: 194 90 116 32 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_MCOL alignment: FL_ALIGN_TOP_LEFT style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Horizontal align|#H shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: input_halign callback: C_FormBaseDeprecatedInputCB argument: 0 == create_the_forms
RE: finishing up 1.2.0
On 05-Aug-2001 Lars Gullik Bjønnes wrote: > > Ok, > > - feature freeze as of _now_. > - this mean that stuff like userdefinable floats will > not be done for 1.2.0 Good! > It seems that we are not that far from having something releasable. > But we have a lot of small bugs that require thinking and after that > one-liners to fix them... Well the problem is put the oneliners in the right code-segment! I'm really hard trying to make the update/redraw code work correctly, but when I'm fixing something in one end there comes out something in another end. So this will need some time. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ The truth is what is; what should be is a dirty lie. -- Lenny Bruce
Re: lyx file format changes
On 06-Aug-2001 Lars Gullik Bjønnes wrote: > That will continue to happen until we have a format that makes sense. > (note that for this change it is possible to make 1.2.x read the new > format with just a couple of small tweeks: > - ignore the begin_doc_parameters and end_doc_parameters > - user begin_paragraph just as \layout, ignore end_paragraph > - ignore begin_par_parameters and end_par_parameters > but this will happen in a 1.2.x > 0 release. > ) You surely meant that this will happen for 1.3.0 as I really don't think that we should change format inside a "fix" release and x > 0 will be a fix release where ONLY bugfixes should come in! >| these are minor changes! why can't this be >| happend in 1.2.0? > > We have so many compability hacks in the code that this is very > difficult (and a lot of work.) We have already too much changes! We have to stop now and to fix ONLY bugs or we nerver will see 1.2.0 (well not in this millenium ;) >| it's not important for the user to get 1.2.0 >| as soon as possible! > > Perhaps not, but it is beggining to be important for us (developers) > to get 1.2.0 out. IMO it is for both! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ You know what they say -- the sweetest word in the English language is revenge. -- Peter Beard
Re: Paragraph iterators
On 06-Aug-2001 Lars Gullik Bjønnes wrote: >| I figured this would keep you busy for a while ;-) #:O) > I will probably do the rows in lyxtext first... seems a bit easier... I really hope you plan this not for 1.2.0, but no you wouldn't! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Yow! I'm imagining a surfer van filled with soy sauce!
Re: math - latest cvs
> Seems that your sources are foobar, I do not see that here. I think he has a version with the commented-out 'math_charinset.[Ch]' in Makefile.am Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: math - latest cvs
Please try again after an 'cvs update'. Andre' -- André Pönitz . [EMAIL PROTECTED]
math - latest cvs
what happens?
/bin/sh ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
-I../../src -I./../ -I../.. -I../.. -I../../boost -isystem
/usr/X11R6/include -g -O -fno-exceptions -W -Wall -c array.C
g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../.. -I../..
-I../../boost -isystem /usr/X11R6/include -g -O -fno-exceptions -W -Wall
-Wp,-MD,.deps/array.pp -c array.C
array.C: In method `void MathArray::insert(int, unsigned char,
MathTextCodes)':
array.C:148: parse error before `('
array.C:148: parse error before `)'
make[3]: *** [array.lo] Error 1
Herbert
--
http://www.educat.hu-berlin.de/~voss/lyx/
Re: table and platform problem
On 08-Jun-2001 Jean-Marc Lasgouttes wrote: > There have been a fix for that in 1.2.0cvs. I asked Juergen to > propagate it to 1.1.6 too. Isn't this done yet? IMO I did this already! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ It is impossible to enjoy idling thoroughly unless one has plenty of work to do. -- Jerome Klapka Jerome
Re: Let's try again to change the matrix dialog without being flamed (c:
John Levon wrote: [snip] > for the qt frontend, there is a little tabular box which grows/shrinks as you > change the values. I don't know how word does it. I have made a screenshot of it > > > (and are not aligned properly). > > That's true, that was just a quick hack > > fix this and it will be ok by me ... > > > > Can you try and do something about the clutter perhaps ? > > > I think we should have the buttons on the bottom, not along the side one > > I thought the same thing about the buttons (although a lot of windows > > dialog assistant propose three sides buttons), but the remainders of > > side buttons are really really dumb ... So let's choose the first solution perharp's > > previous discussion was that dialog size should remain the same. > > I don't have a problem with a larger dialog as long as its not /too/ large > > I mean look at citation ;) Is the one in attachment correct -- Cordialement Emmanuel |\ _,,,---,,_ Emmanuel GUREGHIAN ZZZzz /,`.-'`'-. ;-;;,_ mailto:[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) Je choisis mes amis pour leur bonne mine, mes connaissances pour leur bon caractère et mes ennemis pour le bon usage qu'ils font de leur intellect.Oscar Wilde <> Magic: 13000 Internal Form Definition File (do not change) Number of forms: 1 Unit of measure: FL_COORD_PIXEL SnapGrid: 2 === FORM === Name: form_maths_matrix Width: 295 Height: 183 Number of Objects: 8 class: FL_BOX type: UP_BOX box: 0 0 295 183 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_DEFAULT_SIZE lcol: FL_BLACK label: shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: callback: argument: class: FL_VALSLIDER type: VERT_NICE_SLIDER box: 10 30 32 140 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Rows shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_rows callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_VALSLIDER type: HOR_NICE_SLIDER box: 54 28 214 30 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Columns shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_columns callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_CHOICE type: NORMAL_CHOICE box: 56 86 90 30 boxtype: FL_FRAME_BOX colors: FL_COL1 FL_BLACK alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Vertical align|#V shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: choice_valign callback: C_FormBaseDeprecatedInputCB argument: 0 class: FL_INPUT type: NORMAL_INPUT box: 174 86 90 30 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_MCOL alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Horizontal align|#H shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: input_halign callback: C_FormBaseDeprecatedInputCB argument: 0 class: FL_BUTTON type: RETURN_BUTTON box: 44 140 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: OK shortcut: ^M resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_ok callback: C_FormBaseDeprecatedOKCB argument: 0 class: FL_BUTTON type: NORMAL_BUTTON box: 126 140 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Apply|#A shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_apply callback: C_FormBaseDeprecatedApplyCB argument: 0 class: FL_BUTTON type: NORMAL_BUTTON box: 208 140 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Cancel|^[ shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_cancel callback: C_FormBaseDeprecatedCancelCB argument: 0 == create_the_forms
math thingies
Could anybody please help me figuring out what the different beasts in math are? Currently there is a hierarchy that looks like: Inset (abstract base) /| \ Dim Char MacroArg (thing that need (for things formerly the width_/ascent_ known as characters) /descent_ cache) / \ Nest Dots Func Space Symbol (for thing with nested content) | \ GridDecoration Delim Frac Macro Root Script Sqrt / \ Array "Matrix" (base for eqnarray/align/...) The current "Symbol" inset is probably a bit to big, it contains things like \int, \sum (i.e. things that grow in displayed environments and can take limits) greek characters (that can't take limits) \sup, \inf (thing that don't grow, aren't exactly symbols, but take limits) and probabably a few more (some seemingly inserting extra space around themselves, when drawn, like '+' and '-') So the question is: What groups of "symbols" exist for LaTeX? What "characteristics" do they have? Andre' -- André Pönitz . [EMAIL PROTECTED]
