On Mon, Mar 29, 2010 at 4:50 AM, Vincent van Ravesteijn
wrote:
>> +QMimeData const * read_clipboard() {
>> + LYXERR(Debug::ACTION, "Getting Clipboard\n");
>> + QMimeData const * source =
>> + qApp->clipboard()->mimeData(QClipboard::Clipboard);
>> + if (!source) {
>> + LYXERR
The attached patch introduces the feature to change the color for shaded boxes
(fixes http://www.lyx.org/trac/ticket/3863)
(I plan that this would be my last new feature for LyX 2.0.)
The patch is well tested and works as expected, except of one Ui-issue:
When loading a file with a shaded box, t
As Jürgen suggested in
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg159130.html
we need to distinguish between the default color that can be specified by a document class and the
real colors that the user specified for his document.
Following the way I did this for the new document-wi
>> I googled a bit and even the presentation classes like beamer and
>> powerdot have "black = no color".
>
> But if a beamer template specifies a different color, I assume you will have
> to explicitly reset to black, if you want black.
> In any case, a separation is much saner.
I've implemented
Only a test, please ignore.
I'm not very fond of doing so much small changes in the current stage of the
release cycle. But I assume you tested very carefully, and since they are
rather trivial, I am OK with most of them.
However, please let us focus really on the remaining critical issues after
that.
Especially these tw
Jean-Marc Lasgouttes wrote:
> Yes, I was about to commit this when I saw the conflict. Thanks.
>
> This should go to branch too.
Fine with me.
Jürgen
Uwe Stöhr writes:
>> What compression is used for windows installers, BTW?
>
> LZMA
Good.
JMarc
v...@lyx.org writes:
> Author: vfr
> Date: Fri Apr 2 16:05:15 2010
> New Revision: 34021
> URL: http://www.lyx.org/trac/changeset/34021
>
> Log:
> I guess we mean "Up" here in stead of "Roman".
>
> JMarc ?
Yes, I was about to commit this when I saw the conflict. Thanks.
This should go to branch
Uwe Stöhr schreef:
Am 02.04.2010 15:51, schrieb Vincent van Ravesteijn:
I guess you know that roman is not a shape but a family.
Sure. The bug is in amsart.layout. We can replace there "roman" with
"default" but I don't know if this was Richard's intention. Richard?
regards Uwe
It's r
> What compression is used for windows installers, BTW?
LZMA
regards Uwe
Am 02.04.2010 15:51, schrieb Vincent van Ravesteijn:
I guess you know that roman is not a shape but a family.
Sure. The bug is in amsart.layout. We can replace there "roman" with "default" but I don't know if
this was Richard's intention. Richard?
regards Uwe
Uwe Stöhr schreef:
Load the attached document with LyX 2.0svn and you get this warning:
D:\LyXSVN\lyx-devel\src\FontInfo.cpp(521): Unknown shape `roman'
FontInfo.cpp defined these shapes:
char const * LyXShapeNames[6] =
{ "up", "italic", "slanted", "smallcaps", "default", "error" };
Is the ro
Uwe Stöhr schreef:
Load the attached document with LyX 2.0svn and you get this warning:
D:\LyXSVN\lyx-devel\src\FontInfo.cpp(521): Unknown shape `roman'
FontInfo.cpp defined these shapes:
char const * LyXShapeNames[6] =
{ "up", "italic", "slanted", "smallcaps", "default", "error" };
Is the ro
Am Samstag 27 März 2010 schrieb BH:
> On Mon, Mar 22, 2010 at 10:50 AM, Kornel Benko wrote:
> > We need someone having OSX. You already have some experience there. It is
> > not soo difficult to start with cmake. Maybe you could step in here?
> >
> > Code specific for OSX in e.g. CMakeLists.txt wo
Load the attached document with LyX 2.0svn and you get this warning:
D:\LyXSVN\lyx-devel\src\FontInfo.cpp(521): Unknown shape `roman'
FontInfo.cpp defined these shapes:
char const * LyXShapeNames[6] =
{ "up", "italic", "slanted", "smallcaps", "default", "error" };
Is the roman shape missing pu
Uwe Stöhr wrote:
> I fully agree, but I still think we need a linebreak in the label. But feel
> free to change the label as you like.
The fact that the label is that long is a good indicator that the widget is
put in the wrong context.
> > Also, the font pane is the wrong place. You should i
>> I don't understand. All I have done was to add a label. I set the label text
using Qt 4.6
>> designer. So the code was added by designer, not me. I cannot comment on the
"font-family:" issue
>> because this was also automatically added by designer. (I cannot remember to
have used such a
>> f
Jurgen,
I know it's a bit late, but I still had the following commits in the
candidate-for-branch list.
I remember that we already discussed the first few, but I don't remember what
we concluded.
Vincent
*
Author: vfr
Date: Thu Dec 17 15:09:37
On 04/02/2010 04:51 AM, Jürgen Spitzmüller wrote:
rgheck wrote:
On 03/30/2010 04:15 PM, Jack Desert wrote:
Actually, the first issue is that, especially since 2.0 will (hopefully)
let the user choose conversion paths, etc, we can go ahead and install
both the xhtml->blog and html->blo
Le 02/04/2010 01:21, Pavel Sanda a écrit :
Support for xz and lzma have been added at the same time in automake.
are you sure? my 1.10.3 generated makefile knows dist-lzma, but not dist-xz
target. after hard fight i forced gentoo automake wrapper to choose 1.11.1 and
dist-xz appeared.
This is
Peter Kümmel wrote:
> Pavel Sanda wrote:
>> Abdelrazak Younes wrote:
>>> What about http://gitorious.org/ ? I used that for a project
>>> (http://gitorious.org/sgt in case you're interested) and it works just fine
>>> and reliably.
>> are you able to setup it? (we would need full history and all
Pavel Sanda wrote:
> Abdelrazak Younes wrote:
>> What about http://gitorious.org/ ? I used that for a project
>> (http://gitorious.org/sgt in case you're interested) and it works just fine
>> and reliably.
>
> are you able to setup it? (we would need full history and all branches
> included).
>
Uwe Stöhr wrote:
> >> Why is having a label over 2 lines ugly? Qt supports this and
> >> also many other applications have this. Moreover the font dialog
> >> look OK to me. In fact it's only a matter of taste, isn't it?
> >> What do others think?
> >
> >
> >
> > It's ugly, and I don't want HTML a
rgheck wrote:
> On 03/30/2010 04:15 PM, Jack Desert wrote:
> >> Actually, the first issue is that, especially since 2.0 will (hopefully)
> >> let the user choose conversion paths, etc, we can go ahead and install
> >> both the xhtml->blog and html->blog converters. This is particularly
> >> importa
rgheck wrote:
> > btw i think this is also for branch. Juergen?
> >
> >
>
> Yes, also for branch.
Yes, for 1.6.7, though.
Jürgen
26 matches
Mail list logo
