Le 27/04/2018 à 03:03, Richard Kimberly Heck a écrit :
Yes, go ahead. It will let it get some testing before release.
Done, thanks. No status.23x entry necessary, since this is new code.
JMarc
On 04/26/2018 05:33 PM, Jean-Marc Lasgouttes wrote:
> Le 18/04/2018 à 14:18, Pavel Sanda a écrit :
>> Jean-Marc Lasgouttes wrote:
>>> Le 17/04/2018 ?? 11:52, Jean-Marc Lasgouttes a écrit :
Sorry for being slow on this. As I understand it, the crash is
related to
the new painting arch
Le 18/04/2018 à 14:18, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 17/04/2018 ?? 11:52, Jean-Marc Lasgouttes a écrit :
Sorry for being slow on this. As I understand it, the crash is related to
the new painting architecture and therefore probably exists in 2.3.x too.
This is the one I n
Jean-Marc Lasgouttes wrote:
>> I will have to check with qt5 again but master is dead slow again for
>> cursor
>> movement (even without this patch). Perhaps we killed it in previous
>> patches,
>> 2.3. still looks ok.
>
> This is very bad. I'd appreciate a bisect if you can.
I must take this pa
On Wed, Apr 18, 2018 at 02:47:36PM +, Jean-Marc Lasgouttes wrote:
> Le 18/04/2018 à 16:45, Scott Kostyshak a écrit :
> > > Scott, I would be interested to know whether you can still reproduce the
> > > Spanish keyboard issue.
> >
> > Yes, I still see it with current master + your patch.
>
> O
Jean-Marc Lasgouttes wrote:
>>> Please test this experimental patch. It should cure the crash.
>> I can confirm that the crash is gone with this patch.
>
> It had better be gone, I removed the relevant code :) The question is
> whether cursor display is still OK.
I saw tiny glitch, but might be t
Le 18/04/2018 à 16:45, Scott Kostyshak a écrit :
Scott, I would be interested to know whether you can still reproduce the
Spanish keyboard issue.
Yes, I still see it with current master + your patch.
OK, what do you mean by Spanish keyboard? A physical Spanish keyboard or
the internal LyX ke
On Wed, Apr 18, 2018 at 08:47:59AM +, Jean-Marc Lasgouttes wrote:
> Le 17/04/2018 à 11:52, Jean-Marc Lasgouttes a écrit :
> > Sorry for being slow on this. As I understand it, the crash is related
> > to the new painting architecture and therefore probably exists in 2.3.x
> > too. This is the o
Le 18/04/2018 à 14:18, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 17/04/2018 ?? 11:52, Jean-Marc Lasgouttes a écrit :
Sorry for being slow on this. As I understand it, the crash is related to
the new painting architecture and therefore probably exists in 2.3.x too.
This is the one I n
Jean-Marc Lasgouttes wrote:
> Le 17/04/2018 ?? 11:52, Jean-Marc Lasgouttes a écrit :
>> Sorry for being slow on this. As I understand it, the crash is related to
>> the new painting architecture and therefore probably exists in 2.3.x too.
>> This is the one I need to fix first. I have an idea, bu
Pavel Sanda wrote:
> Hi JMarc,
>
> we likely have new crash related to the latest mathed cursor patch:
>
> 1. load the document (I will send privately though)
> 2. go to section 7.2, in the midst of paragraph there is last
There is something weird going on with our section counters.
When lyx cra
Le 17/04/2018 à 11:52, Jean-Marc Lasgouttes a écrit :
Sorry for being slow on this. As I understand it, the crash is related
to the new painting architecture and therefore probably exists in 2.3.x
too. This is the one I need to fix first. I have an idea, but I have to
see how it works. This sho
Le 06/04/2018 à 18:33, Pavel Sanda a écrit :
Hi JMarc,
we likely have new crash related to the latest mathed cursor patch:
1. load the document (I will send privately though)
2. go to section 7.2, in the midst of paragraph there is last
CA^{2+} in mathed, put the cursor just behind it
3.
no
On Mon, Apr 05, 2004 at 11:09:03AM +0100, Angus Leeming wrote:
> Here's one error,
Indeed. Thanks.
> Here, should you test nargs()?
> void MathScriptInset::notifyCursorLeaves(idx_type idx)
> {
> MathNestInset::notifyCursorLeaves(idx);
>
> // remove empty scripts if possible
> -
Andre Poenitz wrote:
>> I think this has been reported before...
>
> Indeed. And I haven't had time to fix it so far.
>
> The problem is most likely an off-by-one (or two) bug in accessing
> the cells of the script inset. A while ago, cell 0 was always the
> subscript, cell 1 the superscript and
On Sat, Apr 03, 2004 at 01:19:49PM +0200, Lars Gullik Bjønnes wrote:
>
> I think this has been reported before...
Indeed. And I haven't had time to fix it so far.
The problem is most likely an off-by-one (or two) bug in accessing the
cells of the script inset. A while ago, cell 0 was always the
Lars Gullik Bjønnes wrote:
> I think this has been reported before...
Aparently mathscriptinset is totally broken at the moment. Your report
is identical to mine.
--
Angus
17 matches
Mail list logo
