Re: [PATCH] Improve the performance of the source panel by using a QTimer (bug #9493)

Guillaume Munch wrote: > require a regeneration if it's the same paragraph. But I might have > misinterpreted. Of course, the generation is only triggered after > the user acts or moves, since the QTimer is non-repeating > (setSingleShot). This is actually what I had in mind, good. Richard Heck w

Re: Lyx slow even with small documents

Liviu Andronic gmail.com> writes: > > On Fri, Jul 17, 2015 at 1:51 AM, Sad Lyxer gmail.com> wrote: > I also use Xfce. I have Sub-pixel order to "RGB" , but encounter none > of the slowness. I also have anti-aliasing enabled, and Hinting to > "Slight". What options do you use? > Same options (

Re: [PATCH] Improve the performance of the source panel by using a QTimer (bug #9493)

On 08/03/2015 09:34 AM, Guillaume Munch wrote: Le 03/08/2015 00:53, Guillaume Munch a écrit : Le 02/08/2015 02:38, Richard Heck a écrit : On 08/01/2015 04:37 PM, Pavel Sanda wrote: Guillaume Munch wrote: +const int long_delay = 400; +const int short_delay = 40; So we will regenerate

Re: [PATCH] Improve the performance of the source panel by using a QTimer (bug #9493)

Le 03/08/2015 00:53, Guillaume Munch a écrit : Le 02/08/2015 02:38, Richard Heck a écrit : On 08/01/2015 04:37 PM, Pavel Sanda wrote: Guillaume Munch wrote: +const int long_delay = 400; +const int short_delay = 40; So we will regenerate paragraph each 40ms no matter whether user typed

Re: [PATCH] \{ and \% now correctly use the selection as their argument instead of erasing it (bug #6466)

Le 31/07/2015 17:05, Guillaume Munch a écrit : \{ and \% now correctly use the selection as their argument instead of erasing it. Solves . Please criticise. If there are no experts of math mode to review the patch, here's to help you check: 1) the change

Re: How to Require a package with options in module?

Liviu Andronic wrote: > I think this should be documented in the Requires (or the Provides) > entry of our docs: both that PackageOptions can be used to define > options, and that it needs to be defined globally. Should I file a > ticket for this? No, I'll do the change right now. Jürgen

Re: How to Require a package with options in module?

On Mon, Aug 3, 2015 at 1:10 PM, Jürgen Spitzmüller wrote: > Liviu Andronic wrote: >> Does this work for Flex insets? It's not documented, and seems to fail here. >> >> With attached module, inserting the Xcolor custom inset I only get >> \usepackage{xcolor} >> >> in Preamble. > > PackageOptions mu

Re: How to Require a package with options in module?

Liviu Andronic wrote: > Does this work for Flex insets? It's not documented, and seems to fail here. > > With attached module, inserting the Xcolor custom inset I only get > \usepackage{xcolor} > > in Preamble. PackageOptions must be defined on a global level. See attached. Jürgen > > Liviu >

Re: How to Require a package with options in module?

On Mon, Aug 3, 2015 at 12:13 PM, Jürgen Spitzmüller wrote: > Am Montag 03 August 2015, 11:49:06 schrieb Liviu Andronic: >> Dear all, >> I'm working on a module that needs to load a package with options. >> What I currently do is: >> Preamble >> \usepackage[usenames,dvipsnames]{xcolor} >> EndPr

Re: How to Require a package with options in module?

Am Montag 03 August 2015, 11:49:06 schrieb Liviu Andronic: > Dear all, > I'm working on a module that needs to load a package with options. > What I currently do is: > Preamble > \usepackage[usenames,dvipsnames]{xcolor} > EndPreamble > > But the above is I suspect not recommended. I can see ho

How to Require a package with options in module?

Dear all, I'm working on a module that needs to load a package with options. What I currently do is: Preamble \usepackage[usenames,dvipsnames]{xcolor} EndPreamble But the above is I suspect not recommended. I can see how I can require the xcolor package via: Requiresxcolor