RE: Table inset bugs
On 16-Sep-2000 Dekel Tsur wrote: I've created a list of bugs/problems with the new table inset. This should keep Juergen busy for a while (I suppose I should help with items 19 and 20). Ok now some final words to this "missing features" report #:O) all points I'll let out have been fixed in current cvs to the problematic ones I'll comment [and snip most of the original post have a look at that if you want to see in detail what Dekel found out]: 1. The most annoying problem is that the cursor can be placed outside of a cell's text inset, and when the cursor is there, you cannot [snip] Ok this should be fixed now in some way! now you can start typing also when the cursor is outside the textinset and the text is added at the begin of the text inset or at the end of it (have to do this today) depending if the cursor is before or behind in the cell! 2. When you have a table with many rows (whose height is bigger then the height of the screen), and you scroll through the document with either down or pagedown, the view will jump from the top of the table to the bottom of the table, without showing the middle. This is still unresolved I'll need some help with this one! 4. The speed of editing of text in a table is slow. Especially when having fixed width columns, or a table inside a table. I'll guess we first make the inset stable then we look another time where we can make it faster (low priority and also hard to do!) 5. LyX crashed when doing line-delete-forward inside a table cell. There are surely other not supported functions but we'll find them out and implement them in time. IMO that the tabular inset as it is now is already MUCH more usefull than the old one so it shouldn't be a big problem if you still cannot do all what you can do in normal text! 9. When marking several cells and pressing C-c (copy), the text is not copied to the X-clipboard. Has to be done. The question is how we should copy the text into the clipboard? As tab/newline separated text? We could also put an option in the tabular-layout to copy the tabular into the clipboard as TeX or/and Troff #:O) 10. When exporting as ASCII, the tables are missing. TODO! I would like to implement both forms a simple Ascii output (one cell in one row NO multiline cell output) and using groff to process the tables (is it possible to get ascii output from a LaTeX file, asciilatex ???) 11. when having a fixed width column, the separation between paragraphs is indent, where it should be skip. I'll have to look into this the text inset has to know it is inside a tabular, but I guess this is not so important for now! TODO! 19. When inserting a table in a paragraph with a language different then the document language, when you type text in some cell it will be in the document language (or actually, "default" language :( ), and not in the language of the paragraph. I guess this is easy, I have the buffer from that the text and the actual postition in the text, the paragraph embeding the inset and the actual language on the position the inset is embeded, hmmm, should be too hard to create all the insets with this langugage, should it? I'll have a look today! 20. RTL doesn't work properly. This is defenitively your domain! Now that I (hopefully) solved most of the reported stuff could somebody hit me with another report, so that we can make this more and more stable! I've the feeling that we don't miss too much 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 -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ May you have many handsome and obedient sons.
Re: Table inset bugs
Now that I (hopefully) solved most of the reported stuff could somebody hit me with another report, so that we can make this more and more stable! I've the feeling that we don't miss too much now! Not so much as a bug report as a feature request that somebody? made and I wouldn't want you to forget ;-) Would it be possible to mark text by column? Angus
Re: Table inset bugs
Would it be possible to mark text by column? This IS already possible. Do you have problems with this? 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 -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ While it may be true that a watched pot never boils, the one you don't keep an eye on can make an awful mess of your stove. -- Edward Stevenson
Re: Table inset bugs
On Tue, 03 Oct 2000, Juergen Vigna wrote: Would it be possible to mark text by column? This IS already possible. Do you have problems with this? Oh good! My only problem has been lyx segfaulting on start up. Resolved as of today. Will have a play. Thanks, Angus
Re: Table inset bugs
9. When marking several cells and pressing C-c (copy), the text is not copied to the X-clipboard. Has to be done. The question is how we should copy the text into the clipboard? As tab/newline separated text? From a user's point I'd say it should be inserted in a way that the result is useful when pasting to tables again. Andre' -- Andre' Poenitz [EMAIL PROTECTED]
Re: Table inset bugs
On 03-Oct-2000 Andre Poenitz wrote: 9. When marking several cells and pressing C-c (copy), the text is not copied to the X-clipboard. Has to be done. The question is how we should copy the text into the clipboard? As tab/newline separated text? From a user's point I'd say it should be inserted in a way that the result is useful when pasting to tables again. Well would you say this comment is helpfull? I know that it should be useful for a user! * hicks * (just drunk some Sparkling wine with friends on my marriage last friday ;) 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 -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ O'Reilly's Law of the Kitchen: Cleanliness is next to impossible
Re: Table inset bugs
From a user's point I'd say it should be inserted in a way that the result is useful when pasting to tables again. ^ Well would you say this comment is helpfull? Yes. The 'whatever-separated' solution could mean, that you could paste it to an external editor or speadsheet (which would be fine), but not to a LyX table with other dimensions. I'd prefer to be able to cut parts of a table and paste it to another table (with possibly other dimensions) within LyX. I know that it should be useful for a user! Well, I tried to communicate what kind of 'usefulness' I have in mind ;-) Andre' -- Andre' Poenitz [EMAIL PROTECTED]
Re: Table inset bugs
On 03-Oct-2000 Andre Poenitz wrote: From a user's point I'd say it should be inserted in a way that the result is useful when pasting to tables again. ^ Well would you say this comment is helpfull? Yes. The 'whatever-separated' solution could mean, that you could paste it to an external editor or speadsheet (which would be fine), but not to a LyX table with other dimensions. I'd prefer to be able to cut parts of a table and paste it to another table (with possibly other dimensions) within LyX. You already can copy/cut/paste different parts of a tabular inside another tabular (with the copy/cut/paste functions), this one is just to copy the tabular outside LyX to a text-editor or somewhere else (we don't use the XClipboard for internal copy/paste stuff as we loose all font information and a lot more!) So the question was refered ONLY to pastes OUTSIDE LyX! 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 have been in Afghanistan, I perceive." -- Sir Arthur Conan Doyle, "A Study in Scarlet"
Re: Table inset bugs
On Tue, 3 Oct 2000, Andre Poenitz wrote: 9. When marking several cells and pressing C-c (copy), the text is not copied to the X-clipboard. Has to be done. The question is how we should copy the text into the clipboard? As tab/newline separated text? From a user's point I'd say it should be inserted in a way that the result is useful when pasting to tables again. Better yet we should support XDND and offer a choice of ascii, LaTeX, HTML and DocBook tables for export. Likewise for the rest of LyX exports. Allan. (ARRae)
RE: Table inset bugs
On 16-Sep-2000 Dekel Tsur wrote: > I've created a list of bugs/problems with the new table inset. > This should keep Juergen busy for a while (I suppose I should help with > items 19 and 20). > Ok now some final words to this "missing features" report #:O) all points I'll let out have been fixed in current cvs to the problematic ones I'll comment [and snip most of the original post have a look at that if you want to see in detail what Dekel found out]: > 1. The most annoying problem is that the cursor can be placed outside > of a cell's text inset, and when the cursor is there, you cannot [snip] Ok this should be fixed now in some way! now you can start typing also when the cursor is outside the textinset and the text is added at the begin of the text inset or at the end of it (have to do this today) depending if the cursor is before or behind in the cell! > 2. When you have a table with many rows (whose height is bigger then the > height of the screen), and you scroll through the document with either > down or pagedown, the view will jump from the top of the table to > the bottom of the table, without showing the middle. > This is still unresolved I'll need some help with this one! > 4. The speed of editing of text in a table is slow. Especially when having > fixed width columns, or a table inside a table. > I'll guess we first make the inset stable then we look another time where we can make it faster (low priority and also hard to do!) > 5. LyX crashed when doing line-delete-forward inside a table cell. There are surely other not supported functions but we'll find them out and implement them in time. IMO that the tabular inset as it is now is already MUCH more usefull than the old one so it shouldn't be a big problem if you still cannot do all what you can do in normal text! > 9. When marking several cells and pressing C-c (copy), the text is not > copied to the X-clipboard. > Has to be done. The question is how we should copy the text into the clipboard? As tab/newline separated text? We could also put an option in the tabular-layout to copy the tabular into the clipboard as TeX or/and Troff #:O) > 10. When exporting as ASCII, the tables are missing. > TODO! I would like to implement both forms a simple Ascii output (one cell in one row NO multiline cell output) and using groff to process the tables (is it possible to get ascii output from a LaTeX file, asciilatex ???) > 11. when having a fixed width column, the separation between paragraphs is > indent, where it should be skip. > I'll have to look into this the text inset has to know it is inside a tabular, but I guess this is not so important for now! TODO! > 19. When inserting a table in a paragraph with a language different then the > document language, when you type text in some cell it will be in the document > language (or actually, "default" language :( ), and not in the language of the > paragraph. > I guess this is easy, I have the buffer from that the text and the actual postition in the text, the paragraph embeding the inset and the actual language on the position the inset is embeded, hmmm, should be too hard to create all the insets with this langugage, should it? I'll have a look today! > 20. RTL doesn't work properly. This is defenitively your domain! Now that I (hopefully) solved most of the reported stuff could somebody hit me with another report, so that we can make this more and more stable! I've the feeling that we don't miss too much 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 -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ May you have many handsome and obedient sons.
Re: Table inset bugs
> Now that I (hopefully) solved most of the reported stuff could somebody > hit me with another report, so that we can make this more and more stable! > I've the feeling that we don't miss too much now! Not so much as a bug report as a feature request that somebody? made and I wouldn't want you to forget ;-) Would it be possible to mark text by column? Angus
Re: Table inset bugs
> > Would it be possible to mark text by column? This IS already possible. Do you have problems with this? 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 -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ While it may be true that a watched pot never boils, the one you don't keep an eye on can make an awful mess of your stove. -- Edward Stevenson
Re: Table inset bugs
On Tue, 03 Oct 2000, Juergen Vigna wrote: > > Would it be possible to mark text by column? > > This IS already possible. Do you have problems with this? Oh good! My only problem has been lyx segfaulting on start up. Resolved as of today. Will have a play. Thanks, Angus
Re: Table inset bugs
> > 9. When marking several cells and pressing C-c (copy), the text is not > > copied to the X-clipboard. > > Has to be done. The question is how we should copy the text into the > clipboard? As tab/newline separated text? >From a user's point I'd say it should be inserted in a way that the result is useful when pasting to tables again. Andre' -- Andre' Poenitz [EMAIL PROTECTED]
Re: Table inset bugs
On 03-Oct-2000 Andre Poenitz wrote: >> > 9. When marking several cells and pressing C-c (copy), the text is not >> > copied to the X-clipboard. >> >> Has to be done. The question is how we should copy the text into the >> clipboard? As tab/newline separated text? > > From a user's point I'd say it should be inserted in a way that the result > is useful when pasting to tables again. Well would you say this comment is helpfull? I know that it should be useful for a user! * hicks * (just drunk some Sparkling wine with friends on my marriage last friday ;) 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 -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ O'Reilly's Law of the Kitchen: Cleanliness is next to impossible
Re: Table inset bugs
> > From a user's point I'd say it should be inserted in a way that the result > > is useful when pasting to tables again. ^ > Well would you say this comment is helpfull? Yes. The 'whatever-separated' solution could mean, that you could paste it to an external editor or speadsheet (which would be fine), but not to a LyX table with other dimensions. I'd prefer to be able to cut parts of a table and paste it to another table (with possibly other dimensions) within LyX. > I know that it should be useful for a user! Well, I tried to communicate what kind of 'usefulness' I have in mind ;-) Andre' -- Andre' Poenitz [EMAIL PROTECTED]
Re: Table inset bugs
On 03-Oct-2000 Andre Poenitz wrote: >> > From a user's point I'd say it should be inserted in a way that the result >> > is useful when pasting to tables again. >^ > >> Well would you say this comment is helpfull? > > Yes. The 'whatever-separated' solution could mean, that you could paste it > to an external editor or speadsheet (which would be fine), but not to > a LyX table with other dimensions. > > I'd prefer to be able to cut parts of a table and paste it to another table > (with possibly other dimensions) within LyX. > You already can copy/cut/paste different parts of a tabular inside another tabular (with the copy/cut/paste functions), this one is just to copy the tabular outside LyX to a text-editor or somewhere else (we don't use the XClipboard for internal copy/paste stuff as we loose all font information and a lot more!) So the question was refered ONLY to pastes OUTSIDE LyX! 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 have been in Afghanistan, I perceive." -- Sir Arthur Conan Doyle, "A Study in Scarlet"
Re: Table inset bugs
On Tue, 3 Oct 2000, Andre Poenitz wrote: > > > 9. When marking several cells and pressing C-c (copy), the text is not > > > copied to the X-clipboard. > > > > Has to be done. The question is how we should copy the text into the > > clipboard? As tab/newline separated text? > > >From a user's point I'd say it should be inserted in a way that the result > is useful when pasting to tables again. Better yet we should support XDND and offer a choice of ascii, LaTeX, HTML and DocBook tables for export. Likewise for the rest of LyX exports. Allan. (ARRae)
Table inset bugs
I've created a list of bugs/problems with the new table inset. This should keep Juergen busy for a while (I suppose I should help with items 19 and 20). 1. The most annoying problem is that the cursor can be placed outside of a cell's text inset, and when the cursor is there, you cannot enter text (I'll call these positions dummy cursor positions, and I'll call the positions inside the text inset real positions). I believe the purpose of the dummy positions is to allow selecting of cells in the table, but they are annoying when you try to enter text in the table. Here are two ways to solve this problem (the first one seems better) - Completely remove the dummy cursor positions. When you press the mouse button on some cell and move it to create a selection, LyX will select the appropriate region in the text inset. When the mouse exit the cell in which the selection started, the text inset in that cell "gives control" to the table inset and LyX begins doing a cell selection. This mechanism is used in the math inset, when doing keyboard selection (but no mouse selection): goto the first position in math inset, and begin pressing S+right. After all the text in inset is selected, the selection changes from math selection to "global" selection. - When you enter a table with the mouse/keyboard, you always go to a real position. Moving the cursor with tab/up/down/left/right will always move the cursor to a real position. To get into a dummy position you need to press a special key (e.g escape). 2. When you have a table with many rows (whose height is bigger then the height of the screen), and you scroll through the document with either down or pagedown, the view will jump from the top of the table to the bottom of the table, without showing the middle. 3. Memory consumption: With old table code, a 50x50 empty table takes ~140kb of memory or ~57 bytes per cell. With the new code, such a table takes ~4936kb or ~2022 bytes per cell. 4. The speed of editing of text in a table is slow. Especially when having fixed width columns, or a table inside a table. 5. LyX crashed when doing line-delete-forward inside a table cell. 6. When copying table cells, it is not possible to paste them into another table. 7. Suppose I have the table 1 2 3 4 5 6 7 8 9 and I mark the upper left 2x2 subtable. After pressing C-x (cut), I get - - - - 5 6 7 8 9 8. It is not possible to paste a text from the X-clipboard into a cell's text inset. 9. When marking several cells and pressing C-c (copy), the text is not copied to the X-clipboard. 10. When exporting as ASCII, the tables are missing. 11. when having a fixed width column, the separation between paragraphs is indent, where it should be skip. 12. It is possible to select a layout (e.g. enumerate) or change paragraph parameters (e.g. pagebreaks) for a "paragraph" of a cell in a non-fixed column, which is senseless. Furthermore, for a paragraph in a cell in a fixed width column, you can select a pagebreak below/above the paragraph, which is senseless. 13. A lot of redundant data is written when saving a table in a LyX file. For example a 1x1 table is stored as: \begin_inset Tabular LyXTabular version=1 rows=1 columns=1 Features rotate=0 islongtable=0 endhead=0 endfirsthead=0 endfoot=0 ... Row topline=1 bottomline=1 newpage=0 Column alignment=8 valignment=0 leftline=1 rightline=1 width="" special="" Cell multicolumn=0 alignment=8 valignment=0 topline=0 bottomline=0 ... \begin_inset Text \layout Standard Some text \end_inset /Cell /Column /Row /LyXTabular \end_inset All table/row values are the default ones (e.g., rotate = 0), so there is no need to store them. The "\layout Standard" is redundant, as the column is has non-fixed width, so layout information is senseless. The "\begin_inset Text" is also redundant. 14. Check the attached file (bug.lyx) - Pressing the mouse on one of the "f"s, and then pressing the mouse on the "x" will cause a crash. - Putting the cursor on the "f"s and pressing backspace wil cause a display problem. 15. The red insettext's frame flickers when typing (while the text of the table doesn't). 16. After insertion of table the cursor is sometimes misplaced (esp. if you insert a table inside a table). 17. If the file contain only a table, when you press left when the cursor is to the left of the table, the cursor will go into the table. 18. Suppose I have a table with a fixed width column, and a cell in that column contains two paragraphs: A and B, both with standard layout. I then change the layout of A to enumerate. Now, if I try to change the layout of B to enumerate, nothing happens. 19. When inserting a table in a paragraph with a language different then the document language, when you type text in some cell it will be in the document language (or actually, "default" language :( ), and not in the language of the paragraph. 20. RTL doesn't work properly. bug.lyx.gz
Table inset bugs
I've created a list of bugs/problems with the new table inset. This should keep Juergen busy for a while (I suppose I should help with items 19 and 20). 1. The most annoying problem is that the cursor can be placed outside of a cell's text inset, and when the cursor is there, you cannot enter text (I'll call these positions dummy cursor positions, and I'll call the positions inside the text inset real positions). I believe the purpose of the dummy positions is to allow selecting of cells in the table, but they are annoying when you try to enter text in the table. Here are two ways to solve this problem (the first one seems better) - Completely remove the dummy cursor positions. When you press the mouse button on some cell and move it to create a selection, LyX will select the appropriate region in the text inset. When the mouse exit the cell in which the selection started, the text inset in that cell "gives control" to the table inset and LyX begins doing a cell selection. This mechanism is used in the math inset, when doing keyboard selection (but no mouse selection): goto the first position in math inset, and begin pressing S+right. After all the text in inset is selected, the selection changes from math selection to "global" selection. - When you enter a table with the mouse/keyboard, you always go to a real position. Moving the cursor with tab/up/down/left/right will always move the cursor to a real position. To get into a dummy position you need to press a special key (e.g escape). 2. When you have a table with many rows (whose height is bigger then the height of the screen), and you scroll through the document with either down or pagedown, the view will jump from the top of the table to the bottom of the table, without showing the middle. 3. Memory consumption: With old table code, a 50x50 empty table takes ~140kb of memory or ~57 bytes per cell. With the new code, such a table takes ~4936kb or ~2022 bytes per cell. 4. The speed of editing of text in a table is slow. Especially when having fixed width columns, or a table inside a table. 5. LyX crashed when doing line-delete-forward inside a table cell. 6. When copying table cells, it is not possible to paste them into another table. 7. Suppose I have the table 1 2 3 4 5 6 7 8 9 and I mark the upper left 2x2 subtable. After pressing C-x (cut), I get - - - - 5 6 7 8 9 8. It is not possible to paste a text from the X-clipboard into a cell's text inset. 9. When marking several cells and pressing C-c (copy), the text is not copied to the X-clipboard. 10. When exporting as ASCII, the tables are missing. 11. when having a fixed width column, the separation between paragraphs is indent, where it should be skip. 12. It is possible to select a layout (e.g. enumerate) or change paragraph parameters (e.g. pagebreaks) for a "paragraph" of a cell in a non-fixed column, which is senseless. Furthermore, for a paragraph in a cell in a fixed width column, you can select a pagebreak below/above the paragraph, which is senseless. 13. A lot of redundant data is written when saving a table in a LyX file. For example a 1x1 table is stored as: \begin_inset Tabular \begin_inset Text \layout Standard Some text \end_inset \end_inset All table/row values are the default ones (e.g., rotate = 0), so there is no need to store them. The "\layout Standard" is redundant, as the column is has non-fixed width, so layout information is senseless. The "\begin_inset Text" is also redundant. 14. Check the attached file (bug.lyx) - Pressing the mouse on one of the "f"s, and then pressing the mouse on the "x" will cause a crash. - Putting the cursor on the "f"s and pressing backspace wil cause a display problem. 15. The red insettext's frame flickers when typing (while the text of the table doesn't). 16. After insertion of table the cursor is sometimes misplaced (esp. if you insert a table inside a table). 17. If the file contain only a table, when you press left when the cursor is to the left of the table, the cursor will go into the table. 18. Suppose I have a table with a fixed width column, and a cell in that column contains two paragraphs: A and B, both with standard layout. I then change the layout of A to enumerate. Now, if I try to change the layout of B to enumerate, nothing happens. 19. When inserting a table in a paragraph with a language different then the document language, when you type text in some cell it will be in the document language (or actually, "default" language :( ), and not in the language of the paragraph. 20. RTL doesn't work properly. bug.lyx.gz
