Pavel Sanda wrote:
Pavel Sanda wrote:
I purposely left RC_VISUAL_CURSOR out of this function, because something
is fishy about it. AFAICT, this function doesn't do anything... JMarc
took a look and I think he also wasn't sure about it... So before just
fixing the warnings, we ought to try and
After a hiatus, I'm returning to the rewrite of InsetCommandParams, the
purpose of all of this being to make things more flexible, with the
ultimate goal being biblatex support and a kind of InsetCommandFlex that
will allow user-definable such things. The next step, really, is to fix
up CiteE
Andre Poenitz schrieb:
On Sat, Feb 23, 2008 at 12:06:18AM +0100, Bernhard Roider wrote:
hello,
yesterday i played around with layout files and created the following
counter definition (ok, i didn't read the docs carefully enough)
Counter
Name MajorVersion
Labe
On Sat, Feb 23, 2008 at 12:06:18AM +0100, Bernhard Roider wrote:
> hello,
>
> yesterday i played around with layout files and created the following
> counter definition (ok, i didn't read the docs carefully enough)
>
> Counter
> Name MajorVersion
> LabelString
hello,
yesterday i played around with layout files and created the following counter definition (ok, i
didn't read the docs carefully enough)
Counter
Name MajorVersion
LabelString "\theMajorVersion.0"
End
Using this counter causes lyx to crash because
Andre Poenitz wrote:
On Fri, Feb 22, 2008 at 04:46:44PM -0500, rgheck wrote:
Andre Poenitz wrote:
Does anybody remember why we use a shared pointer and not an index into
the global list of textclasses?
Yes, that was my doing.
So this is a recent change?
A few months
On Fri, Feb 22, 2008 at 04:46:44PM -0500, rgheck wrote:
> Andre Poenitz wrote:
>> Does anybody remember why we use a shared pointer and not an index into
>> the global list of textclasses?
>
> Yes, that was my doing.
So this is a recent change?
> It used to be a list of textclasses, when these we
Andre Poenitz wrote:
Does anybody remember why we use a shared pointer and not an index into
the global list of textclasses?
Yes, that was my doing. It used to be a list of textclasses, when these
were static objects. But now the textclasses that are in use are dynamic
objects: They get cha
Does anybody remember why we use a shared pointer and not an index into
the global list of textclasses?
Andre'
> Dear all,
>
> This patch solves two problems:
>
> 1. LFUN_TEXTCLASS_APPLY and LFUN_TEXTCLASS_LOAD try to load a
> textclass without passing document path. (see loadTextclass(class) in
> line 1765 and 1796 of LyXFunc.cpp). This leads to erraneous behaviors
> when the preamble of a buffer with lo
Dear all,
This patch solves two problems:
1. LFUN_TEXTCLASS_APPLY and LFUN_TEXTCLASS_LOAD try to load a
textclass without passing document path. (see loadTextclass(class) in
line 1765 and 1796 of LyXFunc.cpp). This leads to erraneous behaviors
when the preamble of a buffer with local layout file
Those few files regarding building of lyx, have some vague warnings
about using system boost instead of included one. What is the real
current situation in this matter - Lyx version 1.5.3, Boost version
1.34.1.
On Feb 22, 2008, at 1:33 PM, Pavel Sanda wrote:
I have encountered a couple other problems that seem directly
related to
fullscreen mode:
1. When coming out of fullscreen mode, the normal window returns,
but it
does not automatically take focus as it should.
Bennett, is that focus thing o
> >> i guess there will be more transitional problems wrt 4.4 (rc1 here).
> >> GuiApplication.cpp: In member function 'void
> >> lyx::frontend::GuiApplication::commitData(QSessionManager&)':
> >> GuiApplication.cpp:552: error: invalid use of undefined type 'struct
> >> QSessionManager'
> >
> > #i
> > I have encountered a couple other problems that seem directly related to
> > fullscreen mode:
> >
> > 1. When coming out of fullscreen mode, the normal window returns, but it
> > does not automatically take focus as it should.
Bennett, is that focus thing ok in the current trunk?
>
> pavel
On Thu, Feb 21, 2008 at 11:38:46PM -, [EMAIL PROTECTED] wrote:
> Author: sts
> Date: Fri Feb 22 00:38:46 2008
> New Revision: 23115
>
> URL: http://www.lyx.org/trac/changeset/23115
> Log:
> * typo
>
> Modified:
> lyx-devel/trunk/src/insets/Inset.h
>
> Modified: lyx-devel/trunk/src/insets
On Fri, Feb 22, 2008 at 12:45:22PM +0100, Stefan Schimanski wrote:
> I do not really understand the parser very well. So here is a simple minded
> patch. Andre, as you are mentioned as author, does this make sense? With
> FLAG_ITEM the parser will stop at the closing \end, but ignoring the
> {si
> Pavel Sanda wrote:
>>> I purposely left RC_VISUAL_CURSOR out of this function, because something
>>> is fishy about it. AFAICT, this function doesn't do anything... JMarc
>>> took a look and I think he also wasn't sure about it... So before just
>>> fixing the warnings, we ought to try and fig
On Fri, Feb 22, 2008 at 09:44:47AM +0200, Martin Vermeer wrote:
> The X system should have a routine for doing that...
Yes, but that's not available on Windows.
Using QColor::setNamedColor() might be an option,
void QColor::setNamedColor ( const QString & name )
Sets the RGB valu
Hello,
I've just parsed the wiki page about the subject.
I am very much impressed, you have done a great work!
Thanks a lot again for making (La)TeX so easy to control.
--
Jean-Pierre
Stefan Schimanski wrote:
See http://www.lyx.org/trac/changeset/23133. The two switch cases are
the same. I just merged them.
OK, understood :-)
Abdel.
> Pavel Sanda wrote:
Or 4.4's ;-}
>>> It seems we have a bug there:
>>>
>>> http://bugzilla.lyx.org/show_bug.cgi?id=4568
>>>
>>> Could somebody have a look?
>> i guess there will be more transitional problems wrt 4.4 (rc1 here).
>> GuiApplication.cpp: In member function 'void
>> lyx::frontend
Abdelrazak Younes wrote:
Stefan Schimanski wrote:
See http://www.lyx.org/trac/changeset/23133. The two switch cases are
the same. I just merged them.
I don't follow you. You did more than that:
-if (lyx_view_)
-return lyx_view_->getStatus(cmd);
-enable = false;
-
Stefan Schimanski wrote:
See http://www.lyx.org/trac/changeset/23133. The two switch cases are
the same. I just merged them.
I don't follow you. You did more than that:
-if (lyx_view_)
-return lyx_view_->getStatus(cmd);
-enable = false;
-break;
-
See http://www.lyx.org/trac/changeset/23133. The two switch cases are
the same. I just merged them.
Stefan
Am 22.02.2008 um 17:50 schrieb Abdelrazak Younes:
[EMAIL PROTECTED] wrote:
Author: sts
Date: Fri Feb 22 16:38:26 2008
New Revision: 23133
URL: http://www.lyx.org/trac/changeset/23133
L
[EMAIL PROTECTED] wrote:
Author: sts
Date: Fri Feb 22 16:38:26 2008
New Revision: 23133
URL: http://www.lyx.org/trac/changeset/23133
Log:
* cosmetic
Well, this is not cosmetics. Why did you you do that?
Modified:
lyx-devel/trunk/src/LyXFunc.cpp
Modified: lyx-devel/trunk/src/LyXFunc.cpp
Pavel Sanda wrote:
I purposely left RC_VISUAL_CURSOR out of this function, because something
is fishy about it. AFAICT, this function doesn't do anything... JMarc took
a look and I think he also wasn't sure about it... So before just fixing
the warnings, we ought to try and figure out what this
I do not really understand the parser very well. So here is a simple
minded patch. Andre, as you are mentioned as author, does this make
sense? With FLAG_ITEM the parser will stop at the closing \end, but
ignoring the {sideways}. All the other cases of the \begin handler use
the FLAG_END.
Number 4573
Which bug number?
Stefan
Am 22.02.2008 um 12:34 schrieb Dominik Böhm:
On Fri, Feb 22, 2008 at 12:18 PM, Stefan Schimanski <[EMAIL PROTECTED]>
wrote:
Looks like a bug in the parser.
Thanks for the quick answer, I just filed a bug report.
On Fri, Feb 22, 2008 at 12:18 PM, Stefan Schimanski <[EMAIL PROTECTED]> wrote:
> Looks like a bug in the parser.
Thanks for the quick answer, I just filed a bug report.
[EMAIL PROTECTED] wrote:
Author: younes
Date: Fri Feb 22 12:07:41 2008
New Revision: 23126
URL: http://www.lyx.org/trac/changeset/23126
Log:
Fix this bug:
1. scroll a bit so that the cursor is not visible anymore
2. hit the keyboard arrow keys to move the cursor or type something
The problem wa
Looks like a bug in the parser.
Stefan
Am 22.02.2008 um 12:12 schrieb Dominik Böhm:
Hi,
I am not sure if that's a bug or just not supported. That's the reason
why I send this message to the lyx-devel list.
When you create a new math-macro and insert some
"\begin{sideways}#1\end{sideways}", s
Hi,
I am not sure if that's a bug or just not supported. That's the reason
why I send this message to the lyx-devel list.
When you create a new math-macro and insert some
"\begin{sideways}#1\end{sideways}", save the file and reload it, LyX
isn't able to load the macro properly. Instead of
"\begin
Abdelrazak Younes wrote:
Pavel Sanda wrote:
i'm sorry Abdel, but your polishment brought the old bugs back :(
1. srollbar is not correct after resize (as Enrico noted, its not a
serious bug,
no problem if remain this way)
Are you sure? For me it works correctly... weird.
maybe you just n
Stefan Schimanski <[EMAIL PROTECTED]> writes:
>> I used 'QStyleOptionViewItem' and it seems to compile.
>
> Also seems to work. So I changed it.
Thanks.
JMarc
Am 22.02.2008 um 11:10 schrieb Jean-Marc Lasgouttes:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I only have 'QStyleOptionViewItemV2' on 4.2.
Stefan, are you sure that we really need it?
Does it compile with it?
I used 'QStyleOptionViewItem' and it seems to compile.
Also seems to wor
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> I only have 'QStyleOptionViewItemV2' on 4.2.
>>
>> Stefan, are you sure that we really need it?
>
> Does it compile with it?
I used 'QStyleOptionViewItem' and it seems to compile.
JMarc
Jean-Marc Lasgouttes wrote:
I get:
../../../../lyx-devel/src/frontends/qt4/GuiCompleter.cpp: In member function 'virtual
void lyx::frontend::PixmapItemDelegate::paint(QPainter*, const
QStyleOptionViewItem&, const QModelIndex&) const':
../../../../lyx-devel/src/frontends/qt4/GuiCompleter.cpp:53
I get:
../../../../lyx-devel/src/frontends/qt4/GuiCompleter.cpp: In member function
'virtual void lyx::frontend::PixmapItemDelegate::paint(QPainter*, const
QStyleOptionViewItem&, const QModelIndex&) const':
../../../../lyx-devel/src/frontends/qt4/GuiCompleter.cpp:53: error:
'QStyleOptionViewIt
Martin Vermeer <[EMAIL PROTECTED]> writes:
> Sounds like a plan. And it seems that these SVG colours actually include
> the X colours.
Looks good indeed.
JMarc
On Fri, 22 Feb 2008 10:04:33 +0100
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Jean-Marc Lasgouttes wrote:
> > Martin Vermeer <[EMAIL PROTECTED]> writes:
> >
> >>> or we
> >>> need ColorSet::ColorSet() to include the hex values directly. Or else we
> >>> need to hardcode the hex values wher
OK, I fixed this.
-- Build started: Project: tex2lyx, Configuration: Release Win32 --
Linking...
TextClass.obj : error LNK2019: unresolved external symbol "public:
__thiscall lyx::InsetLayout::InsetLayout(void)"
([EMAIL PROTECTED]@@[EMAIL PROTECTED]) referenced in function "public: class
lyx::InsetLayout
Jean-Marc Lasgouttes wrote:
Martin Vermeer <[EMAIL PROTECTED]> writes:
or we
need ColorSet::ColorSet() to include the hex values directly. Or else we
need to hardcode the hex values where they're wanted.
Rather not. The ColorSet list should be able to contain official X11 names
at that posit
Thanks! Should have enabled stdlib-debug to catch this one.
Stefan
Am 22.02.2008 um 04:21 schrieb rgheck:
Open the User's Guide. Click fast (FAST!) several times on the first
note.
#0 0x003c41430ec5 in raise (sig=) at ../
nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x003c414329
Martin Vermeer <[EMAIL PROTECTED]> writes:
>> or we
>> need ColorSet::ColorSet() to include the hex values directly. Or else we
>> need to hardcode the hex values where they're wanted.
>
> Rather not. The ColorSet list should be able to contain official X11 names
> at that position.
I am not
Hello,
I had just this issue of having to remove page numbers from a document,
but simply setting the page style to "empty" from the document->settings
dialog was not sufficient: still I had the page number in the very first
page.
I generated the LaTeX, and verified that there was a \pagestyle
Hello,
I had just this issue of having to remove page numbers from a document,
but simply setting the page style to "empty" from the document->settings
dialog was not sufficient: still I had the page number in the very first
page.
I generated the LaTeX, and verified that there was a \pagestyle
Am 22.02.2008 um 01:52 schrieb Pavel Sanda:
Well, the set is a sorted container by definition, see here:
you are right. still i feel there is something strange in set[i]
operation :)
The completion popup accesses this containter in a random access way.
Though probably it would be enough
50 matches
Mail list logo
