On 21.03.2012 16:56, Marc de Bruijn wrote:
Jerrylanceboyleat qwest.net writes:
On Jan 3, 2012, at 8:31 AM, Pavel Sanda wrote:
Olivier Ripoll wrote:
I reported the very same sysmptoms a few weeks ago but until now it seems I
was the only person to see it, although I could see it on 2
On 21.03.2012 16:56, Marc de Bruijn wrote:
Jerrylanceboyleat qwest.net writes:
On Jan 3, 2012, at 8:31 AM, Pavel Sanda wrote:
Olivier Ripoll wrote:
I reported the very same sysmptoms a few weeks ago but until now it seems I
was the only person to see it, although I could see it on 2
On 21.03.2012 16:56, Marc de Bruijn wrote:
Jerry writes:
On Jan 3, 2012, at 8:31 AM, Pavel Sanda wrote:
Olivier Ripoll wrote:
I reported the very same sysmptoms a few weeks ago but until now it seems I
was the only person to see it, although I could see it on 2
Jerry lanceboyle at qwest.net writes:
On Jan 3, 2012, at 8:31 AM, Pavel Sanda wrote:
Olivier Ripoll wrote:
I reported the very same sysmptoms a few weeks ago but until now it seems
I
was the only person to see it, although I could see it on 2 machines
(different OS versions of
Jerry lanceboyle at qwest.net writes:
On Jan 3, 2012, at 8:31 AM, Pavel Sanda wrote:
Olivier Ripoll wrote:
I reported the very same sysmptoms a few weeks ago but until now it seems
I
was the only person to see it, although I could see it on 2 machines
(different OS versions of
Jerry qwest.net> writes:
> On Jan 3, 2012, at 8:31 AM, Pavel Sanda wrote:
>
> > Olivier Ripoll wrote:
> >> I reported the very same sysmptoms a few weeks ago but until now it seems
> >> I
> >> was the only person to see it, although I could see it on 2 machines
> >> (different OS versions of
It looks like it's about time to wrap up this thread. It has been a good
exchange and I believe that the developers have been helpful and suitably
notified. If someone thinks it is better to file a formal bug report, please
let me know.
I will summarize for myself by saying that, even though I
Am 10.01.2012 um 00:28 schrieb Jerry:
It looks like it's about time to wrap up this thread.
It has been a good exchange and I believe that the developers have been
helpful and suitably notified.
If someone thinks it is better to file a formal bug report, please let me
know.
I think it's
It looks like it's about time to wrap up this thread. It has been a good
exchange and I believe that the developers have been helpful and suitably
notified. If someone thinks it is better to file a formal bug report, please
let me know.
I will summarize for myself by saying that, even though I
Am 10.01.2012 um 00:28 schrieb Jerry:
It looks like it's about time to wrap up this thread.
It has been a good exchange and I believe that the developers have been
helpful and suitably notified.
If someone thinks it is better to file a formal bug report, please let me
know.
I think it's
It looks like it's about time to wrap up this thread. It has been a good
exchange and I believe that the developers have been helpful and suitably
notified. If someone thinks it is better to file a formal bug report, please
let me know.
I will summarize for myself by saying that, even though I
Am 10.01.2012 um 00:28 schrieb Jerry:
> It looks like it's about time to wrap up this thread.
> It has been a good exchange and I believe that the developers have been
> helpful and suitably notified.
> If someone thinks it is better to file a formal bug report, please let me
> know.
I think
On Thu, Jan 05, 2012 at 02:17:29PM +0100, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
please...
On Thu, Jan 05, 2012 at 02:17:29PM +0100, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
please...
On Thu, Jan 05, 2012 at 02:17:29PM +0100, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
> > Le 05/01/2012 02:40, André Pönitz a écrit :
> >> The main performance problems I have seesn so far are due to an abuse of
> >> the toolkit, not caused _by_ the toolkit (except for the remote raster
>
>
Hi Jerry,
I confirm that I get 89% when I am over a dense text/math region and
scrolling becomes slightly slower, and jumps more. In my case, I consider
this as a low inconvenience, since I can perfectly see and read the text.
I agree that with Lyx, scrolling under OSX is not as fluid as in other
Hi Jerry,
I confirm that I get 89% when I am over a dense text/math region and
scrolling becomes slightly slower, and jumps more. In my case, I consider
this as a low inconvenience, since I can perfectly see and read the text.
I agree that with Lyx, scrolling under OSX is not as fluid as in other
Hi Jerry,
I confirm that I get 89% when I am over a dense text/math region and
scrolling becomes slightly slower, and jumps more. In my case, I consider
this as a low inconvenience, since I can perfectly see and read the text.
I agree that with Lyx, scrolling under OSX is not as fluid as in other
On 05.01.2012 19:14, André Pönitz wrote:
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file ~/Library/Application
On Jan 6, 2012, at 1:47 AM, Olivier Ripoll wrote:
For the sake of completness, I have to say I now notice LyX taking 50% CPU in
all versions while scrolling fast, with I did not remember seeing with 2.0.1
before (perhaps I was using another document and I was scrolling on smaller
areas
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak to 80%
for very short moments, but the rest of the time, it takes around 30% (so
15% since I have two processors). My processors remain globally inactive at
60% even if I am compiling Wine in MacPorts in the same time and listening
Le 06/01/2012 09:47, Olivier Ripoll a écrit :
- 2.0.2 pristine jumps in 2 to 3 steps (text and scrollbar): top of
the document, sometimes an intermediate step, and bottom of the document.
* Adding \use_pixmap_cache and setting to false or true has no effect
* Adding \force_paint_single_char,
On 06/01/2012 12:02, Jean-Marc Lasgouttes wrote:
Le 06/01/2012 09:47, Olivier Ripoll a écrit :
- 2.0.2 pristine jumps in 2 to 3 steps (text and scrollbar): top of
the document, sometimes an intermediate step, and bottom of the document.
* Adding \use_pixmap_cache and setting to false or true
Le 06/01/2012 21:12, Abdelrazak Younes a écrit :
You are mixing up \use_qimage and \use_pixmap_cache. \use_pixmap_cache
is an old setting that I created to speed up text rendering on MAC. But
apparently MAC users cannot bare the on screen side effect so we can get
rid of this in trunk maybe.
On Jan 6, 2012, at 3:29 AM, Murat Yildizoglu wrote:
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak to 80% for
very short moments, but the rest of the time, it takes around 30% (so 15%
since I have two processors). My processors remain globally inactive at 60%
even if I
On Friday, January 06, 2012 04:39:07 PM Jerry wrote:
On Jan 6, 2012, at 3:29 AM, Murat Yildizoglu wrote:
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak
to 80% for very short moments, but the rest of the time, it
takes around 30% (so 15% since I have two processors). My
On 05.01.2012 19:14, André Pönitz wrote:
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file ~/Library/Application
On Jan 6, 2012, at 1:47 AM, Olivier Ripoll wrote:
For the sake of completness, I have to say I now notice LyX taking 50% CPU in
all versions while scrolling fast, with I did not remember seeing with 2.0.1
before (perhaps I was using another document and I was scrolling on smaller
areas
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak to 80%
for very short moments, but the rest of the time, it takes around 30% (so
15% since I have two processors). My processors remain globally inactive at
60% even if I am compiling Wine in MacPorts in the same time and listening
Le 06/01/2012 09:47, Olivier Ripoll a écrit :
- 2.0.2 pristine jumps in 2 to 3 steps (text and scrollbar): top of
the document, sometimes an intermediate step, and bottom of the document.
* Adding \use_pixmap_cache and setting to false or true has no effect
* Adding \force_paint_single_char,
On 06/01/2012 12:02, Jean-Marc Lasgouttes wrote:
Le 06/01/2012 09:47, Olivier Ripoll a écrit :
- 2.0.2 pristine jumps in 2 to 3 steps (text and scrollbar): top of
the document, sometimes an intermediate step, and bottom of the document.
* Adding \use_pixmap_cache and setting to false or true
Le 06/01/2012 21:12, Abdelrazak Younes a écrit :
You are mixing up \use_qimage and \use_pixmap_cache. \use_pixmap_cache
is an old setting that I created to speed up text rendering on MAC. But
apparently MAC users cannot bare the on screen side effect so we can get
rid of this in trunk maybe.
On Jan 6, 2012, at 3:29 AM, Murat Yildizoglu wrote:
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak to 80% for
very short moments, but the rest of the time, it takes around 30% (so 15%
since I have two processors). My processors remain globally inactive at 60%
even if I
On Friday, January 06, 2012 04:39:07 PM Jerry wrote:
On Jan 6, 2012, at 3:29 AM, Murat Yildizoglu wrote:
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak
to 80% for very short moments, but the rest of the time, it
takes around 30% (so 15% since I have two processors). My
On 05.01.2012 19:14, André Pönitz wrote:
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file "~/Library/Application
On Jan 6, 2012, at 1:47 AM, Olivier Ripoll wrote:
> For the sake of completness, I have to say I now notice LyX taking 50% CPU in
> all versions while scrolling fast, with I did not remember seeing with 2.0.1
> before (perhaps I was using another document and I was scrolling on smaller
>
In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak to 80%
for very short moments, but the rest of the time, it takes around 30% (so
15% since I have two processors). My processors remain globally inactive at
60% even if I am compiling Wine in MacPorts in the same time and listening
Le 06/01/2012 09:47, Olivier Ripoll a écrit :
- 2.0.2 "pristine" jumps in 2 to 3 steps (text and scrollbar): top of
the document, sometimes an intermediate step, and bottom of the document.
* Adding "\use_pixmap_cache" and setting to false or true has no effect
* Adding "
On 06/01/2012 12:02, Jean-Marc Lasgouttes wrote:
Le 06/01/2012 09:47, Olivier Ripoll a écrit :
- 2.0.2 "pristine" jumps in 2 to 3 steps (text and scrollbar): top of
the document, sometimes an intermediate step, and bottom of the document.
* Adding "\use_pixmap_cache" and setting to false or
Le 06/01/2012 21:12, Abdelrazak Younes a écrit :
You are mixing up \use_qimage and \use_pixmap_cache. \use_pixmap_cache
is an old setting that I created to speed up text rendering on MAC. But
apparently MAC users cannot bare the on screen side effect so we can get
rid of this in trunk maybe.
On Jan 6, 2012, at 3:29 AM, Murat Yildizoglu wrote:
> In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak to 80% for
> very short moments, but the rest of the time, it takes around 30% (so 15%
> since I have two processors). My processors remain globally inactive at 60%
> even
On Friday, January 06, 2012 04:39:07 PM Jerry wrote:
> On Jan 6, 2012, at 3:29 AM, Murat Yildizoglu wrote:
> > In my case, scrolling the User Guide, I can see Lyx 2.0.2 to peak
> > to 80% for very short moments, but the rest of the time, it
> > takes around 30% (so 15% since I have two
If the issue I reported is the same (it seems the definition of slow
scrolling can cover different behaviours), it happens also on Windows 7.
BR,
O.
On 04.01.2012 10:03, Olivier Ripoll wrote:
On 03.01.2012 21:36, Stephan Witt wrote:
Am 03.01.2012 um 17:15 schrieb Olivier Ripoll:
[...]
Hi,
I'm almost sure it depends on Qt-Version.
IIRC, I checked the file properties of QtCore4 and QtGUI4 dlls and both
files were version 4.7.4.0 in LyX
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to file a bug report
for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll see
several names of LyX developers (not exhautively: Pavel Sanda, Richard
on OSX 10.7.x?
No—I'm on OS X 10.6.8.
Jerry
James
If the issue I reported is the same (it seems the definition of slow
scrolling can cover different behaviours), it happens also on Windows 7.
BR,
O.
Interesting. So now we have reports of slow scrolling problems on multiple
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
painter problem perhaps). Just start at RowPainter::paintChars() and
walk down through all the mess _before_
On Jan 4, 2012, at 9:13 PM, Jerry wrote:
On Jan 4, 2012, at 3:03 PM, Stephan Witt wrote:
I've prepared a LyX-package with Qt-4.8.0 and the upload is here:
http://dl.dropbox.com/u/27842660/LyX-2.1.0svn%2Bqt4.8.0-cocoa.dmg
and there were no problems with that either.
So it appears that this issue is unique to LyX on OSX
10.7.x?
No—I'm on OS X 10.6.8. Jerry
James
If the issue I reported is the same (it seems the definition of
slow scrolling can cover different behaviours), it happens also
on Windows 7.
BR
it appears that this issue is unique to LyX on OSX 10.7.x?
No—I'm on OS X 10.6.8.
Jerry
James
If the issue I reported is the same (it seems the definition of slow
scrolling can cover different behaviours), it happens also on Windows 7.
BR,
O.
Interesting. So now we have reports
Am 05.01.2012 um 10:02 schrieb Jerry:
On Jan 4, 2012, at 9:13 PM, Jerry wrote:
On Jan 4, 2012, at 3:03 PM, Stephan Witt wrote:
I've prepared a LyX-package with Qt-4.8.0 and the upload is here:
http://dl.dropbox.com/u/27842660/LyX-2.1.0svn%2Bqt4.8.0-cocoa.dmg
Le 05/01/2012 09:40, Olivier Ripoll a écrit :
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to file a
bug report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll see
several names of LyX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/01/12 10:58, Jean-Marc Lasgouttes wrote:
Le 05/01/2012 09:40, Olivier Ripoll a écrit :
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to
file a bug report for the slow scrolling problem?
Jerry
report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll
see several names of LyX developers (not exhautively: Pavel
Sanda, Richard Heck, Jean-Marc Lasgouttes, André Pönitz)
The problem is that we have yet to pinpoint the root cause. I
Jean-Marc Lasgouttes wrote:
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
please... there were many cases we have no clue where the problem is.
it can
Pavel Sanda wrote:
whats really funny is that it seems that i'm able to repeat it quite more
reliably
in screnario first instance is \use_qimage true and second false.
sometimes it doesn't happen in this scenario and it never happened (up to now)
vice versa in false-true scenario. dont ask
report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll
see several names of LyX developers (not exhautively: Pavel
Sanda, Richard Heck, Jean-Marc Lasgouttes, André Pönitz)
The problem is that we have yet to pinpoint the root cause. I see
two
On 05.01.2012 10:13, Rainer M Krug wrote:
-BEGIN PGP SIGNED MESSAGE-
[...]
If the issue I reported is the same (it seems the definition of
slow scrolling can cover different behaviours), it happens also
on Windows 7.
BR,
O.
Interesting. So now we have reports of slow scrolling
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file ~/Library/Application
Support/LyX-2.0/preferences.
(Broken cursor placement for
If the issue I reported is the same (it seems the definition of slow
scrolling can cover different behaviours), it happens also on Windows 7.
BR,
O.
On 04.01.2012 10:03, Olivier Ripoll wrote:
On 03.01.2012 21:36, Stephan Witt wrote:
Am 03.01.2012 um 17:15 schrieb Olivier Ripoll:
[...]
Hi,
I'm almost sure it depends on Qt-Version.
IIRC, I checked the file properties of QtCore4 and QtGUI4 dlls and both
files were version 4.7.4.0 in LyX
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to file a bug report
for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll see
several names of LyX developers (not exhautively: Pavel Sanda, Richard
on OSX 10.7.x?
No—I'm on OS X 10.6.8.
Jerry
James
If the issue I reported is the same (it seems the definition of slow
scrolling can cover different behaviours), it happens also on Windows 7.
BR,
O.
Interesting. So now we have reports of slow scrolling problems on multiple
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
painter problem perhaps). Just start at RowPainter::paintChars() and
walk down through all the mess _before_
On Jan 4, 2012, at 9:13 PM, Jerry wrote:
On Jan 4, 2012, at 3:03 PM, Stephan Witt wrote:
I've prepared a LyX-package with Qt-4.8.0 and the upload is here:
http://dl.dropbox.com/u/27842660/LyX-2.1.0svn%2Bqt4.8.0-cocoa.dmg
and there were no problems with that either.
So it appears that this issue is unique to LyX on OSX
10.7.x?
No—I'm on OS X 10.6.8. Jerry
James
If the issue I reported is the same (it seems the definition of
slow scrolling can cover different behaviours), it happens also
on Windows 7.
BR
it appears that this issue is unique to LyX on OSX 10.7.x?
No—I'm on OS X 10.6.8.
Jerry
James
If the issue I reported is the same (it seems the definition of slow
scrolling can cover different behaviours), it happens also on Windows 7.
BR,
O.
Interesting. So now we have reports
Am 05.01.2012 um 10:02 schrieb Jerry:
On Jan 4, 2012, at 9:13 PM, Jerry wrote:
On Jan 4, 2012, at 3:03 PM, Stephan Witt wrote:
I've prepared a LyX-package with Qt-4.8.0 and the upload is here:
http://dl.dropbox.com/u/27842660/LyX-2.1.0svn%2Bqt4.8.0-cocoa.dmg
Le 05/01/2012 09:40, Olivier Ripoll a écrit :
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to file a
bug report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll see
several names of LyX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/01/12 10:58, Jean-Marc Lasgouttes wrote:
Le 05/01/2012 09:40, Olivier Ripoll a écrit :
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to
file a bug report for the slow scrolling problem?
Jerry
report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll
see several names of LyX developers (not exhautively: Pavel
Sanda, Richard Heck, Jean-Marc Lasgouttes, André Pönitz)
The problem is that we have yet to pinpoint the root cause. I
Jean-Marc Lasgouttes wrote:
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
please... there were many cases we have no clue where the problem is.
it can
Pavel Sanda wrote:
whats really funny is that it seems that i'm able to repeat it quite more
reliably
in screnario first instance is \use_qimage true and second false.
sometimes it doesn't happen in this scenario and it never happened (up to now)
vice versa in false-true scenario. dont ask
report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll
see several names of LyX developers (not exhautively: Pavel
Sanda, Richard Heck, Jean-Marc Lasgouttes, André Pönitz)
The problem is that we have yet to pinpoint the root cause. I see
two
On 05.01.2012 10:13, Rainer M Krug wrote:
-BEGIN PGP SIGNED MESSAGE-
[...]
If the issue I reported is the same (it seems the definition of
slow scrolling can cover different behaviours), it happens also
on Windows 7.
BR,
O.
Interesting. So now we have reports of slow scrolling
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file ~/Library/Application
Support/LyX-2.0/preferences.
(Broken cursor placement for
If the issue I reported is the same (it seems the definition of "slow
scrolling" can cover different behaviours), it happens also on Windows 7.
BR,
O.
On 04.01.2012 10:03, Olivier Ripoll wrote:
On 03.01.2012 21:36, Stephan Witt wrote:
Am 03.01.2012 um 17:15 schrieb Olivier Ripoll:
[...]
Hi,
I'm almost sure it depends on Qt-Version.
IIRC, I checked the file properties of QtCore4 and QtGUI4 dlls and both
files were version 4.7.4.0 in LyX
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to file a bug report
for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll see
several names of LyX developers (not exhautively: Pavel Sanda, Richard
LyX 2.0.2 on 10.6.8 and
>>> there were no problems with that either.
>>>
>>> So it appears that this issue is unique to LyX on OSX 10.7.x?
>>
>> No—I'm on OS X 10.6.8.
>> Jerry
>>>
>>> James
>>
>
> If the issue I reported is
Le 05/01/2012 02:40, André Pönitz a écrit :
The main performance problems I have seesn so far are due to an abuse of
the toolkit, not caused _by_ the toolkit (except for the remote raster
painter problem perhaps). Just start at RowPainter::paintChars() and
walk down through all the mess _before_
On Jan 4, 2012, at 9:13 PM, Jerry wrote:
>
> On Jan 4, 2012, at 3:03 PM, Stephan Witt wrote:
>
>> I've prepared a LyX-package with Qt-4.8.0 and the upload is here:
>>
>> http://dl.dropbox.com/u/27842660/LyX-2.1.0svn%2Bqt4.8.0-cocoa.dmg
>>
ique to LyX on OSX
>>>> 10.7.x?
>>>
>>> No—I'm on OS X 10.6.8. Jerry
>>>>
>>>> James
>>>
>>
>> If the issue I reported is the same (it seems the definition of
>> "slow scrolling" can cover different behav
ther Mac system running OSX 10.6.8 and LyX
>>>> 2.0.0. No problems there. I then updated to LyX 2.0.2 on 10.6.8 and
>>>> there were no problems with that either.
>>>>
>>>> So it appears that this issue is unique to LyX on OSX 10.7.x?
>>>
>>>
Am 05.01.2012 um 10:02 schrieb Jerry:
>
> On Jan 4, 2012, at 9:13 PM, Jerry wrote:
>
>>
>> On Jan 4, 2012, at 3:03 PM, Stephan Witt wrote:
>>
>>> I've prepared a LyX-package with Qt-4.8.0 and the upload is here:
>>>
>>> http://dl.dropbox.com/u/27842660/LyX-2.1.0svn%2Bqt4.8.0-cocoa.dmg
>>>
Le 05/01/2012 09:40, Olivier Ripoll a écrit :
On 05.01.2012 05:16, Jerry wrote:
Do the developers monitor this list? Or does someone need to file a
bug report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll see
several names of LyX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/01/12 10:58, Jean-Marc Lasgouttes wrote:
> Le 05/01/2012 09:40, Olivier Ripoll a écrit :
>> On 05.01.2012 05:16, Jerry wrote:
>>> Do the developers monitor this list? Or does someone need to
>>> file a bug report for
opers monitor this list? Or does someone need to
> >>> file a bug report for the slow scrolling problem?
> >>>
> >>> Jerry
> >>
> >> Yes, they are looking at it. If you look at the thread, you'll
> >> see several names of LyX develope
Jean-Marc Lasgouttes wrote:
> Le 05/01/2012 02:40, André Pönitz a écrit :
>> The main performance problems I have seesn so far are due to an abuse of
>> the toolkit, not caused _by_ the toolkit (except for the remote raster
please... there were many cases we have no clue where the problem is.
it
Pavel Sanda wrote:
> whats really funny is that it seems that i'm able to repeat it quite more
> reliably
> in screnario first instance is \use_qimage true and second false.
> sometimes it doesn't happen in this scenario and it never happened (up to now)
> vice versa in false->true scenario. dont
report for the slow scrolling problem?
Jerry
Yes, they are looking at it. If you look at the thread, you'll
see several names of LyX developers (not exhautively: Pavel
Sanda, Richard Heck, Jean-Marc Lasgouttes, André Pönitz)
The problem is that we have yet to pinpoint the root cause. I see
two
On 05.01.2012 10:13, Rainer M Krug wrote:
-BEGIN PGP SIGNED MESSAGE-
[...]
If the issue I reported is the same (it seems the definition of
"slow scrolling" can cover different behaviours), it happens also
on Windows 7.
BR,
O.
Interesting. So now we have repor
On Thu, Jan 05, 2012 at 09:28:58AM +0100, Olivier Ripoll wrote:
> >>To check if this is the culprit one may add the following line to your
> >>preferences file:
> >>\force_paint_single_char false
> >>On a Mac this is the file "~/Library/Application
> >>Support/LyX-2.0/preferences".
> >>(Broken
On Jan 3, 2012, at 11:36 PM, Stephan Witt wrote:
Am 04.01.2012 um 01:28 schrieb Jerry:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file ~/Library/Application
Support/LyX-2.0/preferences.
On 03.01.2012 21:36, Stephan Witt wrote:
Am 03.01.2012 um 17:15 schrieb Olivier Ripoll:
[...]
Hi,
I'm almost sure it depends on Qt-Version.
IIRC, I checked the file properties of QtCore4 and QtGUI4 dlls and both
files were version 4.7.4.0 in LyX 2.0.1 and 2.0.2.
But perhaps my memories
Am 04.01.2012 um 09:41 schrieb Jerry:
On Jan 3, 2012, at 11:36 PM, Stephan Witt wrote:
Am 04.01.2012 um 01:28 schrieb Jerry:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file
Am 04.01.2012 um 07:36 schrieb Stephan Witt:
Am 04.01.2012 um 01:28 schrieb Jerry:
To check if this is the culprit one may add the following line to your
preferences file:
\force_paint_single_char false
On a Mac this is the file ~/Library/Application
Support/LyX-2.0/preferences.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/01/12 12:44, Stephan Witt wrote:
Am 04.01.2012 um 07:36 schrieb Stephan Witt:
Am 04.01.2012 um 01:28 schrieb Jerry:
To check if this is the culprit one may add the following
line to your preferences file: \force_paint_single_char
false
On 01/04/2012 07:34 AM, Rainer M Krug wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/01/12 12:44, Stephan Witt wrote:
Am 04.01.2012 um 07:36 schrieb Stephan Witt:
Am 04.01.2012 um 01:28 schrieb Jerry:
To check if this is the culprit one may add the following
line to your
Le 04/01/2012 12:44, Stephan Witt a écrit :
And this is the result:
I've opened the users guide and started to page down unto the end once.
* 2.0.0, 4.6.3 Carbon, 22 Sekunden
* 2.0.0, 4.6.3 Cocoa, 23 Sekunden
* 2.0.2, 4.7.2 Cocoa, 20 Sekunden
* 2.1svn, 4.8.0 Cocoa, 23 Sekunden
* 2.1svn, 4.8.0
1 - 100 of 201 matches
Mail list logo
