Now some detail words for this bug-report and a status quo:
On 17-Aug-2000 Bernd Paysan wrote:
I'm using latext CVS (i.e. the bug report is related to insettabular.C
rev. 1.44, Aug 11). I'll give a more detailed bug report in the following
lines:
The first table I inserted didn't redraw
Now some detail words for this bug-report and a status quo:
On 17-Aug-2000 Bernd Paysan wrote:
>
> I'm using latext CVS (i.e. the bug report is related to insettabular.C
> rev. 1.44, Aug 11). I'll give a more detailed bug report in the following
> lines:
>
> The first table I inserted didn't
On 17-Aug-2000 Bernd Paysan wrote:
I'm using latext CVS (i.e. the bug report is related to insettabular.C
rev. 1.44, Aug 11). I'll give a more detailed bug report in the following
lines:
For now thanks for the report I will replay to the single points when
I find the time to have a look,
On 17-Aug-2000 Bernd Paysan wrote:
> I'm using latext CVS (i.e. the bug report is related to insettabular.C
> rev. 1.44, Aug 11). I'll give a more detailed bug report in the following
> lines:
>
For now thanks for the report I will replay to the single points when
I find the time to have a
On Wed, 16 Aug 2000, Juergen Vigna wrote:
With which version are you working? I'll see my work there terminated util
I get some bugreports. So please could you give me more informations on the
crashes and on the update-problems (ONLY if you are using the latest CVS).
I'm using latext CVS
On Wed, 16 Aug 2000, Juergen Vigna wrote:
> With which version are you working? I'll see my work there terminated util
> I get some bugreports. So please could you give me more informations on the
> crashes and on the update-problems (ONLY if you are using the latest CVS).
I'm using latext CVS
On 14-Aug-2000 Bernd Paysan wrote:
No, I ignorantly just clicked on the "table" icon ;-). I now tried that
(enter the command in the bottom line), and it worked! Yeah! That's
exactly how I want a table inset to look like (ok, minus the crashes that
happen when your randomly click into the
On 14-Aug-2000 Bernd Paysan wrote:
>
> No, I ignorantly just clicked on the "table" icon ;-). I now tried that
> (enter the command in the bottom line), and it worked! Yeah! That's
> exactly how I want a table inset to look like (ok, minus the crashes that
> happen when your randomly click into
On 13-Aug-2000 Bernd Paysan wrote:
On Mon, 7 Aug 2000, Juergen Vigna wrote:
You should try the inset-tabular in the new 1.1.6cvs and you'll see that
this has been all removed. Now a parbox is inserted automatically if you
use linebreaks (because of the above mentioned problem), but there
On Mon, 14 Aug 2000, Juergen Vigna wrote:
I don't understand??? How do you insert a insettabular in your document?
Do you use Meta-x tabular-insert?
No, I ignorantly just clicked on the "table" icon ;-). I now tried that
(enter the command in the bottom line), and it worked! Yeah! That's
On 13-Aug-2000 Bernd Paysan wrote:
> On Mon, 7 Aug 2000, Juergen Vigna wrote:
>
>> You should try the inset-tabular in the new 1.1.6cvs and you'll see that
>> this has been all removed. Now a parbox is inserted automatically if you
>> use linebreaks (because of the above mentioned problem), but
On Mon, 14 Aug 2000, Juergen Vigna wrote:
> I don't understand??? How do you insert a insettabular in your document?
> Do you use Meta-x tabular-insert?
No, I ignorantly just clicked on the "table" icon ;-). I now tried that
(enter the command in the bottom line), and it worked! Yeah! That's
On Mon, 7 Aug 2000, Juergen Vigna wrote:
You should try the inset-tabular in the new 1.1.6cvs and you'll see that
this has been all removed. Now a parbox is inserted automatically if you
use linebreaks (because of the above mentioned problem), but there is no
\smallskip{} as you can now
On Mon, 7 Aug 2000, Juergen Vigna wrote:
> You should try the inset-tabular in the new 1.1.6cvs and you'll see that
> this has been all removed. Now a parbox is inserted automatically if you
> use linebreaks (because of the above mentioned problem), but there is no
> \smallskip{} as you can now
Generally, good LaTeX style is to put out \\ for line-ends, table-ends or
whatever ends you have in the current context (\\ is just a token assigned
by \let). \newline is for the special case you want to have a text line end
inside a table.
Well then I can at least let the parbox as for
>
> Generally, good LaTeX style is to put out \\ for line-ends, table-ends or
> whatever ends you have in the current context (\\ is just a token assigned
> by \let). \newline is for the special case you want to have a text line end
> inside a table.
>
Well then I can at least let the parbox
Hello Bernd!
There's always \newline (a robust command that expands to the \@normalcr
linebreak command). This is valid LaTeX code without a parbox or
minipage, and it does have two lines in a cell:
Ok you got me here, so can you tell me what's the difference between
outputing \\ and
Juergen Vigna [EMAIL PROTECTED] writes:
| Hello Bernd!
|
|
| There's always \newline (a robust command that expands to the \@normalcr
| linebreak command). This is valid LaTeX code without a parbox or
| minipage, and it does have two lines in a cell:
|
|
| Ok you got me here, so can you
You did look at the example right?
\begin{tabular}[p{5cm}|c]
cell one line one \newline
cell one line two cell two \\
cell three cell four
\end{tabular}
I did look ;), you see the \newline? Well if I do Ctrl-Return in LyX
LyXParagraph can output or \newline or \\ well it does the
Juergen Vigna [EMAIL PROTECTED] writes:
| You did look at the example right?
|
| \begin{tabular}[p{5cm}|c]
| cell one line one \newline
| cell one line two cell two \\
| cell three cell four
| \end{tabular}
|
|
| I did look ;), you see the \newline? Well if I do Ctrl-Return in LyX
|
So you are not speaking of tabulars anymore? But about plain
paragraphs?
Well you know that a multirow-tabular-cell (cell with width) now IS
actually a multiparagraph text inset and I actually use LyXParagraph
to output it's contents!
What is the difference on the TeX level? \\ has some
Hello Bernd!
>
> There's always \newline (a robust command that expands to the \@normalcr
> linebreak command). This is valid LaTeX code without a parbox or
> minipage, and it does have two lines in a cell:
>
Ok you got me here, so can you tell me what's the difference between
outputing \\
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Hello Bernd!
|
| >
| > There's always \newline (a robust command that expands to the \@normalcr
| > linebreak command). This is valid LaTeX code without a parbox or
| > minipage, and it does have two lines in a cell:
| >
|
| Ok you got me here, so
> You did look at the example right?
>
> \begin{tabular}[p{5cm}|c]
> cell one line one \newline
> cell one line two & cell two \\
> cell three & cell four
> \end{tabular}
>
I did look ;), you see the \newline? Well if I do Ctrl-Return in LyX
LyXParagraph can output or \newline or \\ well it
Juergen Vigna <[EMAIL PROTECTED]> writes:
| > You did look at the example right?
| >
| > \begin{tabular}[p{5cm}|c]
| > cell one line one \newline
| > cell one line two & cell two \\
| > cell three & cell four
| > \end{tabular}
| >
|
| I did look ;), you see the \newline? Well if I do
>
> So you are not speaking of tabulars anymore? But about plain
> paragraphs?
>
Well you know that a multirow-tabular-cell (cell with width) now IS
actually a multiparagraph text inset and I actually use LyXParagraph
to output it's contents!
> What is the difference on the TeX level? \\ has
Juergen Vigna wrote:
Well I don't know :), I know for sure that inside tabulars they are not
allowed because \\ is a special case for tabulars (end of this row).
There's always \newline (a robust command that expands to the \@normalcr
linebreak command). This is valid LaTeX code without a
Juergen Vigna wrote:
> Well I don't know :), I know for sure that inside tabulars they are not
> allowed because \\ is a special case for tabulars (end of this row).
There's always \newline (a robust command that expands to the \@normalcr
linebreak command). This is valid LaTeX code without a
| then output the text inside a minipage! This only means that I will have a
| "Use parbox" button too ;)
Why?
Because you cannot force newlines (\\) if you don't have a parbox or minipage
and this IS needed and always was there it was just called linebreaks. I also
have to find a way how to
Juergen Vigna [EMAIL PROTECTED] writes:
| Answering to your question, if the above problem is none (means that we don't
| permit linebreaks which are not real linebreaks) then the use of parbox can
| be automatically choosen.
I _think_ that would be sufficient.
Lgb
Jürgen Answering to your question, if the above problem is none (means that we don't
Jürgen permit linebreaks which are not real linebreaks) then the use of parbox can
Jürgen be automatically choosen.
For what it's worth, I think that this option should be thrown out. It's
counter-intuitive and
On 01-Aug-2000 Angus Leeming wrote:
Jürgen Answering to your question, if the above problem is none (means that we don't
Jürgen permit linebreaks which are not real linebreaks) then the use of parbox can
Jürgen be automatically choosen.
For what it's worth, I think that this option should
On 01-Aug-2000 Lars Gullik Bjønnes wrote:
I _think_ that would be sufficient.
Ok so I will remove the parbox button from the layout and calculate
automatically if I need one (based on if the insettext has newlines).
Jürgen
--
"Andre" == Andre Poenitz [EMAIL PROTECTED] writes:
Andre Juergen wrote:
Well I guess we should have a horizontal scrollbar (and I'll have a
look how to implement this). But we will have it on the main lyx
window or where would you put it inside the inset? Think of a
tabular which is at
Jürgen Answering to your question, if the above problem is none (means that we
don't
Jürgen permit linebreaks which are not real linebreaks) then the use of parbox can
Jürgen be automatically choosen.
For what it's worth, I think that this option should be thrown out. It's
On 01-Aug-2000 Jean-Marc Lasgouttes wrote:
Or an horizontal scrollbar that (1) only appears when needed and (2)
appears at the bottom of the screen if the inset is taller than the
screen. Is it possible? Does it make sense from an UI point of view?
I was thinking to disable the scrollbar
"Juergen" == Juergen Vigna [EMAIL PROTECTED] writes:
Juergen No only the inset will scroll horizontally the rest of the
Juergen text will not be touched!
The simplest way for now would be to make it move with the cursor (no
scrollbar).
JMarc
>| then output the text inside a minipage! This only means that I will have a
>| "Use parbox" button too ;)
>
> Why?
Because you cannot force newlines (\\) if you don't have a parbox or minipage
and this IS needed and always was there it was just called linebreaks. I also
have to find a way how
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Answering to your question, if the above problem is none (means that we don't
| permit linebreaks which are not real linebreaks) then the use of parbox can
| be automatically choosen.
I _think_ that would be sufficient.
Lgb
Jürgen> Answering to your question, if the above problem is none (means that we don't
Jürgen> permit linebreaks which are not real linebreaks) then the use of parbox can
Jürgen> be automatically choosen.
For what it's worth, I think that this option should be thrown out. It's
counter-intuitive
On 01-Aug-2000 Angus Leeming wrote:
> Jürgen> Answering to your question, if the above problem is none (means that we don't
> Jürgen> permit linebreaks which are not real linebreaks) then the use of parbox can
> Jürgen> be automatically choosen.
>
> For what it's worth, I think that this option
On 01-Aug-2000 Lars Gullik Bjønnes wrote:
>
> I _think_ that would be sufficient.
Ok so I will remove the parbox button from the layout and calculate
automatically if I need one (based on if the insettext has newlines).
Jürgen
--
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> Juergen wrote:
>> Well I guess we should have a horizontal scrollbar (and I'll have a
>> look how to implement this). But we will have it on the main lyx
>> window or where would you put it inside the inset? Think of a
>> tabular
> > Jürgen> Answering to your question, if the above problem is none (means that we
>don't
> > Jürgen> permit linebreaks which are not real linebreaks) then the use of parbox can
> > Jürgen> be automatically choosen.
> >
> > For what it's worth, I think that this option should be thrown out.
On 01-Aug-2000 Jean-Marc Lasgouttes wrote:
>
> Or an horizontal scrollbar that (1) only appears when needed and (2)
> appears at the bottom of the screen if the inset is taller than the
> screen. Is it possible? Does it make sense from an UI point of view?
>
I was thinking to disable the
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> No only the inset will scroll horizontally the rest of the
Juergen> text will not be touched!
The simplest way for now would be to make it move with the cursor (no
scrollbar).
JMarc
On 30-Jul-2000 Lars Gullik Bjønnes wrote:
|
| Well the you can center align multirow-text in a cell and the whole
| stuff is also easier to handle. I'm thinking of a "Use minipage" button
| instead of the Linebreaks button (as that one is obsolet as if we have
| a width we then always would use
Juergen Vigna [EMAIL PROTECTED] writes:
| On 30-Jul-2000 Lars Gullik Bjønnes wrote:
| |
| | Well the you can center align multirow-text in a cell and the whole
| | stuff is also easier to handle. I'm thinking of a "Use minipage" button
| | instead of the Linebreaks button (as that one is
On 30-Jul-2000 Lars Gullik Bjønnes wrote:
>|
>| Well the you can center align multirow-text in a cell and the whole
>| stuff is also easier to handle. I'm thinking of a "Use minipage" button
>| instead of the Linebreaks button (as that one is obsolet as if we have
>| a width we then always
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 30-Jul-2000 Lars Gullik Bjønnes wrote:
| >|
| >| Well the you can center align multirow-text in a cell and the whole
| >| stuff is also easier to handle. I'm thinking of a "Use minipage" button
| >| instead of the Linebreaks button (as that one is
Juergen Vigna [EMAIL PROTECTED] writes:
| Hello!
|
| I'm thinking of dropping the p{} column parameters from the production
| of tabulars and subsitute them always by parbox and/or minipage.
|
| Why?
|
| Well the you can center align multirow-text in a cell and the whole
| stuff is also
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Hello!
|
| I'm thinking of dropping the p{} column parameters from the production
| of tabulars and subsitute them always by parbox and/or minipage.
|
| Why?
|
| Well the you can center align multirow-text in a cell and the whole
| stuff is also
Hello!
I'm thinking of dropping the p{} column parameters from the production
of tabulars and subsitute them always by parbox and/or minipage.
Why?
Well the you can center align multirow-text in a cell and the whole
stuff is also easier to handle. I'm thinking of a "Use minipage" button
Hello!
I'm thinking of dropping the p{} column parameters from the production
of tabulars and subsitute them always by parbox and/or minipage.
Why?
Well the you can center align multirow-text in a cell and the whole
stuff is also easier to handle. I'm thinking of a "Use minipage" button
54 matches
Mail list logo
