We currently have the following code in GuiApplication::dispatch:
DispatchResult dr;
// redraw the screen at the end (first of the two drawing steps).
// This is done unless explicitly requested otherwise
dr.screenUpdate(Update::FitCursor);
dispatch(cmd, dr);
updateCurrentView(cmd, dr)
I confess I'm lost as to which layouts have been proposed for the converters
prefs pane.
Probably, having a few pics/snapshots comparing the options might be the best
way to gather feedback from others.
Thanks,
T.
On 07/12/2016 21:00, Enrico Forestieri wrote:
On Wed, Dec 07, 2016 at
Am Freitag, 9. Dezember 2016 um 19:21:04, schrieb Kornel Benko
> Am Freitag, 9. Dezember 2016 um 18:48:57, schrieb Enrico Forestieri
>
> > On Fri, Dec 09, 2016 at 02:36:04PM +0100, Kornel Benko wrote:
> > >
> > > Nobody seems interested. Probably no one uses PDF(luatex) as default
> > > output
Am Freitag, 9. Dezember 2016 um 18:48:57, schrieb Enrico Forestieri
> On Fri, Dec 09, 2016 at 02:36:04PM +0100, Kornel Benko wrote:
> >
> > Nobody seems interested. Probably no one uses PDF(luatex) as default output
> > format.
>
> Or, more simply, don't experience the issue. See attached.
>
On Fri, Dec 09, 2016 at 10:39:14AM +0100, Jean-Marc Lasgouttes wrote:
> Le 07/12/2016 à 21:00, Enrico Forestieri a écrit :
> > Why would you think that a proper implementation (if and when that will
> > be performed) would need more space? However, please have a look at the
> > attached patch, whic
On Fri, Dec 09, 2016 at 02:36:04PM +0100, Kornel Benko wrote:
>
> Nobody seems interested. Probably no one uses PDF(luatex) as default output
> format.
Or, more simply, don't experience the issue. See attached.
--
Enrico
Hello,
The subject almost says it all. I am not sure that the pixmap cache (a
different way of painting where the pixmaps corresponding to strings are
remembered) is very useful these days, especially with my caching patch
that also uses QTextLayout objects for painting.
Would somebody obje
Le 09/12/2016 à 16:04, mn a écrit :
Right now I guess there were several reasons we arrived at the current
situation. Either very good or congruent reasons or just by chance.
But I also guess that no-one has tested or adjusted all the color options:
-- for people with (color-)vision abnormalitie
On 09.12.16 13:25, Jean-Marc Lasgouttes wrote:
> Le 09/12/2016 à 12:59, mn a écrit :
>> This setting dwells under a different Settings group named Look&Feel?
>> There I can only change the color of this solid line, not its thickness
>> or position.
>> And in my eyes the line itself is the problem,
Le 07/12/2016 à 16:10, Jean-Marc Lasgouttes a écrit :
Le 07/12/2016 à 12:15, Jean-Marc Lasgouttes a écrit :
I'll post a new version to try soon.
Here is a patch to play with. It is not perfect, but I would be
interested to know whether it improves performance with Qt4.
I have improved a bit
Le 09/12/2016 à 15:37, Tommaso Cucinotta a écrit :
On 09/12/2016 11:34, Jean-Marc Lasgouttes wrote:
Note though
that with my patch we directly draw the cached QTextLayout object.
your patch turns LyX from a snail to a lightning fast editor :-)!
It's a long time I don't have memory of being ab
On 09/12/2016 11:34, Jean-Marc Lasgouttes wrote:
Note though
that with my patch we directly draw the cached QTextLayout object.
your patch turns LyX from a snail to a lightning fast editor :-)!
It's a long time I don't have memory of being able to go through a doc at such
a speed, just keepin
Am Donnerstag, 8. Dezember 2016 um 23:31:48, schrieb Scott Kostyshak
> On Sat, Nov 05, 2016 at 11:40:51AM +0100, Kornel Benko wrote:
> > Try to open attached document.
> > Wait a moment until the preview is done.
> > The formula takes too much space.
>
> I thought someone had responded to this b
Le 09/12/2016 à 12:59, mn a écrit :
This setting dwells under a different Settings group named Look&Feel?
There I can only change the color of this solid line, not its thickness
or position.
And in my eyes the line itself is the problem, not its color.
I understand your arguments, but this is a
On 08.12.16 16:31, Jean-Marc Lasgouttes wrote:
> Le 08/12/2016 à 16:21, mn a écrit :
>> Try to select what comes after the first colon (to the left) up until
>> the second colon in the second line. Or in other words: what is just
>> between those two.
>> The selection will jump to the beginning of
On 08.12.16 16:27, Jean-Marc Lasgouttes wrote:
> Le 08/12/2016 à 16:20, mn a écrit :
>> Yes. But this means I loose the ability to immediately see whether or
>> not this part was correctly assigned to a given language.
>> I think there might be a better solution than to disable _a_ marking
>> compl
Le 08/12/2016 à 00:09, Guenter Milde a écrit :
* consistency: currently, if a user sees a guillemot « on screen, it can be
a literal character or a Quote inset and the LaTeX export can be
"«" or "\guillemotleft" (depending on the "inputencoding")
"<<" (for Quote inset, even if « is support
Le 07/12/2016 à 18:49, Guenter Milde a écrit :
The current behaviour of "insert-quote" LFUN is usually called "smart
quotes". This can be done without Quote insets.
Sure. What the Quote inset brings us, as Juergen pointed out already, is
some semantics. But it is not semantics that we really e
Le 08/12/2016 à 23:18, Tommaso Cucinotta a écrit :
likely with this sequel [1], so the innermost LyX code seems:
lyx::frontend::GuiFontMetrics::breakAt,lyx::Row::Element::breakAt,
lyx::Row::shortenIfNeeded,lyx::TextMetrics::breakRow,lyx::TextMetrics::redoParagraph,
breakAt is the main method f
Le 07/12/2016 à 21:00, Enrico Forestieri a écrit :
Why would you think that a proper implementation (if and when that will
be performed) would need more space? However, please have a look at the
attached patch, which leaves more space to the converters definitions.
No need to revert f0f555b5, as
20 matches
Mail list logo
