On 9/13/23 02:56, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 13.09.2023 um 08:51 +0200 schrieb Pavel Sanda:
Hopefully, this is fixed now. Juergen, how straightforward would be
backporting for 2.3.x? I think this one deserves it.
Not completely straightforward, but doable, I think.
OK by me.
Am Mittwoch, dem 13.09.2023 um 08:51 +0200 schrieb Pavel Sanda:
> Hopefully, this is fixed now. Juergen, how straightforward would be
> backporting for 2.3.x? I think this one deserves it.
Not completely straightforward, but doable, I think.
--
Jürgen
--
lyx-devel mailing list
On Tue, Sep 05, 2023 at 07:57:55PM +0200, Pavel Sanda wrote:
> I would ask all reportes in trac whether they can reproduce with beta5
> and unless we obtain new complaint, we should tentatively consider it
> solved...
Hopefully, this is fixed now. Juergen, how straightforward would be
backporting
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).
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 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
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
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
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: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
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 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
--
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 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
>
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
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
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 we only know it works if someone can check
master or beta5.
--
Jürgen
--
On Mon, Sep 04, 2023 at 05:29:35PM +0200, Jürgen Spitzmüller wrote:
> Am Montag, dem 04.09.2023 um 17:10 +0200 schrieb Pavel Sanda:
> > The problem is that I see #12820 on Qt 5 while we try
> > to avoid releasing with Qt 6 because of #12641.
>
> You see this bug with current master? This would be
Am Montag, dem 04.09.2023 um 17:10 +0200 schrieb Pavel Sanda:
> The problem is that I see #12820 on Qt 5 while we try
> to avoid releasing with Qt 6 because of #12641.
You see this bug with current master? This would be bad.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Mon, Sep 04, 2023 at 04:39:13PM +0200, Jürgen Spitzmüller wrote:
> > I decided to search Qt bugs about that and voil??!:
> > https://bugreports.qt.io/browse/QTBUG-70
> >
> > This bug has been fixed in Qt 6.5. It is not clear whether it existed
> > in 5.x.
> >
> > Does this ring a bell?
I
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 Qt bugs about that and voilà!:
>
21 matches
Mail list logo
