Bo Peng wrote:
> During a fast-evolving period like this, with no public release in
> between, reversion of lyx2lyx is IMHO acceptable
I think we discussed this sufficiently now. It doesn't matter in which release
perdiod we are.
Jürgen
Bo Peng wrote:
> I change from 4.3 format to 4.22 (which is supposedly the same as
> 4.1). I could not compile the trunk without this change.
Now I'm puzzled.
Jürgen
Andre Poenitz wrote:
> ../../trunk/src/LyXFunc.cpp:2477: warning: enumeration value
> 'RC_DEFFILE' not handled in switch
> ../../trunk/src/LyXFunc.cpp:2477: warning: enumeration value
> 'RC_USE_PIXMAP_CACHE' not handled in switch
The latter is fixed. This is commented-out code btw.
Jürgen
OK, thanks.
- Martin
On Sat, Nov 03, 2007 at 12:35:08AM +, [EMAIL PROTECTED] wrote:
> Author: younes
> Date: Sat Nov 3 01:35:07 2007
> New Revision: 21396
>
> URL: http://www.lyx.org/trac/changeset/21396
> Log:
> Further cleanup of InsetFlex, InsetCollapsable and InsetLayout:
> - Getting rid of some unneeded init
On Fri, Nov 02, 2007 at 11:12:45PM +, [EMAIL PROTECTED] wrote:
> Author: younes
> Date: Sat Nov 3 00:12:43 2007
> New Revision: 21394
>
> URL: http://www.lyx.org/trac/changeset/21394
> Log:
> Remremove unneeded init() method.
>
>
> Modified:
> lyx-devel/trunk/src/insets/InsetListings.cp
Uwe Stöhr wrote:
This description is independent from CTAN. We need an explanation for
all document classes we ship with LyX in LateXConfig.lyx. So it would
be nice when you could send a patch for LaTeXConfig.lyx the next days.
Sorry for being late. Please apply the attached patch to add desc
> But this introduces crashed: I can for example not open Stefan's macro
> example file, see my just
> sent post on the list.
As far as I know, today's crash is caused by some insets, not \begin manifest.
Bo
> I need to include feynman diagrams in my lyx-document.
Here is an alternative that don't need metafont scripts:
http://wiki.lyx.org/Tips/FeynmanDiagrams
regards Uwe
> During a fast-evolving period like this, with no public release in
> between, reversion of lyx2lyx is IMHO acceptable.
But this introduces crashed: I can for example not open Stefan's macro example file, see my just
sent post on the list.
Besides this we have the general problem that LyX can
Martin Vermeer wrote:
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
I fought with this fruitlessly until Jean-Marc showed me. You
reverted to my old non-working code :-(
Calm down, I found a better solution (appended below, I guess you cannot
read lyx-cvs?).
Yes, b
Stefan Schimanski schrieb:
I have many test cases here: http://1stein.org/download/testcases.lyx
With this file LyX crashes. Could you send me a file that I can open with
current trunk?
thanks and regards
Uwe
On Fri, Nov 02, 2007 at 09:27:41PM -, [EMAIL PROTECTED] wrote:
> Author: younes
> Date: Fri Nov 2 22:27:41 2007
> New Revision: 21392
>
> URL: http://www.lyx.org/trac/changeset/21392
> Log:
> Further cleanup of collapsable insets. The layouts are now properly read and
> applied.
>
>
> Modi
On Sat, Nov 03, 2007 at 12:00:42AM +0100, Abdelrazak Younes wrote:
...
> >> OK, I've done some cleanup an the crashes are gone but the inset layouts
> >> are broken!
> >>
> >> Martin, Richard, do you have an idea here? I don't know if we shall we
> >> fix Inset::getLayout() or if we shall a
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 06:51:54PM +0100, Abdelrazak Younes wrote:
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signa
On Fri, Nov 02, 2007 at 06:51:54PM +0100, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
> > On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
> >> Start lyx, open a "recent document" - assert.
> >>
> >> Case one (A11.lyx, beamer presentation)
> > ...
> >> Program received sign
On Nov 2, 2007 3:47 PM, Uwe Stöhr <[EMAIL PROTECTED]> wrote:
> >> I can do that, no problem.
> >> I though lyx2lyx would do such things anyway though,
> >
> > I did not want to complicate lyx2lyx by adding another reversion
> > function to remove this section.
>
> This won't complicate lyx2lyx
>> I can do that, no problem.
>> I though lyx2lyx would do such things anyway though,
>
> I did not want to complicate lyx2lyx by adding another reversion
> function to remove this section.
This won't complicate lyx2lyx, that's what lyx2lyx is for. Removing stuff manually from a LyX file
using a
> I applied the thing to branch.
I need to describe this in the docs. What exactly does the pixmap? Is there a
wiki-page about this?
regards Uwe
lyxactOnUpdatedPrefs(const lyx::LyXRC&, const
lyx::LyXRC&)':
../../trunk/src/LyXFunc.cpp:2477: warning: enumeration value
'RC_DEFFILE' not handled in switch
../../trunk/src/LyXFunc.cpp:2477: warning: enumeration value
'RC_USE_PIXMAP_CACHE' not handled in switch
Please fix.
Andre'
On Fri, Nov 02, 2007 at 02:33:03PM +0100, Edwin Leuven wrote:
> Uwe Stöhr wrote:
>> Then my comments are not good enough. \href requires some characters to be
>> escaped or changed. The for loop parse the string for a certain character
>> and do something with it when found. Every loop run checks
Abdelrazak Younes wrote:
OK, I've done some cleanup an the crashes are gone but the inset layouts
are broken!
Martin, Richard, do you have an idea here? I don't know if we shall we
fix Inset::getLayout() or if we shall assume that each inset hard-code
its own layout.
OK, I see that the fon
Andre Poenitz wrote:
On Fri, Nov 02, 2007 at 05:33:08PM +0100, Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
[EMAIL PROTECTED] wrote:
save prefui in qt422 format
Since when do we require qt 4.2?
The format is the same as 4.1.
In any case, we should bump the requirements.
Are you pre
On Fri, Nov 02, 2007 at 05:33:08PM +0100, Abdelrazak Younes wrote:
> Jürgen Spitzmüller wrote:
>> [EMAIL PROTECTED] wrote:
>>> save prefui in qt422 format
>> Since when do we require qt 4.2?
>
> The format is the same as 4.1.
In any case, we should bump the requirements.
Andre'
On Nov 2, 2007 11:55 AM, Jürgen Spitzmüller <[EMAIL PROTECTED]> wrote:
> Abdelrazak Younes wrote:
> > The format is the same as 4.1.
>
> So why the change? I did the designer changes with qt 4.1.
I change from 4.3 format to 4.22 (which is supposedly the same as
4.1). I could not compile the trunk
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
The format is the same as 4.1.
So why the change? I did the designer changes with qt 4.1.
Yep, and that was the reason why the change was so big in your last
commit. I think Designer 4.2 sometimes re-arrange the structure but it
stays 4.1
Abdelrazak Younes wrote:
> The format is the same as 4.1.
So why the change? I did the designer changes with qt 4.1.
Jürgen
Jürgen Spitzmüller wrote:
[EMAIL PROTECTED] wrote:
save prefui in qt422 format
Since when do we require qt 4.2?
The format is the same as 4.1.
Abdel.
[EMAIL PROTECTED] wrote:
> save prefui in qt422 format
Since when do we require qt 4.2?
Jürgen
> This seems to be my fault. Which Qt do you use? Maybe the QColor
> constructors with reals are too new. Cannot check myself right now as I am
> in the middle of a OS update, sorry.
4.3.0
pavel
GuiPainter.cpp: In member function 'QColor
lyx::frontend::GuiPainter::filterColor(const QColor&)':
GuiPainter.cpp:140: warning: passing 'qreal' for argument 1 to
'QColor::QColor(int, int, int, int)'
GuiPainter.cpp:140: warning: passing 'qreal' for argument 2 to
'QColor::QColor(int, int, int,
Martin Vermeer wrote:
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa62949b0 (LWP 10363)]
0x0832ec16
On Fri, Nov 02, 2007 at 04:12:15PM +0100, Helge Hafting wrote:
> I experiment with the new modules, and saw a problem
> with "code" today. (LyX compiled 17.oct)
>
> If I emphasize a paragraph that contains a word in 'code'
> text style, then the code is emphasized too - as it should.
>
> If
> I can do that, no problem.
> I though lyx2lyx would do such things anyway though,
I did not want to complicate lyx2lyx by adding another reversion
function to remove this section.
> or that the unknown stuff would be lost the next time I save
> a changed file?
Yes. (But the trunk crashes quite
I experiment with the new modules, and saw a problem
with "code" today. (LyX compiled 17.oct)
If I emphasize a paragraph that contains a word in 'code'
text style, then the code is emphasized too - as it should.
If I first emphasize the word and then apply 'code'
around the emphasized word, then
Bo Peng wrote:
On Nov 2, 2007 6:45 AM, Helge Hafting <[EMAIL PROTECTED]> wrote:
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token: `\be
> Confirmed. Please open a bug report with target 1.5.3.
Done. 4317.
Bo
Bo Peng wrote:
> 1. Create a new file, enter two lines of text and change the style of
> the first line to section. ( a sample is attached).
>
> 2. select both lines, with mouse ending at the first line.
>
> 3. type something, the section title is changed
>
> 4. click on the second line, lyx crashe
Helge Hafting wrote:
> "cc" is a unit of measure, as well as short for "carbon copy".
> These cases need different translations, this is now possible
> by changing to "cc[[unit of measure]]". (The bracketed explanation is
> not used in the compiled binary, of course.)
committed to trunk and branch
On Nov 2, 2007 6:45 AM, Helge Hafting <[EMAIL PROTECTED]> wrote:
> Start lyx, open a "recent document" - assert.
>
> Case one (A11.lyx, beamer presentation)
>
> Handling unknown body token: `\begin_manifest'
> Handling unknown body token: `\end_manifest'
> Handling unknown body token: `\begin_manif
On Fri, Nov 02, 2007 at 12:45:49PM +0100, Helge Hafting wrote:
> Start lyx, open a "recent document" - assert.
>
> Case one (A11.lyx, beamer presentation)
...
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xa62949b0 (LWP 10363)]
> 0x0832ec16 in lyx::InsetCo
Edwin Leuven wrote:
Uwe Stöhr wrote:
Then my comments are not good enough. \href requires some characters
to be escaped or changed. The for loop parse the string for a certain
character and do something with it when found. Every loop run checks
for another character of the list.
maybe qurl c
Abdelrazak Younes wrote:
> Juergen?
OK.
Jürgen
Uwe Stöhr wrote:
Then my comments are not good enough. \href requires some characters to
be escaped or changed. The for loop parse the string for a certain
character and do something with it when found. Every loop run checks for
another character of the list.
maybe qurl can help here?
http:/
Uwe Stöhr wrote:
> There are other things to clean up in there, it is not clear what the
different 'for' loop are
> doing with the strings.
Then my comments are not good enough. \href requires some characters to
be escaped or changed. The for loop parse the string for a certain
character an
>> Richard, we have a restriction of which you might not ave heard yet:
>> static functions/objects need to have different names, even if they
>> are in different .cpp files, otherwise the 'chunked build' will fail.
>>
> Sorry! I've fixed it.
>
> rh
there is another one problem:
make[6]: Enter
Thanks for looking at this!
> That's because you used strings instead of characters.
Yes this was really my problem - sometimes things can be so simple.
> There are other things to clean up in there, it is not clear what the
different 'for' loop are
> doing with the strings.
Then my comments
Two tranlsation clashes in lengthcommon.cpp fixed in
the attached patch:
The unit cc clashes with cc meaning carbon copy.
The unit in clashes with other use of the word in.
Solved by changing to cc[[unit of measure]] and in[[unit of measure]]
I changed the units only, because these are less like
"cc" is a unit of measure, as well as short for "carbon copy".
These cases need different translations, this is now possible
by changing to "cc[[unit of measure]]". (The bracketed explanation is
not used in the compiled binary, of course.)
The patch is minimal as the cc unit appear once, while "c
Start lyx, open a "recent document" - assert.
Case one (A11.lyx, beamer presentation)
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Handling unknown body token: `\begin_manifest'
Handling unknown body token: `\end_manifest'
Program received signal S
Pavel Sanda wrote:
What is the correct way to do this?
you can not do this until somebody changes string in source code
using [[]] .
Ok, I'll create a trivial patch to the source for this.
Helge Hafting
Abdelrazak Younes wrote:
> And I confirm that it works fine.
Good. I applied the thing to branch. Will do trunk later.
Jürgen
Abdelrazak Younes wrote:
Bennett Helm wrote:
On Oct 24, 2007, at 11:45 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Oct 24, 2007, at 2:16 AM, Abdelrazak Younes wrote:
I'm not sure what to be testing here. Is the patch already applied
in changeset 20728? (If not, what is the patch?) In
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
The attached patch implements a pref option to enable the pixmap
cache on
Windows and the Mac (it is now disabled by default).
I cannot really test, since I'm on Linux. Could someone do thi
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
The attached patch implements a pref option to enable the pixmap
cache on
Windows and the Mac (it is now disabled by default).
I cannot really test, since I'm on Linux. Could someone do this and
check
that it work
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
The attached patch implements a pref option to enable the pixmap cache on
Windows and the Mac (it is now disabled by default).
I cannot really test, since I'm on Linux. Could someone do this and check
that it works?
-bool const usePixmapCac
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
It can be done easily, if needed.
I think you should do it.
Sorry, I mean you should implement the option in trunk first and then
backport it to branch.
Abdel.
Juergen Spitzmueller wrote:
The attached patch implements a pref option to enable the pixmap cache on
Windows and the Mac (it is now disabled by default).
I cannot really test, since I'm on Linux. Could someone do this and check
that it works?
-bool const usePixmapCache = USE_PIXMAP_CACHE;
+bo
Juergen Spitzmueller wrote:
Program received signal SIGSEGV, Segmentation fault.
I see the crash in MSVC too. It happens when loading the Tutorial but
not the introduction. The crash did not happen yesterday morning.
Abdel.
#3 0x085a12c3 in lyx::InsetCollapsable::dimensionCollapsed (
Hans Meine wrote:
On Freitag 02 November 2007, Abdelrazak Younes wrote:
@@ -77,10 +77,10 @@
OutputParams const & runparams) const
{
//FIXME: all strings in this routine should be docstrings
- string url = to_utf8(getParam("target"));
+ docstring url = ge
On Freitag 02 November 2007, Abdelrazak Younes wrote:
> @@ -77,10 +77,10 @@
> OutputParams const & runparams) const
> {
> //FIXME: all strings in this routine should be docstrings
> - string url = to_utf8(getParam("target"));
> + docstring url = getParam("target");
Uwe Stöhr wrote:
Enrico wrote today:
> Now waiting for the next bug associated
> to unsigned chars and docstreams.
There's a potential problem in Hyperlink.cpp I'm not able to fix:
http://www.lyx.org/trac/changeset/21352
Could anybody please help me here? I can't get it to work when I change
63 matches
Mail list logo
