Am Dienstag, dem 05.09.2023 um 14:51 +0200 schrieb Pavel Sanda:
> I double checked that the problem I report with 2.3.7 is on Qt
> 5.15.7.
Plus that bug was on Windows, the new ones are on Mac. But the effect
is the same, signaling a mouse movement when the mouse didn't move.
--
Jürgen
--
Am Dienstag, dem 05.09.2023 um 14:04 +0200 schrieb Jean-Marc
Lasgouttes:
> The fix looks good in principle. How does this relate with the code
> at the beginning of GuiWorkArea::mouseMoveEvent?
Looks at least related. But it seems not the same bug, as this one is
said to be fixed in Qt 5.15.1
>
On Tue, Sep 05, 2023 at 02:39:43PM +0200, Jürgen Spitzmüller wrote:
> Looks at least related. But it seems not the same bug, as this one is
> said to be fixed in Qt 5.15.1
I double checked that the problem I report with 2.3.7 is on Qt 5.15.7.
Pavel
--
lyx-devel mailing list
Am Dienstag, dem 05.09.2023 um 15:12 +0200 schrieb Pavel Sanda:
> Actually, where do you read 5.15.1?
https://bugreports.qt.io/browse/QTBUG-85431
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Dienstag, dem 05.09.2023 um 15:21 +0200 schrieb Jürgen Spitzmüller:
> I agree that this is a good idea. Just wondering whether it should be
> done next to the current fix which does a bit more for inset buttons
> (see my other comment on why I like that).
Like this?
--
Jürgen
diff --git
On Mon, Sep 04, 2023 at 06:04:49PM +0200, Jürgen Spitzmüller wrote:
> Am Montag, dem 04.09.2023 um 17:51 +0200 schrieb Pavel Sanda:
> > I have limited access to that machine so the only testing point in my
> > hand is 2.3.7 + Qt 5.15 + Mac OS 12.6 (via homebrew).
>
> The fix is not in 2.3.x, so
On Tue, Sep 05, 2023 at 02:51:17PM +0200, Pavel Sanda wrote:
> On Tue, Sep 05, 2023 at 02:39:43PM +0200, Jürgen Spitzmüller wrote:
> > Looks at least related. But it seems not the same bug, as this one is
> > said to be fixed in Qt 5.15.1
>
> I double checked that the problem I report with 2.3.7
Am Dienstag, dem 05.09.2023 um 15:19 +0200 schrieb Jean-Marc
Lasgouttes:
> Indeed, this is why I thought we may want to have this
> unconditionally as early as possible; It cannot hurt, as I see it.
I agree that this is a good idea. Just wondering whether it should be
done next to the current fix
is at http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/.
We're still waiting for the Windows installer.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 05/09/2023 à 15:10, Jürgen Spitzmüller a écrit :
Am Dienstag, dem 05.09.2023 um 14:51 +0200 schrieb Pavel Sanda:
I double checked that the problem I report with 2.3.7 is on Qt
5.15.7.
Plus that bug was on Windows, the new ones are on Mac. But the effect
is the same, signaling a mouse
Am Dienstag, dem 05.09.2023 um 15:36 +0200 schrieb Jean-Marc
Lasgouttes:
> But I have to admit that I do not understand all the ramifications of
> doing this. I am ambivalent on the change, to be frank. We could just
> keep it in mind in case the issue reappears.
So be it, then.
--
Jürgen
--
Le 04/09/2023 à 16:39, Jürgen Spitzmüller a écrit :
Am Montag, dem 04.09.2023 um 16:31 +0200 schrieb Jean-Marc Lasgouttes:
Dear Devvies,
These last weeks I have seen without really thinking about them
several
macOS issues where mouse movement occurred when they should not.
I decided to search
Le 05/09/2023 à 15:27, Jürgen Spitzmüller a écrit :
Am Dienstag, dem 05.09.2023 um 15:21 +0200 schrieb Jürgen Spitzmüller:
I agree that this is a good idea. Just wondering whether it should be
done next to the current fix which does a bit more for inset buttons
(see my other comment on why I
Hello,
during the translation of the UI I found a string that, in my opinion, is not
clear enough about the feature is describes: showing changes of CT in output.
See the attached LyX file for an example.
Changes, if in order, should be made to the file
src/frontends/qt/ui/ChangeTrackingUi.ui
Am 05.09.2023 um 20:49 schrieb Pavel Sanda :
>
> On Mon, Sep 04, 2023 at 10:17:23PM +0100, José Matos wrote:
>> Attached is a one-line patch to fix the documentation (in this case
>> this can almost be applied manually). :-)
>
> It's in. Pavel
Just for the record - the translated variant w/o
On Mon, Sep 04, 2023 at 10:17:23PM +0100, José Matos wrote:
> Attached is a one-line patch to fix the documentation (in this case
> this can almost be applied manually). :-)
It's in. Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, Sep 05, 2023 at 09:17:09PM +0200, Dan wrote:
> during the translation of the UI I found a string that, in my opinion, is not
> clear enough about the feature is describes: showing changes of CT in output.
> See the attached LyX file for an example.
>
> Changes, if in order, should be
On Mon, Sep 04, 2023 at 05:51:46PM +0200, Pavel Sanda wrote:
> I have limited access to that machine so the only testing point in my hand is
> 2.3.7 + Qt 5.15 + Mac OS 12.6 (via homebrew).
> I might be able to get another data point about 2.4 beta 5 + Qt 5 + Mac Os
> 13.5 (via our provided dmg).
> during the translation of the UI I found a string that, in my opinion, is not
> clear enough about the feature is describes: showing changes of CT in output.
> See the attached LyX file for an example.
>
For some reason, I can not reproduce the behaviour described in the attached
file to my
Ideas?
Forwarded Message
Subject:Re: Can't open 2.4.0-beta5 doc in 2.4.0-beta3
Date: Tue, 5 Sep 2023 20:03:16 -0500
From: Christopher Menzel
To: Richard Kimberly Heck
CC: LyX Users
On 5 Sep 2023, at 5:01 PM, Richard Kimberly Heck wrote:
On 9/5/23
On Mon, 2023-09-04 at 23:50 +0200, Stephan Witt wrote:
> I think so.
Perfect. :-)
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
21 matches
Mail list logo
