José Matos <[EMAIL PROTECTED]> writes:
> On Friday 26 September 2008 14:43:44 Jean-Marc Lasgouttes wrote:
>> PS: here is my updated insetinfo patch with further simplifications.
>
> Post rc3, please.
Yes, this was my plan.
JMarc
On Friday 26 September 2008 14:43:44 Jean-Marc Lasgouttes wrote:
> PS: here is my updated insetinfo patch with further simplifications.
Post rc3, please.
As soon as you are happy with the resulting code this can go in.
--
José Abílio
"Vincent van Ravesteijn - TNW" <[EMAIL PROTECTED]> writes:
> See:
>
> "Why doesn't overloading work for derived classes?" at
>
> http://www.research.att.com/~bs/bs_faq2.html#overloadderived
Yes, it works! I am not convinced by the argument, but it is OK.
JMarc
PS: here is my updated insetinfo pa
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I guess gcc has difficulties to decide between the two versions of it
> because if InsetText::setText() had a default value to _its_ second
> argument, there would be no _way_ to differentiate them.
Looks like Vincent solution was the right one.
JMa
On 26/09/2008 14:51, Abdelrazak Younes wrote:
On 26/09/2008 14:11, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes<[EMAIL PROTECTED]> writes:
One not so minor comment: please use InsetCollapsable::xxx instead of
InsetText::xxx unless you explicitely don't want to use existent
InsetCollapsable me
On 26/09/2008 14:11, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes<[EMAIL PROTECTED]> writes:
One not so minor comment: please use InsetCollapsable::xxx instead of
InsetText::xxx unless you explicitely don't want to use existent
InsetCollapsable method.
Better: could you tell me why
>Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> One not so minor comment: please use InsetCollapsable::xxx instead of
>> InsetText::xxx unless you explicitely don't want to use existent
>> InsetCollapsable method.
>Better: could you tell me why I cannot directly use setText() and need
>to add
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> One not so minor comment: please use InsetCollapsable::xxx instead of
> InsetText::xxx unless you explicitely don't want to use existent
> InsetCollapsable method.
Better: could you tell me why I cannot directly use setText() and need
to add the Inse
On 25/09/2008 15:14, Jean-Marc Lasgouttes wrote:
rgheck<[EMAIL PROTECTED]> writes:
Well, if you're going to leave InsetInfo until after 1.6, we can do
this together. You can tell me what character styles you want, and
I'll produce definitions of them that you can use. I've already done
this
rgheck <[EMAIL PROTECTED]> writes:
> This looks good to me. It's really a great illustration of why
> InsetLayout was such a great idea. Yours, if I recall
Maybe, but Martin did all the hard work.
JMarc
Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
Well, if you're going to leave InsetInfo until after 1.6, we can do
this together. You can tell me what character styles you want, and
I'll produce definitions of them that you can use. I've already done
this for Customization, as
On 25/09/2008 15:40, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes<[EMAIL PROTECTED]> writes:
1/ make InsetInfo depend on InsetCollapsable (this is only because I
need this to have an insetlayout, in principle InsetText is OK).
Why not transferring InsetLayout to InsetText as you i
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> 1/ make InsetInfo depend on InsetCollapsable (this is only because I
>> need this to have an insetlayout, in principle InsetText is OK).
>
> Why not transferring InsetLayout to InsetText as you initially suggested?
Because it requires a bit more wor
On 25/09/2008 15:14, Jean-Marc Lasgouttes wrote:
rgheck<[EMAIL PROTECTED]> writes:
Well, if you're going to leave InsetInfo until after 1.6, we can do
this together. You can tell me what character styles you want, and
I'll produce definitions of them that you can use. I've already done
this
rgheck <[EMAIL PROTECTED]> writes:
> Well, if you're going to leave InsetInfo until after 1.6, we can do
> this together. You can tell me what character styles you want, and
> I'll produce definitions of them that you can use. I've already done
> this for Customization, as you'll see if you look un
rgheck <[EMAIL PROTECTED]> writes:
> Can't you put an InsetInfo into a character style of the appropriate type?
We can do better: specify an InsetLayout for these things. Of course,
life would be easier if InsetLayout was at InsetText level...
JMarc
On 25/09/2008 09:39, Jean-Marc Lasgouttes wrote:
Uwe Stöhr<[EMAIL PROTECTED]> writes:
Why is there no GUI?
Because it is more intended for documenters than plain users. And
because it was thought that the current choice is as fast as what a gui
would give (unless maybe if we have a
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Why is there no GUI?
Because it is more intended for documenters than plain users. And
because it was thought that the current choice is as fast as what a gui
would give (unless maybe if we have a function browser).
> I mean the users will see this inset i
On 24/09/2008 14:42, Jean-Marc Lasgouttes wrote:
Uwe Stöhr<[EMAIL PROTECTED]> writes:
Jean-Marc Lasgouttes schrieb:
I have a question of my own too: do you have plans to use InsetInfo in
the docs?
How can I insert an InsetInfo, there is no menu entry for this? Where should
Pavel Sanda wrote:
Uwe Stöhr wrote:
But to use it for the docs I miss the possibility to customize
InsetInfo's output. In the docs, menu names and shortcuts are in sans
serif, icons have a uniform size of 80%. So I need a way to specify the
output of the different InsetInfo types for the cu
> The latter (e.g. "song"). It's the second mandatory argument of the CJK
> environment.
Thanks Jürgen for you quick reply. I added this info to th docs.
regards Uwe
Uwe Stöhr wrote:
>>> But to use it for the docs I miss the possibility to customize
>>> InsetInfo's output. In the docs, menu names and shortcuts are in sans
>>> serif, icons have a uniform size of 80%. So I need a way to specify the
>>> output of the different InsetInfo types for the current do
Uwe Stöhr wrote:
rgheck schrieb:
But to use it for the docs I miss the possibility to customize
InsetInfo's output. In the docs, menu names and shortcuts are in
sans serif, icons have a uniform size of 80%. So I need a way to
specify the output of the different InsetInfo types for the current
rgheck schrieb:
But to use it for the docs I miss the possibility to customize
InsetInfo's output. In the docs, menu names and shortcuts are in sans
serif, icons have a uniform size of 80%. So I need a way to specify
the output of the different InsetInfo types for the current document.
Can'
Uwe Stöhr wrote:
> Everything is explained in src/insets/InsetInfo.h,
So it is well hidden ;-)
Why is there no GUI? I mean the users will see this inset in the
documentation files and ask how to use it and what it is for.
It's not really meant for ordinary users, I don't think. It gives you
Why is there no GUI? I mean the users will see this inset in the
documentation files and ask how to use it and what it is for. So
InstInfo should at least be described in the Extended or Customization manual.
Could you do this please?
> Everything is explained in src/insets/InsetInfo.h,
So it is well hidden ;-)
Why is there no GUI? I mean the users will see this inset in the documentation files and ask how to
use it and what it is for. So InstInfo should at least be described in the
> 1. input the type and argument of thi
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes schrieb:
>
>> I have a question of my own too: do you have plans to use InsetInfo in
>> the docs?
>
> How can I insert an InsetInfo, there is no menu entry for this? Where should
> I use it?
Everything is explained in src/insets/InsetI
Uwe Stöhr wrote:
Jean-Marc Lasgouttes schrieb:
I have a question of my own too: do you have plans to use InsetInfo in
the docs?
How can I insert an InsetInfo, there is no menu entry for this?
That I do not know either (I always copied from elsewhere), but there
should be an LFUN for it.
Jean-Marc Lasgouttes schrieb:
I have a question of my own too: do you have plans to use InsetInfo in
the docs?
How can I insert an InsetInfo, there is no menu entry for this? Where should I
use it?
regards Uwe
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> In order to finish the documentation update for LyX 1.6.0 there are
> have several features that I haven't fully understood or no idea how
> they are used. So I'll come up with some questions, here's the first
> one:
I have a question of my own too: do you h
Uwe Stöhr wrote:
> In the document settings menu there is under Fonts a new field "CJK" with
> the tooltip that one can enter there the font for CJK script. How is the
> font name entered, is it a file name like "kanji3.pfb" or just the name of
> the font like "kanji-c"?
The latter (e.g. "song").
In order to finish the documentation update for LyX 1.6.0 there are have several features that I
haven't fully understood or no idea how they are used. So I'll come up with some questions, here's
the first one:
In the document settings menu there is under Fonts a new field "CJK" with the toolti
33 matches
Mail list logo
