Am Dienstag, dem 18.03.2025 um 08:15 +0100 schrieb Jürgen Spitzmüller:
> Just from very brief head-scratching I'd say there's no point in
> loading all the bullet SVGs when launching the dialog. It would be
> enough to completely setup the one panel and level that is selected
> and
> finish the oth
On 3/21/25 12:20 PM, Jürgen Spitzmüller wrote:
Am Freitag, dem 21.03.2025 um 13:53 +0100 schrieb Jean-Marc Lasgouttes:
Thanks, this is very snappy now! Pmprof says:
#pmprof# bulletsModule: 837 us, count=1, total=837 us
#pmprof# colorModule: 45.10 ms, count=1, total=45.10 ms
#pmprof# GuiDocument
Am Freitag, dem 21.03.2025 um 13:53 +0100 schrieb Jean-Marc Lasgouttes:
> Thanks, this is very snappy now! Pmprof says:
>
> #pmprof# bulletsModule: 837 us, count=1, total=837 us
> #pmprof# colorModule: 45.10 ms, count=1, total=45.10 ms
> #pmprof# GuiDocument: 105.95 ms, count=1, total=105.95 ms
P
Le 20/03/2025 à 17:54, Jürgen Spitzmüller a écrit :
I'll see if I can take a look at this somewhere in the near future.
I've done this today, as you've probably seen.
Document dialog now loads subjectively faster (and it should also in
theory). I hope this also shows in numbers.
Thanks, this
On Thu, Mar 20, 2025 at 05:54:56PM +0100, Jürgen Spitzmüller wrote:
> Am Dienstag, dem 18.03.2025 um 08:15 +0100 schrieb Jürgen Spitzmüller:
> > Just from very brief head-scratching I'd say there's no point in
> > loading all the bullet SVGs when launching the dialog. It would be
> > enough to comp
s and use it
> > > in several combo boxes? I see 21 calls to updateCustomColors just to
> > > open the document settings on an empty document.
> >
> > I've done this now. The only thing I didn't manage to implement is the
> > " (Default)" fl
Am Montag, dem 17.03.2025 um 18:26 +0100 schrieb Jean-Marc Lasgouttes:
> Only the bullets panel stands out.
Just from very brief head-scratching I'd say there's no point in
loading all the bullet SVGs when launching the dialog. It would be
enough to completely setup the one panel and level that is
Am Mittwoch, dem 12.03.2025 um 11:38 +0100 schrieb Jean-Marc
Lasgouttes:
> Isn't it possible to have a single model for these colors and use it
> in several combo boxes? I see 21 calls to updateCustomColors just to
> open the document settings on an empty document.
I've done
Le 17/03/2025 à 16:50, Jürgen Spitzmüller a écrit :
Am Mittwoch, dem 12.03.2025 um 11:38 +0100 schrieb Jean-Marc
Lasgouttes:
Isn't it possible to have a single model for these colors and use it
in several combo boxes? I see 21 calls to updateCustomColors just to
open the document settings
p
the cycles?
Isn't it possible to have a single model for these colors and use it in
several combo boxes? I see 21 calls to updateCustomColors just to open
the document settings on an empty document.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel
On Wed, Mar 12, 2025 at 03:25:19PM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, dem 12.03.2025 um 12:42 +0100 schrieb Scott Kostyshak:
> > Sounds good. One more attempt at a quick-fix-in-the-meantime solution
> > (tell me if you wish not even to discuss and I will stop). It seems
> > that addIte
On Mon, Mar 10, 2025 at 09:53:34AM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 09.03.2025 um 18:23 +0100 schrieb Jean-Marc Lasgouttes:
> > With 2.5, this is dwarfed by ColorCombo, but that is a different
> > story.
>
> One thing that probably is expensive (and might be optimized) is that
>
Am Mittwoch, dem 12.03.2025 um 12:42 +0100 schrieb Scott Kostyshak:
> Sounds good. One more attempt at a quick-fix-in-the-meantime solution
> (tell me if you wish not even to discuss and I will stop). It seems
> that addItemSort() is taking up the cycles. We call that inside two
> loops inside Colo
s and use it
> > > in several combo boxes? I see 21 calls to updateCustomColors just to
> > > open the document settings on an empty document.
> >
> > Probably. But as I said, this has to wait.
>
> Fine with me.
Sounds good. One more attempt at a quick-fix-in-the
Am Mittwoch, dem 12.03.2025 um 11:38 +0100 schrieb Jean-Marc
Lasgouttes:
> Isn't it possible to have a single model for these colors and use it
> in several combo boxes? I see 21 calls to updateCustomColors just to
> open the document settings on an empty document.
Probably. But a
Le 12/03/2025 à 11:47, Jürgen Spitzmüller a écrit :
Am Mittwoch, dem 12.03.2025 um 11:38 +0100 schrieb Jean-Marc
Lasgouttes:
Isn't it possible to have a single model for these colors and use it
in several combo boxes? I see 21 calls to updateCustomColors just to
open the document settings
Am Sonntag, dem 09.03.2025 um 18:23 +0100 schrieb Jean-Marc Lasgouttes:
> With 2.5, this is dwarfed by ColorCombo, but that is a different
> story.
One thing that probably is expensive (and might be optimized) is that
the color combo needs to be updated regularly to catch up with the
custom colors
On Sun, Mar 09, 2025 at 10:02:08PM +0100, Jean-Marc Lasgouttes wrote:
> Le 09/03/2025 à 21:38, Scott Kostyshak a écrit :
> > Thanks for the patch!
> >
> > I have similar stats:
> >
> > #pmprof# bulletsModule: 313.96 ms, count=1, total=313.96 ms
> > #pmprof# colorModule: 931.35 ms, count=1, total=
Le 09/03/2025 à 21:38, Scott Kostyshak a écrit :
Thanks for the patch!
I have similar stats:
#pmprof# bulletsModule: 313.96 ms, count=1, total=313.96 ms
#pmprof# colorModule: 931.35 ms, count=1, total=931.35 ms
#pmprof# GuiDocument: 1.29 s, count=1, total=1.29 s
And does the lag feels like 1.
Le 09/03/2025 à 18:23, Jean-Marc Lasgouttes a écrit :
I do not have much time right now, but hotspot thinks that the time is
spent in BulletsModule constructor.
This code uses svg images since the commit below. Would it be faster
with one big svg for each type of bullets ?
With 2.5, this is
On Sun, Mar 09, 2025 at 07:09:01PM +0100, Jean-Marc Lasgouttes wrote:
> Le 09/03/2025 à 18:23, Jean-Marc Lasgouttes a écrit :
> > I do not have much time right now, but hotspot thinks that the time is
> > spent in BulletsModule constructor.
> >
> > This code uses svg images since the commit below.
On 3/8/25 12:49, Scott Kostyshak wrote:
On Sat, Mar 08, 2025 at 11:31:47AM -0500, Paul Rubin wrote:
On 3/8/25 07:39, Scott Kostyshak wrote:
To reproduce:
1. Start a new document.
2. Document > Settings.
To me, it feels like it takes a bit longer for the dialog to show than I
remem
On 3/9/25 12:02 PM, Paul Rubin wrote:
On 3/8/25 12:49, Scott Kostyshak wrote:
On Sat, Mar 08, 2025 at 11:31:47AM -0500, Paul Rubin wrote:
On 3/8/25 07:39, Scott Kostyshak wrote:
To reproduce:
1. Start a new document.
2. Document > Settings.
To me, it feels like it takes a bit longer
On Sat, Mar 08, 2025 at 11:31:47AM -0500, Paul Rubin wrote:
>
>
> On 3/8/25 07:39, Scott Kostyshak wrote:
> > To reproduce:
> >
> > 1. Start a new document.
> > 2. Document > Settings.
> >
> > To me, it feels like it takes a bit longer for the
On 3/8/25 07:39, Scott Kostyshak wrote:
To reproduce:
1. Start a new document.
2. Document > Settings.
To me, it feels like it takes a bit longer for the dialog to show than I
remember.
I did a quick check and indeed 2.3.0 and 2.3.x are faster. However,
often when I debug these issues
To reproduce:
1. Start a new document.
2. Document > Settings.
To me, it feels like it takes a bit longer for the dialog to show than I
remember.
I did a quick check and indeed 2.3.0 and 2.3.x are faster. However,
often when I debug these issues it turns out I have different compiler
setti
On Mon, May 08, 2023 at 10:13:56PM +0200, Jean-Marc Lasgouttes wrote:
> Le 08/05/2023 ?? 17:26, Pavel Sanda a écrit :
> >Hi,
> >
> >the document settings dialog quite grew in vertical size for 2.4 mainly due
> >to the
> >formats pane and I think we should shrink
Le 08/05/2023 à 17:26, Pavel Sanda a écrit :
Hi,
the document settings dialog quite grew in vertical size for 2.4 mainly due to
the
formats pane and I think we should shrink it back.
Why is this called Formats and not Output, BTW?
I also think that a subpanel Output Options, with TeX/XHTML
Am Montag, dem 08.05.2023 um 18:03 +0200 schrieb Jürgen Spitzmüller:
> I'd go for tabs or something similar. These contents clearly belong
> to the section they are.
Or we can introduce subsections as we have in prefs.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx
Am Montag, dem 08.05.2023 um 17:26 +0200 schrieb Pavel Sanda:
> Hi,
>
> the document settings dialog quite grew in vertical size for 2.4
> mainly due to the
> formats pane and I think we should shrink it back.
>
> I see several options:
> 1) create tabbed pane for docbo
Hi,
the document settings dialog quite grew in vertical size for 2.4 mainly due to
the
formats pane and I think we should shrink it back.
I see several options:
1) create tabbed pane for docbook/xhtml(and perhaps TeX)
2) Move content of "LyX Format" to "Output format&quo
On Wed, Mar 08, 2023 at 08:26:05AM +0100, Jürgen Spitzmüller wrote:
> > Maybe I was not precise enough, try this one:
> > 1. go to the document setting -> modules
> > 2. click and hold *on arrow* of 'Accesibility' item (so it gets unrolled)
> > 3. while holding move mouse strictly vertically down t
Am Tue, 7 Mar 2023 16:01:01 -0500
schrieb Scott Kostyshak :
> On Tue, Mar 07, 2023 at 08:54:30PM +0100, Pavel Sanda wrote:
> > On Tue, Mar 07, 2023 at 05:13:41PM +0100, Kornel Benko wrote:
> > > Am Tue, 7 Mar 2023 16:04:55 +0100 (CET)
> > > schrieb "Jürgen Spitzmüller" :
> > >
> > > > Pavel
> Maybe I was not precise enough, try this one:
> 1. go to the document setting -> modules
> 2. click and hold *on arrow* of 'Accesibility' item (so it gets unrolled)
> 3. while holding move mouse strictly vertically down to the line of Braille
> item (but stay horizontally ahead of the item)
> 4.
On Tue, Mar 07, 2023 at 08:54:30PM +0100, Pavel Sanda wrote:
> On Tue, Mar 07, 2023 at 05:13:41PM +0100, Kornel Benko wrote:
> > Am Tue, 7 Mar 2023 16:04:55 +0100 (CET)
> > schrieb "Jürgen Spitzmüller" :
> >
> > > Pavel Sanda schrieb am 07.03.2023 12:59 (GMT +01:00):
> > > > 1. go to the document
On Tue, Mar 07, 2023 at 05:13:41PM +0100, Kornel Benko wrote:
> Am Tue, 7 Mar 2023 16:04:55 +0100 (CET)
> schrieb "Jürgen Spitzmüller" :
>
> > Pavel Sanda schrieb am 07.03.2023 12:59 (GMT +01:00):
> > > 1. go to the document setting -> modules
> > > 2. click in avail modules 'Maths'
> > > 3. clic
Am Tue, 7 Mar 2023 16:04:55 +0100 (CET)
schrieb "Jürgen Spitzmüller" :
> Pavel Sanda schrieb am 07.03.2023 12:59 (GMT +01:00):
> > 1. go to the document setting -> modules
> > 2. click in avail modules 'Maths'
> > 3. click *and hold* 'Accesibility'
> > 4. while holding move mouse to the Braille i
Pavel Sanda schrieb am 07.03.2023 12:59 (GMT +01:00):
> 1. go to the document setting -> modules
> 2. click in avail modules 'Maths'
> 3. click *and hold* 'Accesibility'
> 4. while holding move mouse to the Braille item below Accesibility
> 5. kaboom
>
> anyone can reproduce?
I can't, neither Qt5
On Tue, Mar 07, 2023 at 12:49:24PM +0100, Pavel Sanda wrote:
> Hi,
>
> I am struggling to get exact recipy, but I am repeatedly getting
> crashes with document settings dialog, modules panel.
I think I have the recipy:
1. go to the document setting -> modules
2. click in avail mo
Hi,
I am struggling to get exact recipy, but I am repeatedly getting
crashes with document settings dialog, modules panel.
Generally I have opened few categories of modules, then click & hold the
mouse button and start moving around in the combobox. Sometimes I
get the crash most often not.
On Sat, May 23, 2020 at 06:32:32PM +0200, Jürgen Spitzmüller wrote:
> Am Samstag, den 23.05.2020, 11:41 -0400 schrieb Richard Kimberly Heck:
> > > Ah interesting. The Document Settings window does not maximize
> > > here, on
> > > GNOME. I thought it was a Qt t
Am Samstag, den 23.05.2020, 11:41 -0400 schrieb Richard Kimberly Heck:
> > Ah interesting. The Document Settings window does not maximize
> > here, on
> > GNOME. I thought it was a Qt thing but maybe it's a DE thing.
>
> If so, that would explain why your patch had no
On 5/23/20 9:14 AM, Scott Kostyshak wrote:
> On Fri, May 22, 2020 at 10:46:03PM -0400, Richard Kimberly Heck wrote:
>> On 5/22/20 1:45 PM, Scott Kostyshak wrote:
>>> It is sometimes useful to be able to maximize the document settings
>>> window. For example, when adding
On Fri, May 22, 2020 at 10:46:03PM -0400, Richard Kimberly Heck wrote:
> On 5/22/20 1:45 PM, Scott Kostyshak wrote:
> > It is sometimes useful to be able to maximize the document settings
> > window. For example, when adding modules some of the module names are
> > wide. I t
On 5/22/20 1:45 PM, Scott Kostyshak wrote:
> It is sometimes useful to be able to maximize the document settings
> window. For example, when adding modules some of the module names are
> wide. I tried to allow it, but could not get it to work. Does anyone
> have an idea? Attached is
It is sometimes useful to be able to maximize the document settings
window. For example, when adding modules some of the module names are
wide. I tried to allow it, but could not get it to work. Does anyone
have an idea? Attached is a patch with my attempt that does not work.
Scott
diff --git a
On 2019-04-26, Guenter Milde wrote:
> Dear LyX developers,
> there is a glitch in the Document>Settings>Fonts dialogue in current master:
Fixed at 337e3ff9a6b6
Günter
Dear LyX developers,
there is a glitch in the Document>Settings>Fonts dialogue in current master:
How to reproduce: Open a new document (or a document with the new default
value of the font-encoding setting "\fontencoding auto") and open the
Fonts dialogue:
The GUI shows:
LaT
that the Document Settings dialog is partially broken in macos (build
with Qt-5.11.2).
When making a change to the settings (with the default document class) the
buttons (OK, apply, reset) are not highlighted. They seem still active though,
so you can click on them.
When choosing another doc
> Am 04.10.2018 um 14:36 schrieb pdv :
>>
>> Jean-Marc,
>>
>> I noticed that the Document Settings dialog is partially broken in macos
>> (build with Qt-5.11.2).
>>
>> When making a change to the settings (with the default document class) the
>>
Am 04.10.2018 um 14:36 schrieb pdv :
>
> Jean-Marc,
>
> I noticed that the Document Settings dialog is partially broken in macos
> (build with Qt-5.11.2).
>
> When making a change to the settings (with the default document class) the
> buttons (OK, apply, reset) are no
Jean-Marc,
I noticed that the Document Settings dialog is partially broken in macos
(build with Qt-5.11.2).
When making a change to the settings (with the default document class)
the buttons (OK, apply, reset) are not highlighted. They seem still
active though, so you can click on them
erials only generated when it is visible on the screen? Or
are all of the previews generated when you open a document?
Can you send an example file where it takes 8 seconds to open document
settings?
Scott
On 02.11.2017 19:15, Jürgen Spitzmüller wrote:
Am Donnerstag, den 02.11.2017, 18:41 +0200 schrieb racoon:
On 02.11.2017 19:22, Jürgen Spitzmüller wrote:
Am Donnerstag, den 02.11.2017, 17:21 +0200 schrieb racoon:
The opening of Document Settings takes about 8 seconds for some
Documents on my
On 02.11.2017 21:34, Andrew Parsloe wrote:
On 3/11/2017 5:44 a.m., racoon wrote:
On 02.11.2017 17:21, racoon wrote:
The opening of Document Settings takes about 8 seconds for some
Documents on my system. LyX becomes unresponsive in the meanwhile.
(Core 2 Duo, Win7)
I noticed that the
On 3/11/2017 5:44 a.m., racoon wrote:
On 02.11.2017 17:21, racoon wrote:
The opening of Document Settings takes about 8 seconds for some
Documents on my system. LyX becomes unresponsive in the meanwhile.
(Core 2 Duo, Win7)
I noticed that the delay became longer in beta1. But it was much
Am Donnerstag, den 02.11.2017, 18:41 +0200 schrieb racoon:
> On 02.11.2017 19:22, Jürgen Spitzmüller wrote:
> > Am Donnerstag, den 02.11.2017, 17:21 +0200 schrieb racoon:
> > > The opening of Document Settings takes about 8 seconds for some
> > > Documents on my system.
On 02.11.2017 19:22, Jürgen Spitzmüller wrote:
Am Donnerstag, den 02.11.2017, 17:21 +0200 schrieb racoon:
The opening of Document Settings takes about 8 seconds for some
Documents on my system. LyX becomes unresponsive in the meanwhile.
(Core
2 Duo, Win7)
I noticed that the delay became longer
On 02.11.2017 17:21, racoon wrote:
The opening of Document Settings takes about 8 seconds for some
Documents on my system. LyX becomes unresponsive in the meanwhile. (Core
2 Duo, Win7)
I noticed that the delay became longer in beta1. But it was much faster
still.
Seems like these delays
On 02.11.2017 19:02, Scott Kostyshak wrote:
On Thu, Nov 02, 2017 at 03:21:02PM +, racoon wrote:
The opening of Document Settings takes about 8 seconds for some Documents on
my system. LyX becomes unresponsive in the meanwhile. (Core 2 Duo, Win7)
I noticed that the delay became longer in
Am Donnerstag, den 02.11.2017, 17:21 +0200 schrieb racoon:
> The opening of Document Settings takes about 8 seconds for some
> Documents on my system. LyX becomes unresponsive in the meanwhile.
> (Core
> 2 Duo, Win7)
>
> I noticed that the delay became longer in beta1. But it
On Thu, Nov 02, 2017 at 03:21:02PM +, racoon wrote:
> The opening of Document Settings takes about 8 seconds for some Documents on
> my system. LyX becomes unresponsive in the meanwhile. (Core 2 Duo, Win7)
>
> I noticed that the delay became longer in beta1. But it was much fa
The opening of Document Settings takes about 8 seconds for some
Documents on my system. LyX becomes unresponsive in the meanwhile. (Core
2 Duo, Win7)
I noticed that the delay became longer in beta1. But it was much faster
still.
Daniel
overriding it.
>> Remember that although reassigning an unused shortcut might make
>> sense in your app, your users are likely to know and expect the
>> original, established meaning.
>>
>
> Wouldn't this fit then on mac:
> "Shift-Command-P : Page setup
s are likely to know and expect the
> original, established meaning.
>
Wouldn't this fit then on mac:
"Shift-Command-P : Page setup: Display a window for selecting document
settings."
from:
https://support.apple.com/en-us/HT201236
greetings
Mike
Le 15/05/2017 à 01:30, Guillaume MM a écrit :
I do not see an opportunity to change the existing shortcut Ctrl+R.
The denotation of an accelerator has to be accidental. In French it is
"Paramètres", which fits with Ctrl+P.
Considering shortcut reuse, here is what Apple has to say:
* Key se
Le 15/05/2017 à 01:01, Scott Kostyshak a écrit :
On Fri, Apr 21, 2017 at 03:53:08PM -0400, Scott Kostyshak wrote:
On Fri, Apr 21, 2017 at 10:48:05AM +0200, Jean-Marc Lasgouttes wrote:
Le 21/04/2017 à 05:50, Scott Kostyshak a écrit :
Should we have a keyboard shortcut for document settings, as
On Fri, Apr 21, 2017 at 03:53:08PM -0400, Scott Kostyshak wrote:
> On Fri, Apr 21, 2017 at 10:48:05AM +0200, Jean-Marc Lasgouttes wrote:
> > Le 21/04/2017 à 05:50, Scott Kostyshak a écrit :
> > > Should we have a keyboard shortcut for document settings, as proposed at
&
On Fri, Apr 21, 2017 at 10:48:05AM +0200, Jean-Marc Lasgouttes wrote:
> Le 21/04/2017 à 05:50, Scott Kostyshak a écrit :
> > Should we have a keyboard shortcut for document settings, as proposed at
> >
> > http://www.lyx.org/trac/ticket/10400
> >
> > ?
> &g
Le 21/04/2017 à 05:50, Scott Kostyshak a écrit :
Should we have a keyboard shortcut for document settings, as proposed at
http://www.lyx.org/trac/ticket/10400
?
There is a proposal to use ctrl + p, which is now free because we got
rid of print.
I agree a shortcut would be nice. I have
Am Donnerstag, 20. April 2017 um 23:50:45, schrieb Scott Kostyshak
> Should we have a keyboard shortcut for document settings, as proposed at
>
> http://www.lyx.org/trac/ticket/10400
>
> ?
>
> There is a proposal to use ctrl + p, which is now free because we go
Should we have a keyboard shortcut for document settings, as proposed at
http://www.lyx.org/trac/ticket/10400
?
There is a proposal to use ctrl + p, which is now free because we got
rid of print.
I agree a shortcut would be nice. I have mixed feelings about the
particular shortcut ctrl + p
On Sun, Feb 26, 2017 at 02:33:07PM +0200, racoon wrote:
> Every time I try to open the document settings LyX crashes.
>
> LyX Version 2.3.0dev
> Built from git commit hash 3c329db0
I imagine that it works on a previous commit? If so, are you familiar
with a git bisect? It takes time,
Every time I try to open the document settings LyX crashes.
LyX Version 2.3.0dev
Built from git commit hash 3c329db0
OS: Windows 7
On Mon, May 09, 2016 at 12:03:20PM +0200, Helge Hafting wrote:
>
>
> Den 07. mai 2016 08:35, skrev Guenter Milde:
> > This leaves open the possibility to (re)activate the validator in 2.2.1
> > after a non-rushed discussion.
> >
> > I still favour allowing values that
> > * LaTeX allows,
> >
Den 07. mai 2016 08:35, skrev Guenter Milde:
This leaves open the possibility to (re)activate the validator in 2.2.1
after a non-rushed discussion.
I still favour allowing values that
* LaTeX allows,
* have use cases (maybe rare) and
* are not "dangerous".
Negative margins has some u
On 2016-05-06, Jean-Marc Lasgouttes wrote:
> Le 06/05/16 à 09:42, Jürgen Spitzmüller a écrit :
>> Am Mittwoch, den 04.05.2016, 02:21 -0400 schrieb Scott Kostyshak:
>>> Attached is a patch. It seems that everyone in this thread is in
>>> favor of allowing negative values where LaTeX allows negative
On Fri, May 06, 2016 at 09:42:39AM +0200, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 04.05.2016, 02:21 -0400 schrieb Scott Kostyshak:
> > Attached is a patch. It seems that everyone in this thread is in
> > favor
> > of allowing negative values where LaTeX allows negative values. The
> > patch do
Le 06/05/16 à 09:42, Jürgen Spitzmüller a écrit :
Am Mittwoch, den 04.05.2016, 02:21 -0400 schrieb Scott Kostyshak:
Attached is a patch. It seems that everyone in this thread is in
favor
of allowing negative values where LaTeX allows negative values. The
patch does this.
Note however that (if I
Am Mittwoch, den 04.05.2016, 02:21 -0400 schrieb Scott Kostyshak:
> Attached is a patch. It seems that everyone in this thread is in
> favor
> of allowing negative values where LaTeX allows negative values. The
> patch does this.
>
> Note however that (if I understand correctly the comments at #10
o wrote:
>>>>> Scott Kostyshak wrote:
>>>>>> In 2.1.x, because of a bug in our validator code, we allowed negative
>>>>>> values to be input into some document settings. This bug has been fixed
>>>>>> for 2.2.0dev but what that m
gt;>> In 2.1.x, because of a bug in our validator code, we allowed negative
> >>>> values to be input into some document settings. This bug has been fixed
> >>>> for 2.2.0dev but what that means is that if you open such a document
> >>>> with LyX
gative
>>>> values to be input into some document settings. This bug has been fixed
>>>> for 2.2.0dev but what that means is that if you open such a document
>>>> with LyX 2.2.0dev, you will not be able to save any changes to document
>>>> settings
;>>> values to be input into some document settings. This bug has been fixed
>>>> for 2.2.0dev but what that means is that if you open such a document
>>>> with LyX 2.2.0dev, you will not be able to save any changes to document
>>>> settings unless you correc
On Mon, Apr 25, 2016 at 11:48:00AM -0400, Richard Heck wrote:
> On 04/24/2016 10:21 PM, Cyrille Artho wrote:
> > Scott Kostyshak wrote:
> >> In 2.1.x, because of a bug in our validator code, we allowed negative
> >> values to be input into some document settings. This
On 04/24/2016 10:21 PM, Cyrille Artho wrote:
> Scott Kostyshak wrote:
>> In 2.1.x, because of a bug in our validator code, we allowed negative
>> values to be input into some document settings. This bug has been fixed
>> for 2.2.0dev but what that means is that if you open su
Scott Kostyshak wrote:
In 2.1.x, because of a bug in our validator code, we allowed negative
values to be input into some document settings. This bug has been fixed
for 2.2.0dev but what that means is that if you open such a document
with LyX 2.2.0dev, you will not be able to save any changes to
On 04/24/2016 09:46 PM, Scott Kostyshak wrote:
> On Sun, Apr 24, 2016 at 04:24:48PM -0400, Richard Heck wrote:
>> On 04/24/2016 01:10 PM, Scott Kostyshak wrote:
>>> In 2.1.x, because of a bug in our validator code, we allowed negative
>>> values to be input into some
On Sun, Apr 24, 2016 at 04:24:48PM -0400, Richard Heck wrote:
> On 04/24/2016 01:10 PM, Scott Kostyshak wrote:
> > In 2.1.x, because of a bug in our validator code, we allowed negative
> > values to be input into some document settings. This bug has been fixed
> > for 2.2.0de
On 04/24/2016 01:10 PM, Scott Kostyshak wrote:
> In 2.1.x, because of a bug in our validator code, we allowed negative
> values to be input into some document settings. This bug has been fixed
> for 2.2.0dev but what that means is that if you open such a document
> with LyX 2.2.0dev,
In 2.1.x, because of a bug in our validator code, we allowed negative
values to be input into some document settings. This bug has been fixed
for 2.2.0dev but what that means is that if you open such a document
with LyX 2.2.0dev, you will not be able to save any changes to document
settings unless
On Sun, Feb 21, 2016 at 12:00:05PM -0500, PhilipPirrip wrote:
> On 02/21/2016 10:59 AM, Richard Heck wrote:
> >I'd say go ahead. I'm almost certain this is not the right way to fix
> >the bug.
>
> Done: http://www.lyx.org/trac/ticket/9979
>
> Do we need one for the first problem, as a reminder to
On 02/21/2016 10:59 AM, Richard Heck wrote:
I'd say go ahead. I'm almost certain this is not the right way to fix
the bug.
Done: http://www.lyx.org/trac/ticket/9979
Do we need one for the first problem, as a reminder to commit?
On 02/21/2016 10:35 AM, PhilipPirrip wrote:
> On 02/20/2016 11:18 PM, Richard Heck wrote:
>> One solution would be to have Buffer::collectChildren make sure the
>> Buffers exist.
>
> I can confirm that your patch fixes the problem. Thanks, Richard!
>
> Scott, do you still want me to file the bug re
On 02/20/2016 11:18 PM, Richard Heck wrote:
One solution would be to have Buffer::collectChildren make sure the
Buffers exist.
I can confirm that your patch fixes the problem. Thanks, Richard!
Scott, do you still want me to file the bug report?
something in Chapter02 (add a character)
>
> go back to the master document (ClassicThesis.lyx)
>
> open Document Settings dialog, keep it open
>
> then File>Close (or ctrl-w)
>
> Save changes? - choose Discard
>
> LyX crashes, SIGSEGV
This one is more complicated,
On Sat, Feb 20, 2016 at 08:01:37PM -0500, PhilipPirrip wrote:
> On 02/20/2016 07:45 PM, Richard Heck wrote:
> >Something like this:
> >...
> > ...
> >should fix it.
>
> #1 fixed
Good. I would say commit then, Richard. I tried to think of a better
variable name that isReadOnly to take into account
On 02/20/2016 07:45 PM, Richard Heck wrote:
Something like this:
...
> ...
should fix it.
#1 fixed
Not sure about the other one.
#2 not
On 02/20/2016 07:46 PM, PhilipPirrip wrote:
> On 02/20/2016 07:40 PM, Richard Heck wrote:
>> There's a missing test somewhere on whether the dialog needs a view,
>> which this one does. The dialog should really be closed when the last
>> view disappears.
>
> That's only the first case, I believe.
>
On 02/20/2016 07:40 PM, Richard Heck wrote:
There's a missing test somewhere on whether the dialog needs a view,
which this one does. The dialog should really be closed when the last
view disappears.
That's only the first case, I believe.
But in the second case you still have the first, new, d
1 - 100 of 243 matches
Mail list logo
