On 25-Sep-2000 Marko Vendelin wrote:
A CSM should only be visible while the mouse button is held down. Once
the mouse is released the menu closes. If the mouse was over a menu entry
that menu entry's action takes place. If the mouse cursor was outside the
menu borders nothing happens.
On 25-Sep-2000 Marko Vendelin wrote:
>>
>> A CSM should only be visible while the mouse button is held down. Once
>> the mouse is released the menu closes. If the mouse was over a menu entry
>> that menu entry's action takes place. If the mouse cursor was outside the
>> menu borders nothing
I just jumped from first to last emails in this thread so I may have
missed a little bit ;-)
On Sat, 23 Sep 2000, Marko Vendelin wrote:
On Fri, 22 Sep 2000, Angus Leeming wrote:
5. We need some method of toggling between the three LaTeX output states. As
the left mouse button opens the
On Mon, 25 Sep 2000, Allan Rae wrote:
I just jumped from first to last emails in this thread so I may have
missed a little bit ;-)
On Sat, 23 Sep 2000, Marko Vendelin wrote:
On Fri, 22 Sep 2000, Angus Leeming wrote:
5. We need some method of toggling between the three LaTeX
On Fri, 22 Sep 2000, Angus Leeming wrote:
Thanks for all this input.
Here's some from me since I missed most of the discussion.
I'm going to try and summarise it all and so define what the new InsetNote
should do.
1. It should be a collapsable inset.
1a. It should be possible to
I just jumped from first to last emails in this thread so I may have
missed a little bit ;-)
On Sat, 23 Sep 2000, Marko Vendelin wrote:
> On Fri, 22 Sep 2000, Angus Leeming wrote:
>
> > 5. We need some method of toggling between the three LaTeX output states. As
> > the left mouse button
On Mon, 25 Sep 2000, Allan Rae wrote:
> I just jumped from first to last emails in this thread so I may have
> missed a little bit ;-)
>
> On Sat, 23 Sep 2000, Marko Vendelin wrote:
>
> > On Fri, 22 Sep 2000, Angus Leeming wrote:
> >
> > > 5. We need some method of toggling between the
On Fri, 22 Sep 2000, Angus Leeming wrote:
> Thanks for all this input.
Here's some from me since I missed most of the discussion.
> I'm going to try and summarise it all and so define what the new InsetNote
> should do.
>
> 1. It should be a collapsable inset.
1a. It should be possible to
On Fri, 22 Sep 2000, Angus Leeming wrote:
5. We need some method of toggling between the three LaTeX output states. As
the left mouse button opens the inset, this leaves the right mouse button.
Jürgen seems very against using this to toggle between states, so RMB will
launch a (very
On Fri, 22 Sep 2000, Angus Leeming wrote:
> 5. We need some method of toggling between the three LaTeX output states. As
> the left mouse button opens the inset, this leaves the right mouse button.
> Jürgen seems very against using this to toggle between states, so RMB will
> launch a (very
On Fri, 22 Sep 2000, Allan Rae wrote:
Info will become a collapsible inset and so it won't be needing a dialog
in future. It should be fairly easy to implement (give it a better name
at the same time like InsetProofread or something since it's meant for
sticking editting notes into and
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Then somone (!?!) would show me how to write comments to Latex
Angus that could subsequently be interpretted by reLyX and read back
Angus into LyX?
Angus By the way, what's wrong with the name? Your comment that "it's
Angus meant for
On Fri, Sep 22, 2000 at 11:28:35AM +0200, Jean-Marc Lasgouttes wrote:
As I see it, we need 3 related insets:
- one which outputs as % latex comments (InsetNote?). This one could
be restricted to text only, since we cannot expect reLyX to parse
everything after a % as valid latex.
- one
On 22-Sep-2000 Jean-Marc Lasgouttes wrote:
As I see it, we need 3 related insets:
- one which outputs as % latex comments (InsetNote?). This one could
be restricted to text only, since we cannot expect reLyX to parse
everything after a % as valid latex.
- one which outputs as a
On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote:
On Fri, Sep 22, 2000 at 10:44:34AM +0100, Angus Leeming wrote:
On the otherhand, José's suggestion of a checkbox is a cool one. Not that
I've any idea of how to implement it!
Like the url inset. There you have the option from it to
About the question of the 2 point, Lars said there is something like
a comment environment in LaTeX, but he has to explain how it works ;)
If you write
\begin{comment}
some text
\end{comment}
in LaTeX, 'some text' won't be typeset.
Is that what you mean?
Andre'
--
Andre' Poenitz
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Yes. Could you explain what you mean by the second case,
Angus Jean-Marc. I don't really see the difference between cases 1
Angus and 3. Why not output to LaTeX always. It's only a note and
Angus will not be present in the final printed
"Juergen" == Juergen Vigna [EMAIL PROTECTED] writes:
Juergen About the question of the 2 point, Lars said there is
Juergen something like a comment environment in LaTeX, but he has to
Juergen explain how it works ;)
verbatim.sty provides it. However this is quite a big machniery from a
LaTeX
Thanks for all this input.
I'm going to try and summarise it all and so define what the new InsetNote
should do.
1. It should be a collapsable inset.
2. It should output nothing to Ascii, Linuxdoc or DocBook. Don't argue here.
We can always change later!
3. People have suggested a
Ok, I've made the basic inset. It's a rather boring grey button with black
text. I'd like to Give it the same bright yellow background that InsetInfo
has now, but at the moment this isn't possible because PainterBase::button()
is hard-coded to draw the button in boring grey!
PainterBase
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Ok, I've made the basic inset. It's a rather boring grey button
Angus with black text. I'd like to Give it the same bright yellow
Angus background that InsetInfo has now, but at the moment this isn't
Angus possible because
It seems to me that you would need to pass several colors, in order to
get the 3d effect.
Yes. Sod that. Let's have "note" with yellow text on a grey background. It
looks kinda cute!
InsetNote is now a straight replacement for InsetInfo. Ie, it has no output
to LaTeX, but is a collapsable
I'm answering my own mail here. Sorry! But I'm asking another question.
In Buffer::readInset() am I allowed the following code?
string tmptok = lex.GetString();
...
// The old InsetInfo
} else if (tmptok == "Info") {
Inset * inset = new
On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote:
\begin_inset Info
This is just a stupid little note
\end_inset
It is now
\begin_inset Info
collapsed true
\layout Standard
is just a stupid little note
\end_inset
Why do you keep a state of the inset?
IIRC no
All collapsible insets output this. Indeed, if it ain't found on input, then
an error message is output.
A.
On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote:
On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote:
\begin_inset Info
This is just a stupid little note
\end_inset
On Fri, Sep 22, 2000 at 05:26:54PM +0100, Angus Leeming wrote:
All collapsible insets output this. Indeed, if it ain't found on input, then
an error message is output.
A.
My mistake then. That means that I have used that feature...
BTW is it possible to have
\begin_inset XYZ
collapsed
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Angus" == Angus Leeming [EMAIL PROTECTED] writes:
|
| Angus Then somone (!?!) would show me how to write comments to Latex
| Angus that could subsequently be interpretted by reLyX and read back
| Angus into LyX?
|
| Angus By the way, what's
Juergen Vigna [EMAIL PROTECTED] writes:
| About the question of the 2 point, Lars said there is something like
| a comment environment in LaTeX, but he has to explain how it works
|;)
read comment.sty?
We have had the comment layout for a _long_ time now. You have
obviously not used it.
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Juergen" == Juergen Vigna [EMAIL PROTECTED] writes:
|
| Juergen About the question of the 2 point, Lars said there is
| Juergen something like a comment environment in LaTeX, but he has to
| Juergen explain how it works ;)
|
| verbatim.sty
On Fri, 22 Sep 2000, Allan Rae wrote:
> Info will become a collapsible inset and so it won't be needing a dialog
> in future. It should be fairly easy to implement (give it a better name
> at the same time like InsetProofread or something since it's meant for
> sticking editting notes into and
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Then somone (!?!) would show me how to write comments to Latex
Angus> that could subsequently be interpretted by reLyX and read back
Angus> into LyX?
Angus> By the way, what's wrong with the name? Your comment that "it's
Angus>
On Fri, Sep 22, 2000 at 11:28:35AM +0200, Jean-Marc Lasgouttes wrote:
> As I see it, we need 3 related insets:
>
> - one which outputs as % latex comments (InsetNote?). This one could
> be restricted to text only, since we cannot expect reLyX to parse
> everything after a % as valid latex.
>
On 22-Sep-2000 Jean-Marc Lasgouttes wrote:
> As I see it, we need 3 related insets:
>
> - one which outputs as % latex comments (InsetNote?). This one could
> be restricted to text only, since we cannot expect reLyX to parse
> everything after a % as valid latex.
> - one which outputs as a
On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote:
> On Fri, Sep 22, 2000 at 10:44:34AM +0100, Angus Leeming wrote:
> > On the otherhand, José's suggestion of a checkbox is a cool one. Not that
> > I've any idea of how to implement it!
>
> Like the url inset. There you have the option from
> About the question of the 2 point, Lars said there is something like
> a comment environment in LaTeX, but he has to explain how it works ;)
If you write
\begin{comment}
some text
\end{comment}
in LaTeX, 'some text' won't be typeset.
Is that what you mean?
Andre'
--
Andre' Poenitz
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Yes. Could you explain what you mean by the second case,
Angus> Jean-Marc. I don't really see the difference between cases 1
Angus> and 3. Why not output to LaTeX always. It's only a note and
Angus> will not be present in the
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> About the question of the 2 point, Lars said there is
Juergen> something like a comment environment in LaTeX, but he has to
Juergen> explain how it works ;)
verbatim.sty provides it. However this is quite a big machniery from
Thanks for all this input.
I'm going to try and summarise it all and so define what the new InsetNote
should do.
1. It should be a collapsable inset.
2. It should output nothing to Ascii, Linuxdoc or DocBook. Don't argue here.
We can always change later!
3. People have suggested a
Ok, I've made the basic inset. It's a rather boring grey button with black
text. I'd like to Give it the same bright yellow background that InsetInfo
has now, but at the moment this isn't possible because PainterBase::button()
is hard-coded to draw the button in boring grey!
PainterBase &
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Ok, I've made the basic inset. It's a rather boring grey button
Angus> with black text. I'd like to Give it the same bright yellow
Angus> background that InsetInfo has now, but at the moment this isn't
Angus> possible because
> It seems to me that you would need to pass several colors, in order to
> get the 3d effect.
Yes. Sod that. Let's have "note" with yellow text on a grey background. It
looks kinda cute!
InsetNote is now a straight replacement for InsetInfo. Ie, it has no output
to LaTeX, but is a collapsable
I'm answering my own mail here. Sorry! But I'm asking another question.
In Buffer::readInset() am I allowed the following code?
string tmptok = lex.GetString();
...
// The old InsetInfo
} else if (tmptok == "Info") {
Inset * inset = new
On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote:
> \begin_inset Info
> This is just a stupid little note
> \end_inset
>
> It is now
>
> \begin_inset Info
> collapsed true
>
> \layout Standard
>
>
> is just a stupid little note
> \end_inset
Why do you keep a state of the
All collapsible insets output this. Indeed, if it ain't found on input, then
an error message is output.
A.
On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote:
> On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote:
> > \begin_inset Info
> > This is just a stupid little note
> >
On Fri, Sep 22, 2000 at 05:26:54PM +0100, Angus Leeming wrote:
> All collapsible insets output this. Indeed, if it ain't found on input, then
> an error message is output.
> A.
My mistake then. That means that I have used that feature...
BTW is it possible to have
\begin_inset XYZ
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
|
| Angus> Then somone (!?!) would show me how to write comments to Latex
| Angus> that could subsequently be interpretted by reLyX and read back
| Angus> into LyX?
|
| Angus> By the
Juergen Vigna <[EMAIL PROTECTED]> writes:
| About the question of the 2 point, Lars said there is something like
| a comment environment in LaTeX, but he has to explain how it works
|;)
read comment.sty?
We have had the comment layout for a _long_ time now. You have
obviously not used it.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
|
| Juergen> About the question of the 2 point, Lars said there is
| Juergen> something like a comment environment in LaTeX, but he has to
| Juergen> explain how it works ;)
|
|
I see that the following files in src/insets still #include FORMS_H_LOCATION:
figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h,
insetexternal.C, insetinclude.C, insetinfo.h
Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this
direction? What about
On Thu, 21 Sep 2000, Angus Leeming wrote:
I see that the following files in src/insets still #include FORMS_H_LOCATION:
figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h,
insetexternal.C, insetinclude.C, insetinfo.h
Are form_graphics.[Ch] to be made redundant by
On Thu, 21 Sep 2000, Angus Leeming wrote:
I see that the following files in src/insets still #include FORMS_H_LOCATION:
figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h,
insetexternal.C, insetinclude.C, insetinfo.h
Are form_graphics.[Ch] to be made redundant by
I see that the following files in src/insets still #include FORMS_H_LOCATION:
figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h,
insetexternal.C, insetinclude.C, insetinfo.h
Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this
direction? What about
On Thu, 21 Sep 2000, Angus Leeming wrote:
> I see that the following files in src/insets still #include FORMS_H_LOCATION:
>
> figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h,
> insetexternal.C, insetinclude.C, insetinfo.h
>
> Are form_graphics.[Ch] to be made redundant
On Thu, 21 Sep 2000, Angus Leeming wrote:
> I see that the following files in src/insets still #include FORMS_H_LOCATION:
>
> figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h,
> insetexternal.C, insetinclude.C, insetinfo.h
>
> Are form_graphics.[Ch] to be made redundant
54 matches
Mail list logo
