Seen on the user's list.
We definitely should _not_ crash on asserts. This is about the most
annoying behaviour one can get.
- Forwarded message from Andrew Dolman [EMAIL PROTECTED] -
Date: Wed, 19 Sep 2007 10:24:47 +1000
From: Andrew Dolman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
On Tue, Sep 18, 2007 at 08:15:25PM -0500, Bo Peng wrote:
Possible conclusions: Precompiled headers are a waste of time and space.
22% increase on compile times, ~300% increase on disk space.
Could somebody please try the same test with a different compiler?
I tried a while ago with gcc
Andre Poenitz wrote:
Seen on the user's list.
We definitely should _not_ crash on asserts. This is about the most
annoying behaviour one can get.
Why does he run an assertion enabled binary anyway? The packager
(scons?) should disable assertion for Release mode.
I mean, either we disable
Darren Freeman wrote:
Hi all,
I'm just musing about possible causes for the unbearable slowness that
often befalls LyX and then mysteriously clears with a resize-maximise
cycle. I now realise there are multiple levels of slowness and multiple
cycles of the resize-maximise will restore speed in
On Wednesday 19 September 2007 06:48:10 Martin Vermeer wrote:
IIRC is (emph = {}, noun = []):
[aaa { bbb ] ccc}
will be translated as
[aaa { bbb }]{ ccc}
what is the problem?
Yes, that's how to do it if you insist. And that's how a font attribute
to inset converter has to
On Wednesday 19 September 2007 07:26:06 Abdelrazak Younes wrote:
Why does he run an assertion enabled binary anyway? The packager
(scons?) should disable assertion for Release mode.
I mean, either we disable the assertion or we do something useful with
it, like warn the user about a problem
On Tuesday 18 September 2007 21:54:57 Andre Poenitz wrote:
Is DocBook anywhere in active use?
As I found out through the years the answer is yes but those users will not
report back.
I have found that when googling, searching for other related issues. That
meant that we never had the
On Tuesday 18 September 2007 21:45:07 Bo Peng wrote:
I am not in favor of a separate file extension partly because of the
extra work (document, .cpp etc).
I am not either.
If it is decided to use one, I would
prefer .lyz. 'z' is after 'x', it means 'compression', and '.lyz'
actually
On Wed, 19 Sep 2007 08:07:02 +0100
José Matos [EMAIL PROTECTED] wrote:
On Wednesday 19 September 2007 06:48:10 Martin Vermeer wrote:
IIRC is (emph = {}, noun = []):
[aaa { bbb ] ccc}
will be translated as
[aaa { bbb }]{ ccc}
what is the problem?
Yes, that's how
On Wed, 2007-09-19 at 08:36 +0200, Abdelrazak Younes wrote:
Darren Freeman wrote:
I don't think this is the problem but you can try to disable the 'hover'
with the attached patch.
I verified the bug with the original version, and then patched and
compiled, tried again. I found the slowness
Is DocBook anywhere in active use?
André,
I use LyX and DocBook to Get What I Mean in both professional and private life
- from software documentation to club newsletters, from prose to scientific
papers. I want to write in LyX, then press a button and get everything done. My
lyxtox
On Wed, 2007-09-19 at 08:28 +0100, José Matos wrote:
On Tuesday 18 September 2007 21:45:07 Bo Peng wrote:
Remember, if you have file.lyz and file.lyx in the same directory,
unpacking file.lyz will overwrite file.lyx. You also have to decide if
you want to save file.lyx along with file.lyz
Hi all,
Can anybody explain why there are several repaints involved in a window
resize? (On Linux, Qt-4.2.1)
Starting from a small window, maximise it.
1. Window jumps to full size, Qt widgets are correctly drawn at new
sizes, but the document view is old size with old contents.
2. Document
(Just added the following to bugz..)
Now I've seen the speed-up happen with opening the Outline. It seems to
be specifically related to resizing the document view within the main
window, not only resizing the whole thing.
Also, resizing can result in slow-downs too. This is probably why I
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
I'm now going to test the patched version to see if the slowness comes
back at all.
Okay it came back fairly soon but I can't always clear it by resizing
the window.. why, oh why?
I don't know what else has changed. Can anybody blame the
On Wednesday 19 September 2007 09:09:10 Darren Freeman wrote:
On Wed, 2007-09-19 at 08:28 +0100, José Matos wrote:
On Tuesday 18 September 2007 21:45:07 Bo Peng wrote:
Remember, if you have file.lyz and file.lyx in the same directory,
unpacking file.lyz will overwrite file.lyx. You also
On Wed, 19 Sep 2007 00:28:27 +0300
Martin Vermeer [EMAIL PROTECTED] wrote:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect there's a trick even for that if we go this way.
The
Martin Vermeer wrote:
On Wed, 19 Sep 2007 00:28:27 +0300
Martin Vermeer [EMAIL PROTECTED] wrote:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect there's a trick even for that if
Darren Freeman wrote:
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
I'm now going to test the patched version to see if the slowness comes
back at all.
Okay it came back fairly soon but I can't always clear it by resizing
the window.. why, oh why?
The phase of the moon.
I
Darren Freeman wrote:
Hi all,
Can anybody explain why there are several repaints involved in a window
resize? (On Linux, Qt-4.2.1)
Starting from a small window, maximise it.
1. Window jumps to full size, Qt widgets are correctly drawn at new
sizes, but the document view is old size with old
Okay I'll have to look into profiling. Any tips? Extra build options,
preferred profiling tool?
basic is configure with --enable-profile and i think --disable-stdlib-debug too.
gprof /usr/bin/lyx gmon.out gprof.out
maybe you could try it on both cases and then compare where is the difference.
Bernhard Roider wrote:
if we know the possible extensions we could parse for them exactly (to
avoid false matches).
We don't know really. There might be specific extendions from packages (but
I'm not sure about that).
otherwise i see no problem to keep your first version.
I've committed
On Wed, 2007-09-19 at 11:26 +0200, Abdelrazak Younes wrote:
Darren Freeman wrote:
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
I'm now going to test the patched version to see if the slowness comes
back at all.
Okay it came back fairly soon but I can't always clear it by
Darren Freeman wrote:
On Wed, 2007-09-19 at 11:26 +0200, Abdelrazak Younes wrote:
Darren Freeman wrote:
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
I'm now going to test the patched version to see if the slowness comes
back at all.
Okay it came back fairly soon but I can't
On Wed, 19 Sep 2007 11:19:55 +0200
Abdelrazak Younes [EMAIL PROTECTED] wrote:
Martin Vermeer wrote:
On Wed, 19 Sep 2007 00:28:27 +0300
Martin Vermeer [EMAIL PROTECTED] wrote:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous
In an ideal world, we of course would like to have as less redraws as
possible. Of course this is not an ideal world...
You may think this whole painting stuff is easy to fix but believe me,
with current LyX architecture, it is very complicated. Anyway, I think
those missing
this
http://www.lyx.org/trac/changeset/20357
should take care of it...
-Original Message-
From: Jürgen Spitzmüller [mailto:[EMAIL PROTECTED]
Sent: Tue 9/18/07 11:50
To: LyX Devel
Subject: crash in trunk (preferences-converters)
- Go to Preferences-Converters
- Select a converter, say
On Wed, 19 Sep 2007 11:19:55 +0200
Abdelrazak Younes [EMAIL PROTECTED] wrote:
Martin Vermeer wrote:
On Wed, 19 Sep 2007 00:28:27 +0300
Martin Vermeer [EMAIL PROTECTED] wrote:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous
Pavel Sanda wrote:
In an ideal world, we of course would like to have as less redraws as
possible. Of course this is not an ideal world...
You may think this whole painting stuff is easy to fix but believe me,
with current LyX architecture, it is very complicated. Anyway, I think
those
Martin Vermeer [EMAIL PROTECTED] writes:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect there's a trick even for that if we go this way.
The question is, do we?
Personally, I
Bo Peng [EMAIL PROTECTED] writes:
Possible conclusions: Precompiled headers are a waste of time and space.
22% increase on compile times, ~300% increase on disk space.
Could somebody please try the same test with a different compiler?
I tried a while ago with gcc 3.4 on linux. Autotools'
On Wed, 19 Sep 2007 15:06:30 +0200
Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect
In case it is not clear (and I agree that it is not) the question about
secondary argument refers to unpacking in place.
Unpacking will prompt for overwrite if file.lyx already exists. It is
the save/saveas part that annoys me most. My understanding is that
embedding or not, I am working on
Martin Vermeer [EMAIL PROTECTED] writes:
Also, we need to disable font changing inside, right?
No... why? You may want to have font changes inside an index entry. I
tried and it works in LaTeX too.
OK then. But I would think there are things that not useable there.
The index inset could
hi,
it seems that http://www.lyx.org/trac/changeset/20356
is causing this:
make[6]: Entering directory `/home/paf/mac/ledpar/src/frontends/qt4'
/bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../../../src -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_STL
my fault (or bill's actually ;-)
fixed in trunk:
http://www.lyx.org/trac/changeset/20359
sorry
Jean-Marc Lasgouttes wrote:
The index inset could have a auto boolean property which is set to
true when the index contents was derived by LyX. In this case, the
inset would be shown as plain Idx. This would require an additional
checkbox in the index dialog, which would be unset automatically
Richard Heck [EMAIL PROTECTED] writes:
Yes. But what if you insert an index inset and then change the
preceding word? Then it just says Idx, because auto=true, which is
(I take it) supposed to indicate that the index entry is just what it
should be. But now that's misleading.
Yes, this is a
It is the save/saveas part that annoys me most. My understanding is that
embedding or not, I am working on the same file.
A possible solution to the save/saveas problem might be linking .lyx
and .lyz tightly and say 'save a bundled copy' instead of 'save in
bundled format'. Then, .lyx will
José Matos wrote:
There are other more subtle problems, I have hit them before with docbook.
Using the same notation let us suppose that some range has two properties
applied, which version do we mean?
[{range}] or {[range...]}
The only sane procedure is to look to the export
Jean-Marc Lasgouttes wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect there's a trick even for that if we go this way.
The question
On Wed, Sep 19, 2007 at 06:15:42PM +0200, Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I
On Wed, Sep 19, 2007 at 03:06:30PM +0200, Jean-Marc Lasgouttes wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect there's a trick
Hi,
here comes a new 1.5.X patch candidate list. Please tell me which
patches are (ir)relevant/(not) applicable.
Regards, Michael
New
---
http://www.lyx.org/trac/changeset/20260 - Darken vertical stroke on +
sign as it disappears on some graphic cards.
On Wed, Sep 19, 2007 at 08:26:06AM +0200, Abdelrazak Younes wrote:
Andre Poenitz wrote:
Seen on the user's list.
We definitely should _not_ crash on asserts. This is about the most
annoying behaviour one can get.
Why does he run an assertion enabled binary anyway? The packager
On Wed, Sep 19, 2007 at 08:07:02AM +0100, José Matos wrote:
On Wednesday 19 September 2007 06:48:10 Martin Vermeer wrote:
IIRC is (emph = {}, noun = []):
[aaa { bbb ] ccc}
will be translated as
[aaa { bbb }]{ ccc}
what is the problem?
Yes, that's how to do it if
On Wed, Sep 19, 2007 at 08:10:54AM +0100, José Matos wrote:
On Wednesday 19 September 2007 07:26:06 Abdelrazak Younes wrote:
Why does he run an assertion enabled binary anyway? The packager
(scons?) should disable assertion for Release mode.
I mean, either we disable the assertion or we
On Wed, Sep 19, 2007 at 10:04:41AM +0200, Chris Karakas wrote:
Is DocBook anywhere in active use?
André,
I use LyX and DocBook to Get What I Mean in both professional and
private life - from software documentation to club newsletters, from
prose to scientific papers. I want to
On Wed, Sep 19, 2007 at 03:07:48PM +0200, Jean-Marc Lasgouttes wrote:
Bo Peng [EMAIL PROTECTED] writes:
Possible conclusions: Precompiled headers are a waste of time and space.
22% increase on compile times, ~300% increase on disk space.
Could somebody please try the same test with a
- It corrects LyX' exported SGML code, so that you can use it (otherwise you
will get tons of errors).
I tried to use docbook with lyx but the exported SGML code can not
compile. It there anything specific lyx can do to produce the correct
code? Are there bugzilla entries for them?
Bo
Michael Gerz wrote:
here comes a new 1.5.X patch candidate list. Please tell me which
patches are (ir)relevant/(not) applicable.
I think (but others might correct me), none of these (except for those that
are aready in or on the list I sent last week) are relevant, except perhaps
for these:
On Tue, Sep 18, 2007 at 11:35:46AM +0200, Joost Verburg wrote:
S J Collins wrote:
I need a little more information than your website seems to provide - simply
to work out which was the latest version for Win95 ...
I don't think there is any native version that works with Win95. The
best
Martin Vermeer wrote:
On Wed, Sep 19, 2007 at 06:15:42PM +0200, Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Martin Vermeer [EMAIL PROTECTED] writes:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into
Juergen Spitzmueller wrote:
Michael Gerz wrote:
here comes a new 1.5.X patch candidate list. Please tell me which
patches are (ir)relevant/(not) applicable.
I think (but others might correct me), none of these (except for those that
are aready in or on the list I sent last week) are relevant,
For now I'll add a hint to the docs, when this is OK by you.
Yes, please add a note that g-brief and the current version of marvosym are
incompatible. We could also add a similar note to the g-brief templates.
I'll wait for a reply of the marvosym-maintainer before I proceed.
BTW I think
On Tue, Sep 18, 2007 at 05:04:48PM -, [EMAIL PROTECTED] wrote:
+- Add a pixmap cache to speed up text drawing on screen. This cache is
+ enabled on Mac and Windows platform using a version of Qt greater
+ than 4.2.
This should be rephrased as ... platform using Qt 4.2 or higher.
--
On Wed, Sep 19, 2007 at 12:30:31AM +0200, Andre Poenitz wrote:
Little puzzle for you:
What belongs together?
Configurations:
(A) current svn, --enable-pch
(B) current svn, --disable-pch
Compile times/size of build tree part frontend/qt4:
(1) real 7m35s user 6m25s sys 0m23s
Abdelrazak Younes wrote:
Simple and straight forward.
Indeed. Go ahead.
Jürgen
Uwe Stöhr wrote:
I did this now and sent him a patch to fix marvosym.sty.
Very good. Thanks.
The problem is
indeed that the new marvosym maintainer changed the command definitions
from \providecommand to \newcommand with the actual release from 2006.
I think it used \def in earlier
Enrico Forestieri wrote:
This should be rephrased as ... platform using Qt 4.2 or higher.
Just do it ;-)
(btw if anyone notices style issues, feel free to improve the wording.
Where's Angus when you need him?)
Jürgen
Simple and straight forward.
Juergen?
Index: LyXView.cpp
===
--- LyXView.cpp (revision 20349)
+++ LyXView.cpp (working copy)
@@ -192,6 +192,7 @@
updateTab();
busy(false);
work_area_-redraw();
+
On Wed, Sep 19, 2007 at 06:56:34PM +0200, Michael Gerz wrote:
http://www.lyx.org/trac/changeset/20260 - Darken vertical stroke on +
sign as it disappears on some graphic cards.
Not applicable. This only happens with png images and not xpm ones.
In general, it seems that xpm images are better
On Wed, Sep 19, 2007 at 11:27:47PM +0200, Juergen Spitzmueller wrote:
Enrico Forestieri wrote:
This should be rephrased as ... platform using Qt 4.2 or higher.
Just do it ;-)
(btw if anyone notices style issues, feel free to improve the wording.
Where's Angus when you need him?)
I was
Using LyX 1.4, create a new file containing only a non-ascii character
(à will do). Save and try to reopen it with 1.6 latest svn (there's no
problem with 1.5). You can't.
Traceback (most recent call last):
File /usr/local/src/lyx/lyx-1.6.0svn/lib/lyx2lyx/lyx2lyx, line 77, in ?
doc =
You may want to look at db2latex.
Neal Becker wrote:
You may want to look at db2latex.
Sorry, make that dblatex
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
http://www.lyx.org/trac/changeset/20267 - Somehow this got missed when
(partially) fixing the recursive include problem.
Possibly yes.
I've committed this. I don't know that it was causing problems. I don't
even know that this function gets
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
I am personally OK with it, at least on the code side. Concerning the
binding, I'd prefer to make master-preview the default (using
pdflatex). But this is another story.
I think it can go in now. Juergen, you
Richard Heck ha scritto:
OK. Tommaso, do you want to commit this, then? I can do it Thursday if
you don't have time. And Jurgen, what about branch?
I have only read-access to your svn repository, so far. So, either you
commit it
by yourself, or sb. should give me write permissions so that I
When compiling with --disable-shared, it seems the shared libraries are
being built and installed anyway, which wastes rather a lot of time.
Could this be disabled?
rh
--
==
Richard G Heck, Jr
Professor of Philosophy
Brown
Tommaso Cucinotta wrote:
Richard Heck ha scritto:
OK. Tommaso, do you want to commit this, then? I can do it Thursday
if you don't have time. And Jurgen, what about branch?
I have only read-access to your svn repository, so far. So, either you
commit it
by yourself, or sb. should give me write
Per previous discussion, as a first step towards rationalizing this
stuff. No lyx2lyx is necessary here, because font-code simply invoked
texttt or mathtt as appropriate. Killing LFUN_FONT_NOUN etc will be more
fun for that reason.
For those not privy to the earlier discussion, the rationale
Seen on the user's list.
We definitely should _not_ crash on asserts. This is about the most
annoying behaviour one can get.
- Forwarded message from Andrew Dolman <[EMAIL PROTECTED]> -
Date: Wed, 19 Sep 2007 10:24:47 +1000
From: Andrew Dolman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
On Tue, Sep 18, 2007 at 08:15:25PM -0500, Bo Peng wrote:
> > Possible conclusions: Precompiled headers are a waste of time and space.
> > 22% increase on compile times, ~300% increase on disk space.
> >
> > Could somebody please try the same test with a different compiler?
>
> I tried a while ago
Andre Poenitz wrote:
Seen on the user's list.
We definitely should _not_ crash on asserts. This is about the most
annoying behaviour one can get.
Why does he run an assertion enabled binary anyway? The packager
(scons?) should disable assertion for Release mode.
I mean, either we disable
Darren Freeman wrote:
Hi all,
I'm just musing about possible causes for the unbearable slowness that
often befalls LyX and then mysteriously clears with a resize-maximise
cycle. I now realise there are multiple levels of slowness and multiple
cycles of the resize-maximise will restore speed in
On Wednesday 19 September 2007 06:48:10 Martin Vermeer wrote:
> >
> > IIRC is (emph = {}, noun = []):
> >
> > [aaa { bbb ] ccc}
> >
> > will be translated as
> >
> > [aaa { bbb }]{ ccc}
> >
> > what is the problem?
>
> Yes, that's how to do it if you insist. And that's how a font attribute
> to
On Wednesday 19 September 2007 07:26:06 Abdelrazak Younes wrote:
> Why does he run an assertion enabled binary anyway? The packager
> (scons?) should disable assertion for Release mode.
>
> I mean, either we disable the assertion or we do something useful with
> it, like warn the user about a
On Tuesday 18 September 2007 21:54:57 Andre Poenitz wrote:
> Is DocBook anywhere in active use?
As I found out through the years the answer is yes but those users will not
report back.
I have found that when googling, searching for other related issues. That
meant that we never had the
On Tuesday 18 September 2007 21:45:07 Bo Peng wrote:
> I am not in favor of a separate file extension partly because of the
> extra work (document, .cpp etc).
I am not either.
> If it is decided to use one, I would
> prefer .lyz. 'z' is after 'x', it means 'compression', and '.lyz'
> actually
On Wed, 19 Sep 2007 08:07:02 +0100
José Matos <[EMAIL PROTECTED]> wrote:
> On Wednesday 19 September 2007 06:48:10 Martin Vermeer wrote:
> > >
> > > IIRC is (emph = {}, noun = []):
> > >
> > > [aaa { bbb ] ccc}
> > >
> > > will be translated as
> > >
> > > [aaa { bbb }]{ ccc}
> > >
> > > what is
On Wed, 2007-09-19 at 08:36 +0200, Abdelrazak Younes wrote:
> Darren Freeman wrote:
> I don't think this is the problem but you can try to disable the 'hover'
> with the attached patch.
I verified the bug with the original version, and then patched and
compiled, tried again. I found the
>
>
> Is DocBook anywhere in active use?
>
André,
I use LyX and DocBook to Get What I Mean in both professional and private life
- from software documentation to club newsletters, from prose to scientific
papers. I want to write in LyX, then press a button and get everything done. My
On Wed, 2007-09-19 at 08:28 +0100, José Matos wrote:
> On Tuesday 18 September 2007 21:45:07 Bo Peng wrote:
> > Remember, if you have file.lyz and file.lyx in the same directory,
> > unpacking file.lyz will overwrite file.lyx. You also have to decide if
> > you want to save file.lyx along with
Hi all,
Can anybody explain why there are several repaints involved in a window
resize? (On Linux, Qt-4.2.1)
Starting from a small window, maximise it.
1. Window jumps to full size, Qt widgets are correctly drawn at new
sizes, but the document view is old size with old contents.
2. Document
(Just added the following to bugz..)
Now I've seen the speed-up happen with opening the Outline. It seems to
be specifically related to resizing the document view within the main
window, not only resizing the whole thing.
Also, resizing can result in slow-downs too. This is probably why I
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
> I'm now going to test the patched version to see if the slowness comes
> back at all.
Okay it came back fairly soon but I can't always clear it by resizing
the window.. why, oh why?
I don't know what else has changed. Can anybody blame
On Wednesday 19 September 2007 09:09:10 Darren Freeman wrote:
> On Wed, 2007-09-19 at 08:28 +0100, José Matos wrote:
> > On Tuesday 18 September 2007 21:45:07 Bo Peng wrote:
> > > Remember, if you have file.lyz and file.lyx in the same directory,
> > > unpacking file.lyz will overwrite file.lyx.
On Wed, 19 Sep 2007 00:28:27 +0300
Martin Vermeer <[EMAIL PROTECTED]> wrote:
> The attached does this experimentally. It looks good... what we lose is
> the possibility to get the previous word automatically into the index
> inset. But I suspect there's a trick even for that if we go this way.
>
Martin Vermeer wrote:
On Wed, 19 Sep 2007 00:28:27 +0300
Martin Vermeer <[EMAIL PROTECTED]> wrote:
The attached does this experimentally. It looks good... what we lose is
the possibility to get the previous word automatically into the index
inset. But I suspect there's a trick even for that if
Darren Freeman wrote:
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
I'm now going to test the patched version to see if the slowness comes
back at all.
Okay it came back fairly soon but I can't always clear it by resizing
the window.. why, oh why?
The phase of the moon.
I
Darren Freeman wrote:
Hi all,
Can anybody explain why there are several repaints involved in a window
resize? (On Linux, Qt-4.2.1)
Starting from a small window, maximise it.
1. Window jumps to full size, Qt widgets are correctly drawn at new
sizes, but the document view is old size with old
> Okay I'll have to look into profiling. Any tips? Extra build options,
> preferred profiling tool?
basic is configure with --enable-profile and i think --disable-stdlib-debug too.
gprof /usr/bin/lyx gmon.out > gprof.out
maybe you could try it on both cases and then compare where is the
Bernhard Roider wrote:
> if we know the possible extensions we could parse for them exactly (to
> avoid false matches).
We don't know really. There might be specific extendions from packages (but
I'm not sure about that).
> otherwise i see no problem to keep your first version.
I've committed
On Wed, 2007-09-19 at 11:26 +0200, Abdelrazak Younes wrote:
> Darren Freeman wrote:
> > On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
> >> I'm now going to test the patched version to see if the slowness comes
> >> back at all.
> >
> > Okay it came back fairly soon but I can't always
Darren Freeman wrote:
On Wed, 2007-09-19 at 11:26 +0200, Abdelrazak Younes wrote:
Darren Freeman wrote:
On Wed, 2007-09-19 at 17:58 +1000, Darren Freeman wrote:
I'm now going to test the patched version to see if the slowness comes
back at all.
Okay it came back fairly soon but I can't
On Wed, 19 Sep 2007 11:19:55 +0200
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Martin Vermeer wrote:
> > On Wed, 19 Sep 2007 00:28:27 +0300
> > Martin Vermeer <[EMAIL PROTECTED]> wrote:
> >
> >> The attached does this experimentally. It looks good... what we lose is
> >> the possibility to
> In an ideal world, we of course would like to have as less redraws as
> possible. Of course this is not an ideal world...
>
> You may think this whole painting stuff is easy to fix but believe me,
> with current LyX architecture, it is very complicated. Anyway, I think
> those missing
this
http://www.lyx.org/trac/changeset/20357
should take care of it...
-Original Message-
From: Jürgen Spitzmüller [mailto:[EMAIL PROTECTED]
Sent: Tue 9/18/07 11:50
To: LyX Devel
Subject: crash in trunk (preferences->converters)
- Go to Preferences->Converters
- Select a converter,
On Wed, 19 Sep 2007 11:19:55 +0200
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Martin Vermeer wrote:
> > On Wed, 19 Sep 2007 00:28:27 +0300
> > Martin Vermeer <[EMAIL PROTECTED]> wrote:
> >
> >> The attached does this experimentally. It looks good... what we lose is
> >> the possibility to
1 - 100 of 144 matches
Mail list logo
