Yes, probably you can change that system- or user-wide somewhere. But
it's not obvious: I just tried to find out for a few minutes and didn't
find any GUI for that.
>>> Qt4Config>Interface>Wheel Scroll Lines
>>
>> Either it does not exist on mac or I don't have it installed...
Stefan Schimanski wrote:
Yes, probably you can change that system- or user-wide somewhere.
But it's not obvious: I just tried to find out for a few minutes and
didn't find any GUI for that.
Qt4Config>Interface>Wheel Scroll Lines
Either it does not exist on mac or I don't have it installed..
Yes, probably you can change that system- or user-wide somewhere.
But it's not obvious: I just tried to find out for a few minutes
and didn't find any GUI for that.
Qt4Config>Interface>Wheel Scroll Lines
Either it does not exist on mac or I don't have it installed...
Stefan
Stefan Schimanski wrote:
Am 30.01.2008 um 18:44 schrieb Abdelrazak Younes:
Stefan Schimanski wrote:
Hi!
Attached is a patch which adds a setting to change the scrolling
speed of the mouse wheel.
I always had the feeling that this is far to fast in LyX (compared
to other applications). This
Am 30.01.2008 um 18:44 schrieb Abdelrazak Younes:
Stefan Schimanski wrote:
Hi!
Attached is a patch which adds a setting to change the scrolling
speed of the mouse wheel.
I always had the feeling that this is far to fast in LyX (compared
to other applications). This might come from the Qt
Stefan Schimanski wrote:
Hi!
Attached is a patch which adds a setting to change the scrolling speed
of the mouse wheel.
I always had the feeling that this is far to fast in LyX (compared to
other applications). This might come from the Qt wheelScrollLines
setting which is set to 3 here for
Hi!
Attached is a patch which adds a setting to change the scrolling speed
of the mouse wheel.
I always had the feeling that this is far to fast in LyX (compared to
other applications). This might come from the Qt wheelScrollLines
setting which is set to 3 here for all Mac Qt
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Andre Poenitz wrote:
On Mon, Oct 23, 2006 at 06:33:16PM +0200, Abdelrazak Younes wrote:
Hi Andre,
Before Denmark, the UserGuide PageDown test was at 18 seconds. Now it
is at 25 seconds. I hope you have some more code in store for speed ;-)
?
The
Abdelrazak Younes wrote:
> Andre Poenitz wrote:
>> On Mon, Oct 23, 2006 at 06:33:16PM +0200, Abdelrazak Younes wrote:
>>> Hi Andre,
>>>
>>> Before Denmark, the UserGuide PageDown test was at 18 seconds. Now it
>>> is at 25 seconds. I hope you have some more code in store for speed ;-)
>>
>> ?
>
>
Andre Poenitz wrote:
On Mon, Oct 23, 2006 at 06:33:16PM +0200, Abdelrazak Younes wrote:
Hi Andre,
Before Denmark, the UserGuide PageDown test was at 18 seconds. Now it is
at 25 seconds. I hope you have some more code in store for speed ;-)
?
The decrease in speed was due to the new black s
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Tue, Oct 24, 2006 at 10:01:43AM +0200, Juergen Vigna wrote:
>> Hi Abdel,
>>
>> as much as I know before we started on fixing bugs there I was not
>> able to scroll trough the UserGuide without hitting an Assert ;)
>>
>> I think
On Tue, Oct 24, 2006 at 10:01:43AM +0200, Juergen Vigna wrote:
> Hi Abdel,
>
> as much as I know before we started on fixing bugs there I was not able
> to scroll trough the UserGuide without hitting an Assert ;)
>
> I think that this is due to the "more" metrics calculations we have to do
> in o
On Mon, Oct 23, 2006 at 06:33:16PM +0200, Abdelrazak Younes wrote:
> Hi Andre,
>
> Before Denmark, the UserGuide PageDown test was at 18 seconds. Now it is
> at 25 seconds. I hope you have some more code in store for speed ;-)
?
Andre'
On Mon, Oct 23, 2006 at 07:12:13PM +0200, Asger Ottar Alstrup wrote:
> Finally, it could be André's new rendering scheme which is slower on
> your setup.
Unlikely. Maybe not much of an inprovemnt, but certanily not slower.
The wrong cursor size is my fault though..
Andre'
On Oct 25, 2006, at 11:01 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
On Oct 24, 2006, at 3:07 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Scrolling through the User's Guide (with math preview
turned
Bennett> off) takes about 70 seco
Bennett Helm wrote:
On Oct 24, 2006, at 3:07 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm
<[EMAIL PROTECTED]> writes:
Bennett> Scrolling through the User's Guide (with math preview turned
Bennett> off) takes about 70 seconds.
And does math preview improve things?
Math preview
On Oct 24, 2006, at 3:07 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Scrolling through the User's Guide (with math preview turned
Bennett> off) takes about 70 seconds.
And does math preview improve things?
Math preview doesn't seem to work
On Wed, Oct 25, 2006 at 10:19:12AM +0200, Asger Ottar Alstrup wrote:
> Abdelrazak Younes wrote:
> >The wikipedia link that Martin's provided indicated that this is not
> >about anti-aliasing on/off but about different methods for anti-aliasing
> >(sharpness versus contrast). Could you please chec
Abdelrazak Younes wrote:
The wikipedia link that Martin's provided indicated that this is not
about anti-aliasing on/off but about different methods for anti-aliasing
(sharpness versus contrast). Could you please check that before we
settle on any solution?
It is about anti-aliasing. You can
Asger Ottar Alstrup wrote:
Martin Vermeer wrote:
By the way, I cannot see any text rendering difference between the
two version. Looks to me that the text is anti-aliased in both cases.
Looks to me that this setRenderHint() is just a helper for something
else.
In windows, you can turn off an
Martin Vermeer wrote:
By the way, I cannot see any text rendering difference between the two
version. Looks to me that the text is anti-aliased in both cases. Looks
to me that this setRenderHint() is just a helper for something else.
In windows, you can turn off anti-aliasing. The Qt setRender
On Tue, Oct 24, 2006 at 05:53:05PM +0200, Abdelrazak Younes wrote:
> Asger Ottar Alstrup wrote:
...
> By the way, I cannot see any text rendering difference between the two
> version. Looks to me that the text is anti-aliased in both cases. Looks
> to me that this setRenderHint() is just a hel
Abdelrazak Younes wrote:
One thing that is maybe impacting the scrolling speed is the bogus
cursor. I guess painting a big square square in addition does not help.
Indeed... Without it, the UserGuide test is now at 15 seconds! That's
better than ever!
By the way, you will nee
::TextAntialiasing)
- 22-23 s without.
So I guess this setRenderHint() is not guilty of anything. If anything,
I would say the contrary.
One thing that is maybe impacting the scrolling speed is the bogus
cursor. I guess painting a big square square in addition does not help.
Indeed... Without
-23 s without.
So I guess this setRenderHint() is not guilty of anything. If anything,
I would say the contrary.
One thing that is maybe impacting the scrolling speed is the bogus
cursor. I guess painting a big square square in addition does not help.
By the way, I cannot see any text rendering
Jean-Marc Lasgouttes wrote:
> http://www.aa.org/en_information_aa.cfm
I see, thanks. That's indeed something different than AAA (and the LyX
meetings, as far as I can see).
Jürgen
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> What's AA? I only know the AAA meetings.
http://www.aa.org/en_information_aa.cfm
JMarc
José Matos wrote:
> It will be fun to have at one of the meetings and say "Hello, my name is
> Jürgen S. and I am a lyx developer".
I'll noted that sentence for the case I'll enter reality ;-)
> That will make the meeting look like an AA meeting, I can only laugh with
> such analogy. ;-)
Wha
> "Asger" == Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
Asger> It might very well be the anti-aliasing we enabled. Can you try
Asger> to revert that? Just search for setRenderHint and comment those
Asger> guys out. If this is the case, I guess anti-aliasing should be
Asger> optional throu
On Tuesday 24 October 2006 9:53 am, Juergen Spitzmueller wrote:
> To clarify, Jürgen V. is the "real" Jürgen, I'm just a parvenu.
It will be fun to have at one of the meetings and say "Hello, my name is
Jürgen S. and I am a lyx developer".
That will make the meeting look like an AA meeting,
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Abdelrazak Younes wrote:
>> PS: I didn't know that there was two Jurgen in this list. I was
>> confused by the fact Jurgen (S) criticized the Denmark people while
>> he was part of them :-)
Juergen> To clarify, Jürgen V.
Abdelrazak Younes wrote:
> PS: I didn't know that there was two Jurgen in this list. I was confused
> by the fact Jurgen (S) criticized the Denmark people while he was part
> of them :-)
To clarify, Jürgen V. is the "real" Jürgen, I'm just a parvenu.
Jürgen
On Tue, 2006-10-24 at 10:03 +0200, Juergen Vigna wrote:
>
> Asger Ottar Alstrup wrote:
> > One conclusion is clear: The only sure way to get substantially faster
> > rendering is to draw less on the screen, as discussed earlier today,
> > either by introducing the old singlePar optimisation, or
Juergen Vigna wrote:
Hi Abdel,
as much as I know before we started on fixing bugs there I was not able
to scroll trough the UserGuide without hitting an Assert ;)
But this has nothing to do with speed ;-)
More seriously, I was of course speaking about a built that was before
the scrolling br
Asger Ottar Alstrup wrote:
One conclusion is clear: The only sure way to get substantially faster
rendering is to draw less on the screen, as discussed earlier today,
either by introducing the old singlePar optimisation, or do some
drawing-caching scheme.
I'm of the opinion that in 1.6 we s
Hi Abdel,
as much as I know before we started on fixing bugs there I was not able
to scroll trough the UserGuide without hitting an Assert ;)
I think that this is due to the "more" metrics calculations we have to do
in order to fix all that scrolling bugs and with it the removal of the
nullpaint
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> Scrolling through the User's Guide (with math preview turned
Bennett> off) takes about 70 seconds.
And does math preview improve things?
JMarc
On Oct 23, 2006, at 1:12 PM, Asger Ottar Alstrup wrote:
Abdelrazak Younes wrote:
Before Denmark, the UserGuide PageDown test was at 18 seconds. Now
it is at 25 seconds. I hope you have some more code in store for
speed ;-)
...
Also, we'd like some MacOSX users to try the new code before w
Abdelrazak Younes wrote:
Before Denmark, the UserGuide PageDown test was at 18 seconds. Now it is
at 25 seconds. I hope you have some more code in store for speed ;-)
It might very well be the anti-aliasing we enabled. Can you try to
revert that? Just search for setRenderHint and comment those
Hi Andre,
Before Denmark, the UserGuide PageDown test was at 18 seconds. Now it is
at 25 seconds. I hope you have some more code in store for speed ;-)
Abdel.
On Sun, Jul 23, 2006 at 10:43:15AM +0200, Georg Baum wrote:
> Am Sonntag, 23. Juli 2006 03:22 schrieb Enrico Forestieri:
>
> > So, what is doing LyX with equations to justify such a slow down?
>
> Do you use math macros? If yes, do you see a difference if you remove them?
> Maybe this is relate
Am Sonntag, 23. Juli 2006 03:22 schrieb Enrico Forestieri:
> So, what is doing LyX with equations to justify such a slow down?
Do you use math macros? If yes, do you see a difference if you remove them?
Maybe this is related to http://bugzilla.lyx.org/show_bug.cgi?id=2452
Georg
Scrolling on Windows using qt/win is a real pain. I just discovered
that if instant preview for math is turned on, then the scrolling
speed is about the same as with qt/x11.
No matter how fast I am able to roll the mouse wheel, LyX always
catches up, which is not the case when instant preview is
43 matches
Mail list logo
