On Tue, Sep 17, 2024 at 04:29:38PM +0200, Jürgen Spitzmüller wrote:
> Am Dienstag, dem 17.09.2024 um 15:03 +0200 schrieb Pavel Sanda:
> > - open some structured text (eg any manual)
> > - set tree depth to some higher level (eg 2) by the slider in toc
> > dialog
> > - go inside any section, highlig
Am Dienstag, dem 17.09.2024 um 15:03 +0200 schrieb Pavel Sanda:
> - open some structured text (eg any manual)
> - set tree depth to some higher level (eg 2) by the slider in toc
> dialog
> - go inside any section, highlight the text and remove/replace it
> - the outliner tree depth gets reset to 0
Hi,
- open some structured text (eg any manual)
- set tree depth to some higher level (eg 2) by the slider in toc dialog
- go inside any section, highlight the text and remove/replace it
- the outliner tree depth gets reset to 0 irrespective of the slider position
Works fine in 2.3; bisect in 2.4
On Fri, Jul 26, 2024 at 10:17:06AM GMT, Jean-Marc Lasgouttes wrote:
> But is it faster when the mouse is below the window, then?
Ah, sorry I wasn't clear. The window is maximized, but is not View > Fullscreen.
When I unmaximize the window, yes, then the scrolling is very fast.
Scott
signature.
But is it faster when the mouse is below the window, then?
JMarc
Le 25 juillet 2024 21:14:36 GMT+02:00, Scott Kostyshak a
écrit :
>On Thu, Jul 25, 2024 at 08:48:49PM GMT, Jean-Marc Lasgouttes wrote:
>> You are in full screen, right ?
>
>No, but by default I don't have any toolbars open so ther
On Thu, Jul 25, 2024 at 08:48:49PM GMT, Jean-Marc Lasgouttes wrote:
> You are in full screen, right ?
No, but by default I don't have any toolbars open so there's only the status
bar at the bottom for me.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists
You are in full screen, right ?
JMarc
Le 25 juillet 2024 20:00:15 GMT+02:00, Scott Kostyshak a
écrit :
>On Thu, Jul 25, 2024 at 06:45:58PM GMT, Jean-Marc Lasgouttes wrote:
>>
>> > To me it seems that scrolling down (if I hold and drag the mouse) is
>> > much slower than if I scroll up. Does a
with your patch is aesthetically way better.
> > >
> > > Thanks for testing. The speed is supposed to be the same indeed, but there
> > > are more smaller scroll events. I will push this version and we'll see
> > > whether we want to tweak it.
> > >
&g
ether we want to tweak it.
I am glad the performance is good enough in any case.
We could perhaps make the selection down little bit faster in full-screen mode,
but that's irrelevant wrt your patch.
Indeed in full screen the mouse cannot be below the window. I do not know
how to handle tha
n and we'll see
> whether we want to tweak it.
>
> I am glad the performance is good enough in any case.
>
> > We could perhaps make the selection down little bit faster in full-screen
> > mode,
> > but that's irrelevant wrt your patch.
>
> Indeed in full
aesthetically way better.
Thanks for testing. The speed is supposed to be the same indeed, but
there are more smaller scroll events. I will push this version and we'll
see whether we want to tweak it.
I am glad the performance is good enough in any case.
We could perhaps make the sele
ake the selection down little bit faster in full-screen mode,
but that's irrelevant wrt your patch.
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 20/07/2024 à 21:23, Richard Kimberly Heck a écrit :
On 7/20/24 3:22 PM, Jean-Marc Lasgouttes wrote:
PS: the profiler tells me that more than 10% of this time is lost
updating macros over and over. I'll take a look at that.
That is at the root of a lot of the performance issues we have.
Th
On 7/20/24 3:22 PM, Jean-Marc Lasgouttes wrote:
PS: the profiler tells me that more than 10% of this time is lost
updating macros over and over. I'll take a look at that.
That is at the root of a lot of the performance issues we have.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
ht
-Marc Lasgouttes
Date: Sat, 20 Jul 2024 19:47:32 +0200
Subject: [PATCH] WIP: make scrolling smoother
This trivial patch makes scrolling-by-selection smoother by dividing
the step size and the time between steps by 8 when generating
synthetic events in work area.
---
src/frontends/qt/GuiWorkArea.cp
On Tue, May 21, 2024 at 08:22:05PM GMT, Pavel Sanda wrote:
> On Tue, May 21, 2024 at 02:11:46PM -0400, Scott Kostyshak wrote:
> > In a document if you do a reference clamp and then select some words, it
> > shows negative counts (see screenshots). After thinking about it I suppose
> > this is accur
On Tue, May 21, 2024 at 02:11:46PM -0400, Scott Kostyshak wrote:
> In a document if you do a reference clamp and then select some words, it
> shows negative counts (see screenshots). After thinking about it I suppose
> this is accurate, but is this useful in any case? I'm not sure what I would
> ex
In a document if you do a reference clamp and then select some words, it shows
negative counts (see screenshots). After thinking about it I suppose this is
accurate, but is this useful in any case? I'm not sure what I would expect
since I don't use reference clamp, but still wanted to check.
Sc
On Wed, Oct 11, 2023 at 10:07:05PM +0200, Yu Jin wrote:
> Sorry, I didn't know that I needed to do that, thank you for telling me.
> done at
> https://git.lyx.org/?p=lyx.git;a=commitdiff;h=f1deb1c658c121e21d484130dbd1ba4e6feaa9f4;hp=c9c5a2a9d824acc10fdd96b0972223450c47c6dd
> hope that's right.
> Ju
Am Donnerstag, dem 12.10.2023 um 08:38 +0200 schrieb Jürgen
Spitzmüller:
> Doesn't this need an (even empty) rc format change?
Sorry, missed the ensuing discussion.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
h
Am Mittwoch, dem 11.10.2023 um 18:47 +0200 schrieb Eugene Chornyi:
> commit 072ba7bd2e1ac7514117fafee3143b0bfb8796eb
> Author: Eugene Chornyi
> Date: Wed Oct 11 20:06:52 2023 +0200
>
> Implement ui style selection dialog 12832
Doesn't this need an (even emp
Am Mi., 11. Okt. 2023 um 20:54 Uhr schrieb Pavel Sanda:
> On Wed, Oct 11, 2023 at 06:47:10PM +0200, Eugene Chornyi wrote:
> > commit 072ba7bd2e1ac7514117fafee3143b0bfb8796eb
> > Author: Eugene Chornyi
> > Date: Wed Oct 11 20:06:52 2023 +0200
> >
> > Implemen
On Wed, Oct 11, 2023 at 06:47:10PM +0200, Eugene Chornyi wrote:
> commit 072ba7bd2e1ac7514117fafee3143b0bfb8796eb
> Author: Eugene Chornyi
> Date: Wed Oct 11 20:06:52 2023 +0200
>
> Implement ui style selection dialog 12832
> ---
> lib/RELEASE-NOTES
On Thu, Aug 18, 2022 at 09:55:50AM +0200, Jürgen Spitzmüller wrote:
> showMessage() is triggered on any cursor action. That's way too often.
> E.g., it would fire down statistics unnecessarily if you move with the
> arrow keys through your document.
I'll add just few observational notes collected
Am Freitag, dem 19.08.2022 um 07:06 +0200 schrieb Jürgen Spitzmüller:
> The crash is fixed in the attached patch, which works well for me.
I have still crashes (when pasting). I don't have time to work on it
further for the time being, so I put it on hold.
--
Jürgen
signature.asc
Description:
Am Fri, 19 Aug 2022 10:47:06 +0200
schrieb Kornel Benko :
> Am Fri, 19 Aug 2022 10:44:23 +0200
> schrieb Kornel Benko :
>
> > Am Fri, 19 Aug 2022 10:16:43 +0200
> > schrieb "Jürgen Spitzmüller" :
> >
> > > Am Freitag, dem 19.08.2022 um 10:07 +0200 schrieb Kornel Benko:
> > > > Both.
Am Fri, 19 Aug 2022 10:44:23 +0200
schrieb Kornel Benko :
> Am Fri, 19 Aug 2022 10:16:43 +0200
> schrieb "Jürgen Spitzmüller" :
>
> > Am Freitag, dem 19.08.2022 um 10:07 +0200 schrieb Kornel Benko:
> > > Both.
> >
> > Interesting. I'd need a recipe for the latter.
> >
>
> Nothing speci
Am Fri, 19 Aug 2022 10:16:43 +0200
schrieb "Jürgen Spitzmüller" :
> Am Freitag, dem 19.08.2022 um 10:07 +0200 schrieb Kornel Benko:
> > Both.
>
> Interesting. I'd need a recipe for the latter.
>
Nothing specific. Does not matter what or how I select some parts,
the number of spaces is wrong (
Am Freitag, dem 19.08.2022 um 10:07 +0200 schrieb Kornel Benko:
> Both.
Interesting. I'd need a recipe for the latter.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Fri, 19 Aug 2022 09:59:45 +0200
schrieb "Jürgen Spitzmüller" :
> Am Freitag, dem 19.08.2022 um 09:54 +0200 schrieb Kornel Benko:
> > I seen it in the status bar. Dialog shows OK.
>
> And only of you select whole words (e.g. via double click)? Or also if
> you select manually?
>
Both.
Am Freitag, dem 19.08.2022 um 09:54 +0200 schrieb Kornel Benko:
> I seen it in the status bar. Dialog shows OK.
And only of you select whole words (e.g. via double click)? Or also if
you select manually?
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel
Am Fri, 19 Aug 2022 09:34:29 +0200
schrieb "Jürgen Spitzmüller" :
> Am Freitag, dem 19.08.2022 um 08:42 +0200 schrieb Kornel Benko:
> > There is something not correct with showing number of spaces in
> > Chinese docs.
> >
> > 1.) Open zh_CN/Tutorial.lyx
> > 2.) Select a single word e.g. 参考文献和交叉引用
Am Freitag, dem 19.08.2022 um 08:42 +0200 schrieb Kornel Benko:
> There is something not correct with showing number of spaces in
> Chinese docs.
>
> 1.) Open zh_CN/Tutorial.lyx
> 2.) Select a single word e.g. 参考文献和交叉引用有点像
> => you get
> number of words1
> number of char
Am Fri, 19 Aug 2022 08:42:20 +0200
schrieb Kornel Benko :
> Am Fri, 19 Aug 2022 07:06:57 +0200
> schrieb "Jürgen Spitzmüller" :
>
> > Am Donnerstag, dem 18.08.2022 um 18:43 +0200 schrieb Jean-Marc
> > Lasgouttes:
> > > Indeed, threads create lots of interesting bugs... It would be better
> > >
Am Fri, 19 Aug 2022 07:06:57 +0200
schrieb "Jürgen Spitzmüller" :
> Am Donnerstag, dem 18.08.2022 um 18:43 +0200 schrieb Jean-Marc
> Lasgouttes:
> > Indeed, threads create lots of interesting bugs... It would be better
> > if we could avoid them
>
> The UX difference to the timer approach is h
rc/Cursor.cpp
+++ b/src/Cursor.cpp
@@ -254,6 +254,7 @@ void CursorData::setSelection()
pit() == normalAnchor().pit() &&
pos() == normalAnchor().pos())
selection(false);
+ buffer()->updateStats();
}
@@ -263,6 +264,7 @@ void CursorData::setSelection(DocIterator co
Indeed, threads create lots of interesting bugs... It would be better if we
could avoid them
JMarc
Le 18 août 2022 18:13:38 GMT+02:00, "Jürgen Spitzmüller" a
écrit
>Performance is an issue in larger documents (e.g., UserGuide).
>
>This one, using threads, is snappy and seems to update relia
sor.cpp
+++ b/src/Cursor.cpp
@@ -254,6 +254,7 @@ void CursorData::setSelection()
pit() == normalAnchor().pit() &&
pos() == normalAnchor().pos())
selection(false);
+ buffer()->updateStats();
}
@@ -263,6 +264,7 @@ void CursorData::setSelection(DocIterator const & where,
Le 18 août 2022 14:25:28 GMT+02:00, "Jürgen Spitzmüller" a
écrit :
>> My method: statistics update only when idle for a long enough time
>> and only once, hence, cannot interfere with continuous typing and are
>> very unlikely to interfere at all.
>
>And it updated after that timing whether it
On 18/08/2022 14:25, Jürgen Spitzmüller wrote:
Am Donnerstag, dem 18.08.2022 um 14:08 +0200 schrieb Daniel:
No function exits early on that approach. The function does not get
called in the first place. I think it is really better.
Currently: statistics update continuously and, hence, can inter
Am Donnerstag, dem 18.08.2022 um 14:08 +0200 schrieb Daniel:
> No function exits early on that approach. The function does not get
> called in the first place. I think it is really better.
>
> Currently: statistics update continuously and, hence, can interfere
> with continuous typing.
Which is
On 18/08/2022 11:44, Jürgen Spitzmüller wrote:
Am Donnerstag, dem 18.08.2022 um 11:31 +0200 schrieb Daniel:
This shouldn't be an issue. The idea is that statistics are only
generated after some time has passed without interruption. They are
not
shown immediately. Hence, continuous arrow key move
On Thu, Aug 18, 2022 at 11:44:49AM +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, dem 18.08.2022 um 11:31 +0200 schrieb Daniel:
> > This shouldn't be an issue. The idea is that statistics are only
> > generated after some time has passed without interruption. They are
> > not
> > shown immedia
Am Donnerstag, dem 18.08.2022 um 11:31 +0200 schrieb Daniel:
> This shouldn't be an issue. The idea is that statistics are only
> generated after some time has passed without interruption. They are
> not
> shown immediately. Hence, continuous arrow key movement would not
> trigger statistics at
or().pit() &&
pos() == normalAnchor().pos())
selection(false);
+ buffer()->updateStats();
}
@@ -263,6 +264,7 @@ void CursorData::setSelection(DocIterator const & where, int n)
selection(true);
anchor_ = where;
pos() += n;
+ buffer()->updateStats();
}
@@ -501,6 +50
On 18/08/2022 09:55, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 17.08.2022 um 19:40 +0200 schrieb Daniel:
What I did in
https://www.lyx.org/trac/attachment/ticket/12422/0001-Show-word-count-in-status-bar.patch
was just to hook it on GuiView::showMessage() because this would be
updated in all c
Am Mittwoch, dem 17.08.2022 um 19:40 +0200 schrieb Daniel:
> What I did in
>
> https://www.lyx.org/trac/attachment/ticket/12422/0001-Show-word-count-in-status-bar.patch
>
> was just to hook it on GuiView::showMessage() because this would be
> updated in all cases where text stuff changes.
show
On 2022-08-17 18:41, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 10.08.2022 um 08:01 +0200 schrieb Daniel:
1. The delay timer seems not to be working as expected. Normally,
i.e.
in other word processors, the idea is this:
While typing, no updating takes place, only once the typing stops,
the
upd
Am Mittwoch, dem 10.08.2022 um 08:01 +0200 schrieb Daniel:
> 1. The delay timer seems not to be working as expected. Normally,
> i.e.
> in other word processors, the idea is this:
>
> While typing, no updating takes place, only once the typing stops,
> the
> update timer starts. Once typing is c
On 11/08/2022 08:54, Pavel Sanda wrote:
On Wed, Aug 10, 2022 at 08:01:47AM +0200, Daniel wrote:
I just tested the new feature. Here are a couple of things that came to my
mind:
1. The delay timer seems not to be working as expected. Normally, i.e. in
other word processors, the idea is this:
Wh
Am Mittwoch, dem 17.08.2022 um 14:21 +0200 schrieb Pavel Sanda:
> I am travelling now, so please do as you see fit, I trust your UI
> eye.
Thanks, done. Have a good trip.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx
On Wed, Aug 17, 2022 at 11:00:39AM +0200, Jürgen Spitzmüller wrote:
> Am Dienstag, dem 16.08.2022 um 12:44 +0200 schrieb Jürgen Spitzmüller:
> > I've seen now that you flagged it for localization. But this is still
> > to anglocentric. Use bformat to construct the string. BTW there is
> > also
> >
Am Wed, 17 Aug 2022 12:39:01 +0200
schrieb "Jürgen Spitzmüller" :
> Am Mittwoch, dem 17.08.2022 um 12:35 +0200 schrieb Daniel:
> > 1 slovo
> > Počet slov: 2... (Wordcount: 2... if I understood correctly)
>
> This could be done on po-level if desired. No code change needed.
It is that way in my
Am Wed, 17 Aug 2022 12:35:05 +0200
schrieb Daniel :
> On 17/08/2022 12:01, Jürgen Spitzmüller wrote:
> > Am Mittwoch, dem 17.08.2022 um 11:56 +0200 schrieb Jürgen Spitzmüller:
> >> If the number of inter-language variations is limited, this can be
> >> supported as well.
> >
> > OTOH the prob
Am Mittwoch, dem 17.08.2022 um 12:35 +0200 schrieb Daniel:
> 1 slovo
> Počet slov: 2... (Wordcount: 2... if I understood correctly)
This could be done on po-level if desired. No code change needed.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel maili
On 17/08/2022 12:01, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 17.08.2022 um 11:56 +0200 schrieb Jürgen Spitzmüller:
If the number of inter-language variations is limited, this can be
supported as well.
OTOH the problem is also unsolved in the existing statistics dialog.
Word uses
1 slovo
On 17/08/2022 11:57, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 17.08.2022 um 11:28 +0200 schrieb Daniel:
If the usage of QStringList is fine, it can also be written a bit
more concise as.
Sure. Though it doesn't buy much.
I guess one should choose (even slightly) less complex code whenever
Am Mittwoch, dem 17.08.2022 um 11:56 +0200 schrieb Jürgen Spitzmüller:
> If the number of inter-language variations is limited, this can be
> supported as well.
OTOH the problem is also unsolved in the existing statistics dialog.
--
Jürgen
signature.asc
Description: This is a digitally signed
Am Mittwoch, dem 17.08.2022 um 11:28 +0200 schrieb Daniel:
> If the usage of QStringList is fine, it can also be written a bit
> more concise as.
Sure. Though it doesn't buy much.
> Also, chars_with_blanks should probably be inside the
> second "if statement"
No, this is re-used further below.
Am Mittwoch, dem 17.08.2022 um 11:41 +0200 schrieb Kornel Benko:
> What about languages with different plurals.
>
> In Slovak for example it would be
> 1 slovo
> 2..4 slová
> 5..\infty slov
If the number of inter-language variations is limited, this can be
supported as well.
--
Jürgen
signatu
Am Wed, 17 Aug 2022 11:28:53 +0200
schrieb Daniel :
> On 17/08/2022 11:13, Jürgen Spitzmüller wrote:
> > Am Mittwoch, dem 17.08.2022 um 11:00 +0200 schrieb Jürgen Spitzmüller:
> >> Attached the way I'd recommend to do it:
> >>
> >> * do not use abbreviations
> >> * allow to enable the stats meas
On 17/08/2022 11:13, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 17.08.2022 um 11:00 +0200 schrieb Jürgen Spitzmüller:
Attached the way I'd recommend to do it:
* do not use abbreviations
* allow to enable the stats measures individually
* left click on stats in status bar opens stats dialog (as
Am Mittwoch, dem 17.08.2022 um 11:00 +0200 schrieb Jürgen Spitzmüller:
> Attached the way I'd recommend to do it:
>
> * do not use abbreviations
> * allow to enable the stats measures individually
> * left click on stats in status bar opens stats dialog (as in LO and
> Word)
>
> The rationale bes
Am Dienstag, dem 16.08.2022 um 12:44 +0200 schrieb Jürgen Spitzmüller:
> I've seen now that you flagged it for localization. But this is still
> to anglocentric. Use bformat to construct the string. BTW there is
> also
> a qt_() function, no need for toqstr(_()).
>
> My point that one-letter abbre
Am Dienstag, dem 16.08.2022 um 12:12 +0200 schrieb Jürgen Spitzmüller:
> It's horrible, really. You need not only to spell it out, but also
> localize it.
I've seen now that you flagged it for localization. But this is still
to anglocentric. Use bformat to construct the string. BTW there is also
a
a couple of alternatives:
> >
> > a. abbreviate only these: "42 cb".
> > b. show blanks: "19 blanks".
>
> I agree with initital cryptic impression and was expectecting someone
> will question it. For me, once you get what w/c/cb is supposed to
> m
tic impression and was expectecting someone will
question it. For me, once you get what w/c/cb is supposed to mean the current
display is easier to parse, especially if you are actively changing the
selection size and need quick feedback while selecting.
We can change it if others will compla
On 2022-08-09 23:53, Pavel Sanda wrote:
On Sat, Aug 06, 2022 at 12:23:25PM -0400, Scott Kostyshak wrote:
I suggest we put this into master and let ppl test on their machines
if any noticeable changes are visible when editing documents. At worst
we can disable this feature by default.
Sounds go
On Tue, Aug 09, 2022 at 11:53:05PM +0200, Pavel Sanda wrote:
> On Sat, Aug 06, 2022 at 12:23:25PM -0400, Scott Kostyshak wrote:
> > > I suggest we put this into master and let ppl test on their machines
> > > if any noticeable changes are visible when editing documents. At worst
> > > we can disabl
On Sat, Aug 06, 2022 at 12:23:25PM -0400, Scott Kostyshak wrote:
> > I suggest we put this into master and let ppl test on their machines
> > if any noticeable changes are visible when editing documents. At worst
> > we can disable this feature by default.
>
> Sounds good to me. Thanks for the pat
> I'm on vacation and won't be able to test for a few weeks. Can you do
> > > > the test I described before? Just select a big document, and then hold
> > > > Shift + to decrease the selection towards the beginning of the
> > > > document. I just
Can you do
> > > the test I described before? Just select a big document, and then hold
> > > Shift + to decrease the selection towards the beginning of the
> > > document. I just counted using a wrist stopwatch and compared
> > > with/without the patch.
> >
&g
then hold
> > Shift + to decrease the selection towards the beginning of the
> > document. I just counted using a wrist stopwatch and compared
> > with/without the patch.
>
> I did that already and haven't seen noticeable lag. But I might have too
> powerful mac
On Sun, Jul 31, 2022 at 05:16:17AM -0400, Scott Kostyshak wrote:
> I'm on vacation and won't be able to test for a few weeks. Can you do
> the test I described before? Just select a big document, and then hold
> Shift + to decrease the selection towards the beginning of the
>
> Pavel
I'm on vacation and won't be able to test for a few weeks. Can you do
the test I described before? Just select a big document, and then hold
Shift + to decrease the selection towards the beginning of the
document. I just counted using a wrist stopwatch and compared
wit
On Fri, Jul 15, 2022 at 12:05:25AM +0200, Pavel Sanda wrote:
> On Thu, Jul 14, 2022 at 09:31:06AM +0200, Daniel wrote:
> > >The drawback is that's it's difficult to understand the interaction between
> > >the two timers now. I stared on the code for couple minutes and it was
> > >not clear to me wh
On Thu, Jul 14, 2022 at 09:31:06AM +0200, Daniel wrote:
> >The drawback is that's it's difficult to understand the interaction between
> >the two timers now. I stared on the code for couple minutes and it was
> >not clear to me what is the idea behind your stop/start changes.
>
> Some comments wou
On 2022-07-14 00:13, Pavel Sanda wrote:
On Wed, Jul 13, 2022 at 08:54:28AM +0200, Daniel wrote:
Hi,
There is also a patch for instant counts at
https://www.lyx.org/trac/ticket/12422. It works with delayed calculations. I
have no idea how this does performance wise, but it might be worth checkin
On Wed, Jul 13, 2022 at 08:54:28AM +0200, Daniel wrote:
> Hi,
>
> There is also a patch for instant counts at
> https://www.lyx.org/trac/ticket/12422. It works with delayed calculations. I
> have no idea how this does performance wise, but it might be worth checking
> out.
Yes, that's lazy man ap
ocaly for couple paragraphs and it
did not occur to me to try selection of the whole document.
In a local use even on my super-speedy repeat rate of keyboard
nothing is noticeable but when I select complete User Guide the
lag is indeed visible. One could perhaps disable the feature
if (to-from) i
r couple paragraphs and it
did not occur to me to try selection of the whole document.
In a local use even on my super-speedy repeat rate of keyboard
nothing is noticeable but when I select complete User Guide the
lag is indeed visible. One could perhaps disable the feature
if (to-from) is too b
Le 12/07/2022 à 22:31, Scott Kostyshak a écrit :
Part of it is that I just like to bother JMarc,
I am glad to humor you.
As for how to solve the performance issue, is there any smart caching
that can be done?
The first thing to do would be to scrap the current method and create a
new ver
,
but this could go in the context menu of the status bar. Already we have
entries there for "Show Zoom Level" and "Show Zoom Slider" (which I also
like to turn off).
As for how to solve the performance issue, is there any smart caching
that can be done? For example, when selectio
Le 12/07/2022 à 21:12, Pavel Sanda a écrit :
Hi,
I need to adhere precise word/character counts in sections of a document.
For this I need to have instantaneous visual feedback of stats when selecting
blocks of text.
The attached patch does this. Is there some objection to push this into master
Stats if selection is done
+ if (cur.selection()) {
+ DocIterator from, to;
+ from = cur.selectionBegin();
+ to = cur.selectionEnd();
+ buf.updateStatistics(from, to);
+ int const words = buf.wordCount();
+
On Thu, Mar 17, 2022 at 05:05:45PM +0100, Jean-Marc Lasgouttes wrote:
> Le 13/03/2022 à 21:39, Scott Kostyshak a écrit :
> > A git bisect lead me here based on the following:
>
> Fixed. Next, please!
Thanks for the quick fix! Tested and works well.
Scott
signature.asc
Description: PGP signatur
Le 13/03/2022 à 21:39, Scott Kostyshak a écrit :
A git bisect lead me here based on the following:
Fixed. Next, please!
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 14/03/2022 à 15:51, Scott Kostyshak a écrit :
Whenever I get sad, finding a regression to bug JMarc with always cheers
me up :)
I knew it.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Marc Lasgouttes
> > > Date: Wed Apr 4 18:24:14 2018 +0200
> > >
> > > When inserting math inset, put cursor selection in the correct cell
> >
> > A git bisect lead me here based on the following:
>
> Why is it that you like to dig up my old commi
Le 13/03/2022 à 21:39, Scott Kostyshak a écrit :
On Thu, Apr 05, 2018 at 11:24:27AM +0200, Jean-Marc Lasgouttes wrote:
commit 503c7c1688bee80a2c5dc472aaf97fb2aa0391e0
Author: Jean-Marc Lasgouttes
Date: Wed Apr 4 18:24:14 2018 +0200
When inserting math inset, put cursor selection in the
On Thu, Apr 05, 2018 at 11:24:27AM +0200, Jean-Marc Lasgouttes wrote:
> commit 503c7c1688bee80a2c5dc472aaf97fb2aa0391e0
> Author: Jean-Marc Lasgouttes
> Date: Wed Apr 4 18:24:14 2018 +0200
>
> When inserting math inset, put cursor selection in the correct cell
>
>
On 2022-01-27 15:52, Jean-Marc Lasgouttes wrote:
Le 27/01/2022 à 14:59, Daniel a écrit :
I guess in Scott's after.png the selection looks a bit confusing (as
in unexpected because other applications don't highlight that way).
Isn't there another way to select the "Chap
On Thu, Jan 27, 2022 at 03:52:14PM +0100, Jean-Marc Lasgouttes wrote:
>
> Le 27/01/2022 à 14:59, Daniel a écrit :
> > I guess in Scott's after.png the selection looks a bit confusing (as in
> > unexpected because other applications don't highlight that way). Isn'
Le 27/01/2022 à 14:59, Daniel a écrit :
I guess in Scott's after.png the selection looks a bit confusing (as in
unexpected because other applications don't highlight that way). Isn't
there another way to select the "Chapter" label?
Do you have examples of application
the way the top and bottom selection are drawn
When a selection extends on more than a row, the space between
the two
rows should always be painted in full. Otherwise, with layouts like
Chapter, the "Chapter" label may seem selected in part.
---
I think this changed b
Le 27/01/2022 à 14:06, Scott Kostyshak a écrit :
On Tue, Dec 07, 2021 at 05:50:09PM +0100, Jean-Marc Lasgouttes wrote:
commit 2fd8b6fc2a402c00e78f71d7d6ad986270283a3e
Author: Jean-Marc Lasgouttes
Date: Tue Dec 7 18:15:01 2021 +0100
Fix the way the top and bottom selection are drawn
On Tue, Dec 07, 2021 at 05:50:09PM +0100, Jean-Marc Lasgouttes wrote:
> commit 2fd8b6fc2a402c00e78f71d7d6ad986270283a3e
> Author: Jean-Marc Lasgouttes
> Date: Tue Dec 7 18:15:01 2021 +0100
>
> Fix the way the top and bottom selection are drawn
>
> When a sele
On Sun, Sep 12, 2021 at 09:07:03AM +0200, Jürgen Spitzmüller wrote:
> Am Samstag, dem 11.09.2021 um 10:57 -0400 schrieb Scott Kostyshak:
> > 2. If (2) is not always the case, would we need an extra layout
> > parameter that determines where it is most natural for the selection
&
Am Samstag, dem 11.09.2021 um 10:57 -0400 schrieb Scott Kostyshak:
> 2. If (2) is not always the case, would we need an extra layout
> parameter that determines where it is most natural for the selection
> to be placed into?
Probably this.
Jürgen
signature.asc
Description: This is a
o select one or more paragraphs and then
choose the environment (in this case, the "only" environment) and this would
cause the selection to be included in the auto-inserted argument, which is not
what the user expects.
I see 3 possibilities:
1. For environments, should the selection
1 - 100 of 1315 matches
Mail list logo
