Am Sonntag, den 15.10.2017, 18:41 -0400 schrieb Richard Heck:
> No, it comes whenever a document contains a BibTeX inset. A better
> patch
> would make it happen
> only when a BibTeX inset was involved. Then the delay is no surprise:
> Of
> course we have to reread
> the files.
The attached patch
Le 16/10/2017 à 05:21, Richard Heck a écrit :
OK, this one is better. I'm not sure I understand why I need to reset
first this way, but it seems I do.
I am not sure what is the difference between the two patches, but it
looks fine.
BTW, is ``setInsetBuffers'' really correct grammatically?
As a side-effect of something else I stumbled across these links to LyX
1999--2003 including a graphical tour of LyX, 1999. Last year (I think)
a binary for LyX 0.10.7 was found and Jean-Marc mentioned in relation to
that the material at http://www.lyx.org/misc/archaeology/. I read
there,
Am Montag, 16. Oktober 2017 um 01:43:48, schrieb Uwe Stöhr
> El 15.10.2017 a las 23:07, Kornel Benko escribió:
>
> > As I think I proposed in the attached part in other mail.
> >
> > Essentially, there is the change of
> > open(file)
> > to
> > codecs.open(file, 'r',
Le 13/10/2017 à 20:38, Richard Heck a écrit :
On 10/12/2017 04:08 PM, Jean-Marc Lasgouttes wrote:
Le 08/10/2017 à 08:56, Jean-Marc Lasgouttes a écrit :
The bisect is probably enough for me to find the bug (he said
confidently).
Here is a tentative patch that I will not be able to test and
Le 15/10/2017 à 10:30, Patrick De Visschere a écrit :
I’ve done some more debugging and I believe I’ve found the Qt code that turns
the background black or white.
Om macos (and probably also on windows) Qt uses a QBackingStore for painting. I
couldn’t find a QPlatformBackingStore for linux so
Le 13/10/2017 à 11:00, Patrick De Visschere a écrit :
But I see your point;
When I remove the line setting WA_OpaquePaintEvent the problem remains but
(most of) the view turns white instead of black;
When I set WA_NoSystemBackground instead the problem remains the same.
When I insert
Andrew Parsloe wrote:
> its 'under the hood' machinery." Last updated, alas, in 2009. I wonder if
> these links should be added?
>
> http://compsoc.man.ac.uk/~moz/www-user/news/archive.php3 (LyX Development
> News archive, 2000/02/17 -- 2003/03/03)
>
>
Hi,
Is the patch for http://www.lyx.org/trac/ticket/10469 already in beta1?
If so, it seems not to work. If not, maybe it can make it to rc1?
Daniel
> On 16 Oct 2017, at 11:41, Jean-Marc Lasgouttes wrote:
>
> Le 13/10/2017 à 11:00, Patrick De Visschere a écrit :
>> But I see your point;
>> When I remove the line setting WA_OpaquePaintEvent the problem remains but
>> (most of) the view turns white instead of black;
>>
Hi,
when I quit lyx 2.0 the app terminates instantaneously,
with current master I have to wait ~3s before the window
disappears (emarasingly slower than launching it - 0.5s).
The time is spent on I/O, not cpu. Anyone can confirm?
Pavel
On 2017-10-14, Scott Kostyshak wrote:
> On Mon, Oct 09, 2017 at 11:56:12AM +, Guenter Milde wrote:
>> The current default behaviour for dash export is a regression on
>> changeset 798ad9755a1ff43a06d2b from 16.06.2007
...
> Note that from what I understand, this is a different topic than
Le 16/10/2017 à 16:08, Pavel Sanda a écrit :
Just trying dirty patch for caching settings inside GuiToolbar::saveSession
instead of creating new local var for each fun entry shows that I get quit
time around 1s.
Quick check shows that most of remaining time is spent in DialogPtr saveSession
loop
Hi
Open the attached file.
First, it seems that the underline for tracked inserts on display
equations is at the correct position now. However, the hook that marks
the end of a paragraph did not move with it.
Second, to the slight paint issues:
- Select the z below the display equation.
Am Montag, 16. Oktober 2017 um 23:28:13, schrieb Uwe Stöhr
> El 16.10.2017 a las 11:17, Kornel Benko escribió:
>
> > Please replace the print statement
> > print(SubstituteDataInLine(line[:-1]))
> > with
> > sys.stdout.write(SubstituteDataInLine(line[:-1])+'\n')
>
>
On 10/16/2017 02:04 AM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 15.10.2017, 18:41 -0400 schrieb Richard Heck:
>> No, it comes whenever a document contains a BibTeX inset. A better
>> patch
>> would make it happen
>> only when a BibTeX inset was involved. Then the delay is no surprise:
>> Of
>>
El 16.10.2017 a las 11:17, Kornel Benko escribió:
Please replace the print statement
print(SubstituteDataInLine(line[:-1]))
with
sys.stdout.write(SubstituteDataInLine(line[:-1])+'\n')
This lead to
"python UnicodeEncodeError: 'charmap' codec can't encode character"
However, I
El 16.10.2017 a las 23:38, Kornel Benko escribió:
This leads to following output for e.g. Additional.lyx
b'#LyX 2.3 created this file. For more info see http://www.lyx.org/'
Hmm, but why do we need to modify the doc files? I mean why can't we
just use them as they are and omit
On Mon, Oct 16, 2017 at 01:09:34PM +, racoon wrote:
> Hi,
>
> Is the patch for http://www.lyx.org/trac/ticket/10469 already in beta1? If
> so, it seems not to work. If not, maybe it can make it to rc1?
The patch is in beta1. If the feature doesn't work, then that means the
fix didn't work
On Mon, Oct 16, 2017 at 03:07:28PM +, Jean-Marc Lasgouttes wrote:
> Le 16/10/2017 à 16:08, Pavel Sanda a écrit :
> > Just trying dirty patch for caching settings inside GuiToolbar::saveSession
> > instead of creating new local var for each fun entry shows that I get quit
> > time around 1s.
>
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-latest-qt5-cmake/435/--
[...truncated 172 lines...]
-- Looking for _getpid - not found
-- Looking for gettext
-- Looking for gettext - found
-- Looking for getuid
-- Looking for getuid - found
--
Le 16/10/2017 à 14:49, Pavel Sanda a écrit :
Hi,
when I quit lyx 2.0 the app terminates instantaneously,
with current master I have to wait ~3s before the window
disappears (emarasingly slower than launching it - 0.5s).
The time is spent on I/O, not cpu. Anyone can confirm?
Qt4 or Qt5?
Pavel Sanda wrote:
> with current master I have to wait ~3s before the window
And the winner for almost all of 3s goes to saveUISettings
and its ToolbarMap saveSession loop.
Each GuiToolbar::saveSession() takes ~80ms, guess what happens
when we call it 40x...
This is qt5 so it might be that lyx
Pavel Sanda wrote:
> Single instance of QSettings in pimp might help this.
Just trying dirty patch for caching settings inside GuiToolbar::saveSession
instead of creating new local var for each fun entry shows that I get quit
time around 1s.
Quick check shows that most of remaining time is spent
Am Montag, den 16.10.2017, 14:58 -0400 schrieb Richard Heck:
> Without profiling, it would be hard to know for sure, but I'd guess
> it
> was worth it. Certainly
> re-reading huge files over a high-latency connection could slow
> things down.
By subjective measure, it is noticeable with several
25 matches
Mail list logo