Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 2/12/24 03:23, Léo de Souza wrote: On 10/02/2024 01:56, Richard Kimberly Heck wrote: Should be fixed for RC3, at 91bd457a. Riki I confirm that this is fixed in RC3. Thanks a lot. Thanks! Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org

Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 10/02/2024 01:56, Richard Kimberly Heck wrote: > Should be fixed for RC3, at 91bd457a. > > Riki I confirm that this is fixed in RC3. Thanks a lot. Léo -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 2/7/24 11:57, Richard Kimberly Heck wrote: On 2/7/24 04:41, Léo de Souza wrote: Hello, I would like to report that LyX doesn't show the correct reference in the work area for included listings when the option to do so is active. Environment: I compiled LyX 2.4.0~RC2 on Ubuntu 22.04 with

Re: Bug report: "Format cross-references in the work area" is incorrect for included listings

On 2/7/24 04:41, Léo de Souza wrote: Hello, I would like to report that LyX doesn't show the correct reference in the work area for included listings when the option to do so is active. Environment: I compiled LyX 2.4.0~RC2 on Ubuntu 22.04 with Qt6 enabled. Steps to reproduce: 1. Create a

Bug report: "Format cross-references in the work area" is incorrect for included listings

Hello, I would like to report that LyX doesn't show the correct reference in the work area for included listings when the option to do so is active. Environment: I compiled LyX 2.4.0~RC2 on Ubuntu 22.04 with Qt6 enabled. Steps to reproduce: 1. Create a new document: File > New 2. Open

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Am Freitag, dem 15.09.2023 um 16:23 +0200 schrieb Jürgen Spitzmüller: > Am Freitag, dem 15.09.2023 um 15:41 +0200 schrieb Thibaut Cuvelier: > > Your patch looks fine to me. > > > > It looks cumbersome, especially if we need to do that several > > times; > > maybe we could have a method at the

Re: [Bug Report] Encoding Problem on Windows 10 while Reconfiguring

On Mon, 2023-09-18 at 13:28 +0200, Pavel Sanda wrote: > Actually maybe the python default in lyx's windows release is now v3 > so we don't need to do anything... My thinking as well. :-) -- José Abílio -- lyx-devel mailing list lyx-devel@lists.lyx.org

Re: [Bug Report] Encoding Problem on Windows 10 while Reconfiguring

On Mon, Sep 18, 2023 at 01:25:34PM +0200, Pavel Sanda wrote: > On Mon, Sep 18, 2023 at 12:06:52PM +0100, José Matos wrote: > > On Mon, 2023-09-18 at 10:39 +0200, Pavel Sanda wrote: > > > Jose, does it mean that you propose patching Python source? Can't we > > > fix this ourselves? > > > Pavel > >

Re: [Bug Report] Encoding Problem on Windows 10 while Reconfiguring

On Mon, Sep 18, 2023 at 12:06:52PM +0100, José Matos wrote: > On Mon, 2023-09-18 at 10:39 +0200, Pavel Sanda wrote: > > Jose, does it mean that you propose patching Python source? Can't we > > fix this ourselves? > > Pavel > > This issue is discussed here. And now I understand why the need for >

Re: [Bug Report] Encoding Problem on Windows 10 while Reconfiguring

On Mon, 2023-09-18 at 10:39 +0200, Pavel Sanda wrote: > Jose, does it mean that you propose patching Python source? Can't we > fix this ourselves? > Pavel This issue is discussed here. And now I understand why the need for reload:

Re: [Bug Report] Encoding Problem on Windows 10 while Reconfiguring

On Sun, Sep 17, 2023 at 04:55:32PM +0100, José Matos wrote: > On Sun, 2023-09-17 at 11:48 +0800, Dai Longzhi ? wrote: > > How to fix: > > I found a way in Zhihu.com. It add this: > > import sys > > reload(sys) > > sys.setdefaultencoding("utf-8") > > in "C:\Program Files\LyX

Re: [Bug Report] Encoding Problem on Windows 10 while Reconfiguring

On Sun, 2023-09-17 at 11:48 +0800, Dai Longzhi 戴龙至 wrote: > How to fix: > I found a way in Zhihu.com. It add this: > import sys > reload(sys) > sys.setdefaultencoding("utf-8") > in "C:\Program Files\LyX 2.3\Python\Lib\subprocess.py". Then the > Reconfiguring works. > > I am not sure someone will

[Bug Report] Encoding Problem on Windows 10 while Reconfiguring

Bacis Info Reproduce:   System: Windows 10 22H2 64-bit System Language is Chinese (Simplified)   Lyx: Fresh new installed LyX Version 2.3.7 with Texlive full-installed   Path to Install: C:\Program Files\LyX 2.3\ # (Non-Chinese Path) Debug message: 11:09:54.257:

[Bug Report] Encoding Problem on Windows 10 while Reconfiguring

Bacis Info Reproduce:   System: Windows 10 22H2 64-bit System Language is Chinese (Simplified)   Lyx: Fresh new installed LyX Version 2.3.7 with Texlive full-installed   Path to Install: C:\Program Files\LyX 2.3\ # (Non-Chinese Path) Debug message: 11:09:54.257:

Re: Bug report: Nomenclature no longer works on LyX 2.4.0 beta 5

Am Mittwoch, dem 13.09.2023 um 14:45 +0200 schrieb Léo de Souza: > I would like to report that the nomenclature function no longer works > for me on LyX 2.4.0 beta 5. Thanks. Confirmed and fixed in master. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Le 15/09/2023 à 16:23, Jürgen Spitzmüller a écrit : (Wasn't this bug caught at some point by a static analyser? It seems to be a too common error in C++ for it to slip through.) Apparently not. Coverity scan only tags this if in some other places of the code there is a test for a null

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Am Freitag, dem 15.09.2023 um 15:41 +0200 schrieb Thibaut Cuvelier: > Your patch looks fine to me. > > It looks cumbersome, especially if we need to do that several times; > maybe we could have a method at the inset level, say > getLocalFontOrDefault(const OutputParams&), to return either >

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

On Fri, 15 Sept 2023 at 11:36, Jürgen Spitzmüller wrote: > Am Freitag, dem 15.09.2023 um 10:45 +0200 schrieb Léo de Souza: > > 1. Create new document: File > New > > 2. Insert label: Insert > Label... > > 3. On a new line, switch layout to "Labeling" or "Description" > > 4. Insert

Re: Bug-report - LyX crash

Am 15.09.2023 um 15:26 schrieb Jean-Marc Lasgouttes : > > Le 15/09/2023 à 13:18, Stephan Witt a écrit : >>> To me, this looks like this one: >>> https://www.lyx.org/trac/ticket/12818 >>> >>> We have a problem on macOS with the interpretation of the return values of >>> QMessageBox. >>> >>> I

Re: Bug-report - LyX crash

Le 15/09/2023 à 13:18, Stephan Witt a écrit : To me, this looks like this one: https://www.lyx.org/trac/ticket/12818 We have a problem on macOS with the interpretation of the return values of QMessageBox. I see the patch there is not backported to 2.3.x. Is this normal? I think it’s not

Re: Bug-report - LyX crash

Am 15.09.2023 um 11:44 schrieb Jean-Marc Lasgouttes : > > Le 15/09/2023 à 11:40, luxhacker a écrit : >> Hi Pavel, >> Please create an account for me. I am very interested in LyX. >> It's difficult to reproduce or seize a problem without knowing anything >> about it. >> When looking at the stack,

Re: Bug-report - LyX crash

On Fri, Sep 15, 2023 at 09:40:08AM +, luxhacker wrote: > Please create an account for me. I am very interested in LyX. done. p -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Bug-report - LyX crash

Le 15/09/2023 à 11:40, luxhacker a écrit : Hi Pavel, Please create an account for me. I am very interested in LyX. It's difficult to reproduce or seize a problem without knowing anything about it. When looking at the stack, I get - perhaps wrongly - the impression it's user-interface

Re: Bug-report - LyX crash

, September 15th, 2023 at 11:18 AM, Pavel Sanda wrote: > On Fri, Sep 15, 2023 at 06:39:22AM +, luxhacker wrote: > > > New to LyX and appreciating it ! found no way to register. Is this ok ? > > therefore mailing bug report > > > It's ok. I can create the account if you are

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Am Freitag, dem 15.09.2023 um 10:45 +0200 schrieb Léo de Souza: > 1. Create new document: File > New > 2. Insert label: Insert > Label... > 3. On a new line, switch layout to "Labeling" or "Description" > 4. Insert cross-reference: Insert > Cross-Reference... > 5. Try copying this cross-reference

Re: Bug-report - LyX crash

On Fri, Sep 15, 2023 at 06:39:22AM +, luxhacker wrote: > New to LyX and appreciating it ! found no way to register. Is this ok ? > therefore mailing bug report It's ok. I can create the account if you are interested. > What I do before ;) ? > > Immediately when crashing,

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Can repeat on Mac Ventura 13.5.2. /Anders > On 15 Sep 2023, at 10:45, Léo de Souza wrote: > > Hello, > > I would like to report that LyX crashes with SIGSEGV when copying a cross > reference from a "labeled list" or "description" layout on LyX 2.4.0 beta 5. > > Environment: > > I compiled

Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Hello, I would like to report that LyX crashes with SIGSEGV when copying a cross reference from a "labeled list" or "description" layout on LyX 2.4.0 beta 5. Environment: I compiled LyX 2.4.0 beta 5 on Ubuntu 22.04 with Qt6 enabled and my Tex Live install is up to date. Steps to reproduce:

Bug-report - LyX crash

Dear All, New to LyX and appreciating it ! found no way to register. Is this ok ? therefore mailing bug report Please find hereafter a crash of the LyX-system: (  1) 1   lyx                                 0x00010bde4ddd

Bug report: Nomenclature no longer works on LyX 2.4.0 beta 5

Hi, I would like to report that the nomenclature function no longer works for me on LyX 2.4.0 beta 5. Environment: I compiled LyX 2.4.0 beta 5 on Ubuntu 22.04 with Qt6 enabled and my Tex Live install is up to date. Steps to reproduce: 1. Create new document: File > New 2. Insert

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

On Tue, Jul 18, 2023 at 10:04:03PM +0200, Christoph Schmitz wrote: > In the meantime, this problem has been fixed. However, due to a compiler > error, I can currently no longer compile LyX on macOS. Fixed where? We did not commit the fix yet. (But perhaps you don't use Qt 6.3.1 on platform

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

In the meantime, this problem has been fixed. However, due to a compiler error, I can currently no longer compile LyX on macOS. > Am 18.07.2023 um 16:25 schrieb LyX Ticket Tracker : > > #12576: [Bug report] "Insert graphics" does not work an

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

Hello skostysh, Sorry, I did not know that. Best wishes, Chris > Am 28.10.2022 um 17:50 schrieb LyX Ticket Tracker : > > #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev] > -+- > Reporter

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

Yes, I am. Von meinem iPhone gesendet > Am 27.10.2022 um 21:40 schrieb LyX Ticket Tracker : > > #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev] > -+- > Reporter: docc | Owner: lasgo

Re: [Bug report] "Insert graphics" does not work anymore

On Mon, Oct 10, 2022 at 05:06:20PM +0200, Christoph Schmitz wrote: > For some time now, "Insert graphics" no longer works in my self-compiled > version of LyX 2.4. The window opens and I can search for a file. When I > click on "Open", the window disappears, but the graphic file is not inserted.

[Bug report] "Insert graphics" does not work anymore

For some time now, "Insert graphics" no longer works in my self-compiled version of LyX 2.4. The window opens and I can search for a file. When I click on "Open", the window disappears, but the graphic file is not inserted. It seems to be a problem with the "file picker". If I enter the Unix

Re: Bug Report for LYX.

On Tue, Aug 07, 2018 at 11:36:56AM -0400, Scott Kostyshak wrote: > On Tue, Aug 07, 2018 at 08:32:39AM +, Valmikanathan S wrote: > > Hi, > > > > > > > > Please update the details on how to install with sequence and packages to > > install for engineering mathematics and mathematical

Re: Bug Report for LYX.

On Tue, Aug 07, 2018 at 08:32:39AM +, Valmikanathan S wrote: > Hi, > > > > Please update the details on how to install with sequence and packages to > install for engineering mathematics and mathematical drawing. > > > > I am attaching the bug Hi Valmikanathan, can you please send a

Bug Report for LYX.

Hi, Please update the details on how to install with sequence and packages to install for engineering mathematics and mathematical drawing. I am attaching the bug When I try to export to pdf from LYX after typing the mathematics 12th grade exam papers.

Re: Bug report

lost any data. > Please read the bug-reporting instructions in 'Help->Introduction' and send > us a bug report, if necessary. Thanks! > Bye. > Error: LyX crashed! > > SIGSEGV signal caught! > Sorry, you have found a bug in LyX, hope y

Bug report

Linux Mint 18.1, compiled from the official sources 2.2.2. /home/jb/newfile1.lyx.emergency lyx: SIGSEGV signal caught! Sorry, you have found a bug in LyX, hope you have not lost any data. Please read the bug-reporting instructions in 'Help->Introduction' and send us a bug report, if necess

Re: Advanced search bug report

you have found a bug. Also, in *any* bug report, please always give details on your operating system and the version of software that you're using. In this case, what is your OS and what version of LyX do you use? Also, when I first open LyX and recall the advanced search, it pops up a very

Re: Advanced search bug report

bug. So please keep trying if you think you have found a bug. Also, in *any* bug report, please always give details on your operating system and the version of software that you're using. In this case, what is your OS and what version of LyX do you use? > Also, when I first open LyX and recall t

Advanced search bug report

Hello, First of all, thank you guys for the wonderful program. I guess I found a bug regarding the advanced search. After I tried to search for a math expression several times, when I clicked the advanced search button, it pops up an empty window. Also, when I first open LyX and recall the

Advanced search bug report

Hello, First of all, thank you guys for the wonderful program. I guess I found a bug regarding the advanced search. After I tried to search for a math expression several times, when I clicked the advanced search button, it pops up an empty window. Also, when I first open LyX and recall the

Re: #9028: Bug report of replace feature

On 03/09/2014 10:44 PM, Tommaso Cucinotta wrote: On 10/03/14 02:27, LyX Ticket Tracker wrote: About update, I have a question: would it reset my preference setting? Cause I spent a lot of time to set LyX, like fonts, output form, etc. The most annoying side effect, if you update, is that

Re: #9028: Bug report of replace feature

On 03/09/2014 10:44 PM, Tommaso Cucinotta wrote: On 10/03/14 02:27, LyX Ticket Tracker wrote: About update, I have a question: would it reset my preference setting? Cause I spent a lot of time to set LyX, like fonts, output form, etc. The most annoying side effect, if you update, is that

Re: #9028: Bug report of replace feature

On 10/03/14 02:27, LyX Ticket Tracker wrote: About update, I have a question: would it reset my preference setting? Cause I spent a lot of time to set LyX, like fonts, output form, etc. The most annoying side effect, if you update, is that the new version of LyX saves files with an updated

Re: #9028: Bug report of replace feature

On 10/03/14 02:27, LyX Ticket Tracker wrote: > About update, I have a question: would it reset my preference setting? > Cause I spent a lot of time to set LyX, like fonts, output form, etc. The most annoying side effect, if you update, is that the new version of LyX saves files with an updated

Re: Bug report of replace feature

\} _{k=1:K}}\hfill Now, I want to replace the code \hfill to a, but when I use the find/repace feature, LyX will stop working suddenly. Hi Yu Fei, Thanks for the report. This is the documentation list. I'm forwarding your bug report to the developer list. Best, Scott

Re: Bug report of replace feature

atorname{diag}{\left\{ {e^{{\alpha_{k\right\} > _{k=1:K}}\hfill > > Now, I want to replace the code "\hfill" to "a", but when I use the > "find/repace" feature, LyX will stop working suddenly. Hi Yu Fei, Thanks for the report. This is the documentation list. I'm forwarding your bug report to the developer list. Best, Scott

Re: Patch for 2.0.7 on OSX [was Re: bug report]

16/01/2014 15:29, Stephan Witt: Affecting more code is not a problem IMO. Does the createView() flash a window on the screen? Yes, but it doesn't flash, it remains open. After all, it's a work around. :( The proper solution requires the handling of e.g. Preferences in GuiApplication. Agreed

Re: Patch for 2.0.7 on OSX [was Re: bug report]

On 01/20/2014 09:01 AM, Jean-Marc Lasgouttes wrote: 16/01/2014 15:29, Stephan Witt: Affecting more code is not a problem IMO. Does the createView() flash a window on the screen? Yes, but it doesn't flash, it remains open. After all, it's a work around. :( The proper solution requires the

Re: Patch for 2.0.7 on OSX [was Re: bug report]

Am 20.01.2014 um 17:26 schrieb Richard Heck rgh...@lyx.org: On 01/20/2014 09:01 AM, Jean-Marc Lasgouttes wrote: 16/01/2014 15:29, Stephan Witt: Affecting more code is not a problem IMO. Does the createView() flash a window on the screen? Yes, but it doesn't flash, it remains open. After

Re: Patch for 2.0.7 on OSX [was Re: bug report]

16/01/2014 15:29, Stephan Witt: Affecting more code is not a problem IMO. Does the createView() flash a window on the screen? Yes, but it doesn't flash, it remains open. After all, it's a work around. :( The proper solution requires the handling of e.g. Preferences in GuiApplication. Agreed

Re: Patch for 2.0.7 on OSX [was Re: bug report]

On 01/20/2014 09:01 AM, Jean-Marc Lasgouttes wrote: 16/01/2014 15:29, Stephan Witt: Affecting more code is not a problem IMO. Does the createView() flash a window on the screen? Yes, but it doesn't flash, it remains open. After all, it's a work around. :( The proper solution requires the

Re: Patch for 2.0.7 on OSX [was Re: bug report]

Am 20.01.2014 um 17:26 schrieb Richard Heck : > On 01/20/2014 09:01 AM, Jean-Marc Lasgouttes wrote: >> 16/01/2014 15:29, Stephan Witt: Affecting more code is not a problem IMO. Does the createView() flash a window on the screen? >>> >>> Yes, but it doesn't flash, it

Re: Patch for 2.0.7 on OSX [was Re: bug report]

16/01/2014 07:32, Stephan Witt: Attached is a patch to work around a bug with crash on view close on Mac OSX. See also https://bugreports.qt-project.org/browse/QTBUG-25399 Is anyone able to verify or comment it? I am unfortunately no in a position to test it out. My only comment is that the

Re: Patch for 2.0.7 on OSX [was Re: bug report]

Am 16.01.2014 um 10:49 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: 16/01/2014 07:32, Stephan Witt: Attached is a patch to work around a bug with crash on view close on Mac OSX. See also https://bugreports.qt-project.org/browse/QTBUG-25399 Is anyone able to verify or comment it? I am

Re: Patch for 2.0.7 on OSX [was Re: bug report]

16/01/2014 13:23, Stephan Witt: The dispatch and getstatus calls are made for application first and the for the view. The platform doesn't matter here. It's different for a Mac to have a menu bar without any view. But you're right if you meant to say it works on any platform. I thought that

Re: Patch for 2.0.7 on OSX [was Re: bug report]

Am 16.01.2014 um 14:37 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: 16/01/2014 13:23, Stephan Witt: The dispatch and getstatus calls are made for application first and the for the view. The platform doesn't matter here. It's different for a Mac to have a menu bar without any view. But

Re: Patch for 2.0.7 on OSX [was Re: bug report]

16/01/2014 07:32, Stephan Witt: Attached is a patch to work around a bug with crash on view close on Mac OSX. See also https://bugreports.qt-project.org/browse/QTBUG-25399 Is anyone able to verify or comment it? I am unfortunately no in a position to test it out. My only comment is that the

Re: Patch for 2.0.7 on OSX [was Re: bug report]

Am 16.01.2014 um 10:49 schrieb Jean-Marc Lasgouttes : > 16/01/2014 07:32, Stephan Witt: >> Attached is a patch to work around a bug with crash on view close on Mac OSX. >> See also https://bugreports.qt-project.org/browse/QTBUG-25399 >> >> Is anyone able to verify or comment

Re: Patch for 2.0.7 on OSX [was Re: bug report]

16/01/2014 13:23, Stephan Witt: The dispatch and getstatus calls are made for application first and the for the view. The platform doesn't matter here. It's different for a Mac to have a menu bar without any view. But you're right if you meant to say it works on any platform. I thought that

Re: Patch for 2.0.7 on OSX [was Re: bug report]

Am 16.01.2014 um 14:37 schrieb Jean-Marc Lasgouttes : > 16/01/2014 13:23, Stephan Witt: >> The dispatch and getstatus calls are made for application first and the for >> the view. >> The platform doesn't matter here. >> It's different for a Mac to have a menu bar without any

2.0.7 on OSX [was Re: bug report]

Where do we stand now with 2.0.7 on Mac? Richard On 01/07/2014 03:30 AM, Stephan Witt wrote: Am 06.01.2014 um 16:58 schrieb Richard Heck rgh...@lyx.org: On 01/06/2014 02:37 AM, Stephan Witt wrote: Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 05/01/2014

Re: 2.0.7 on OSX [was Re: bug report]

Am 15.01.2014 um 16:04 schrieb Richard Heck rgh...@lyx.org: Where do we stand now with 2.0.7 on Mac? I'd appreciate some feedback for by patch. Without this patch LyX (Cocoa-build) crashes while closing the 2nd GuiView instance. LyX 2.0.6 was Cocoa based and I don't want to change that.

Re: 2.0.7 on OSX [was Re: bug report]

On 01/15/2014 10:14 AM, Stephan Witt wrote: Am 15.01.2014 um 16:04 schrieb Richard Heck rgh...@lyx.org: Where do we stand now with 2.0.7 on Mac? I'd appreciate some feedback for by patch. Without this patch LyX (Cocoa-build) crashes while closing the 2nd GuiView instance. LyX 2.0.6 was Cocoa

Patch for 2.0.7 on OSX [was Re: bug report]

Attached is a patch to work around a bug with crash on view close on Mac OSX. See also https://bugreports.qt-project.org/browse/QTBUG-25399 Is anyone able to verify or comment it? Stephan Am 15.01.2014 um 18:22 schrieb Richard Heck rgh...@lyx.org: On 01/15/2014 10:14 AM, Stephan Witt wrote:

2.0.7 on OSX [was Re: bug report]

Where do we stand now with 2.0.7 on Mac? Richard On 01/07/2014 03:30 AM, Stephan Witt wrote: Am 06.01.2014 um 16:58 schrieb Richard Heck : On 01/06/2014 02:37 AM, Stephan Witt wrote: Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes : Le 05/01/2014

Re: 2.0.7 on OSX [was Re: bug report]

Am 15.01.2014 um 16:04 schrieb Richard Heck : > Where do we stand now with 2.0.7 on Mac? I'd appreciate some feedback for by patch. Without this patch LyX (Cocoa-build) crashes while closing the 2nd GuiView instance. LyX 2.0.6 was Cocoa based and I don't want to change that.

Re: 2.0.7 on OSX [was Re: bug report]

On 01/15/2014 10:14 AM, Stephan Witt wrote: Am 15.01.2014 um 16:04 schrieb Richard Heck : Where do we stand now with 2.0.7 on Mac? I'd appreciate some feedback for by patch. Without this patch LyX (Cocoa-build) crashes while closing the 2nd GuiView instance. LyX 2.0.6 was

Patch for 2.0.7 on OSX [was Re: bug report]

Attached is a patch to work around a bug with crash on view close on Mac OSX. See also https://bugreports.qt-project.org/browse/QTBUG-25399 Is anyone able to verify or comment it? Stephan Am 15.01.2014 um 18:22 schrieb Richard Heck : > On 01/15/2014 10:14 AM, Stephan Witt

Re: bug report

Am 07.01.2014 um 09:30 schrieb Stephan Witt st.w...@gmx.net: Am 06.01.2014 um 16:58 schrieb Richard Heck rgh...@lyx.org: On 01/06/2014 02:37 AM, Stephan Witt wrote: Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 05/01/2014 21:35, Stephan Witt a écrit : This

Re: bug report

Am 07.01.2014 um 09:30 schrieb Stephan Witt : > Am 06.01.2014 um 16:58 schrieb Richard Heck : > >> On 01/06/2014 02:37 AM, Stephan Witt wrote: >>> Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes : >>> Le 05/01/2014 21:35, Stephan

Re: bug report

Am 06.01.2014 um 16:58 schrieb Richard Heck rgh...@lyx.org: On 01/06/2014 02:37 AM, Stephan Witt wrote: Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs: If you want all windows

Re: bug report

Am 06.01.2014 um 16:58 schrieb Richard Heck : > On 01/06/2014 02:37 AM, Stephan Witt wrote: >> Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes : >> >>> Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs:

Re: bug report

On 01/06/2014 02:37 AM, Stephan Witt wrote: Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs: If you want all windows in a Mac application to share one menu bar, you must create a

Re: bug report

On 01/06/2014 02:37 AM, Stephan Witt wrote: Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes : Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs: "If you want all windows in a Mac application to share one menu bar, you must create a

Re: bug report

Am 05.01.2014 um 00:18 schrieb Scott Kostyshak skost...@lyx.org: On Thu, Jan 2, 2014 at 10:49 AM, Stephan Witt st.w...@gmx.net wrote: There are no messages. LyX 2.0.7 is affected too on my system. It looks like the problem is a run-time effect and QFontMetrics::maxWidth() is the culprit.

Re: bug report

On Sun, Jan 5, 2014 at 6:42 AM, Stephan Witt st.w...@gmx.net wrote: Am 05.01.2014 um 00:18 schrieb Scott Kostyshak skost...@lyx.org: On Thu, Jan 2, 2014 at 10:49 AM, Stephan Witt st.w...@gmx.net wrote: There are no messages. LyX 2.0.7 is affected too on my system. It looks like the problem

Re: bug report

On 01/04/2014 04:32 PM, Stephan Witt wrote: Am 04.01.2014 um 17:35 schrieb Richard Heck rgh...@lyx.org: On 01/04/2014 07:14 AM, Jürgen Spitzmüller wrote: Stephan Witt wrote: Did you possibly try the patch on Linux? Yes. I cannot see a problem with the patch. Agreed. Go ahead and apply, and

Re: bug report

Le 04/01/2014 22:32, Stephan Witt a écrit : But sorry, now I have another unrelated problem, unfortunately. It's a really old one: when repeatedly open and close the main window LyX crashes in Qt-menu-code. There are references to this problem here: * http://www.lyx.org/trac/ticket/7959 *

Re: bug report

Am 05.01.2014 um 20:36 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 04/01/2014 22:32, Stephan Witt a écrit : But sorry, now I have another unrelated problem, unfortunately. It's a really old one: when repeatedly open and close the main window LyX crashes in Qt-menu-code. There are

Re: bug report

Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs: If you want all windows in a Mac application to share one menu bar, you must create a menu bar that does not have a parent. Create a parent-less menu bar this way: QMenuBar *menuBar = new QMenuBar(0);

Re: bug report

Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs: If you want all windows in a Mac application to share one menu bar, you must create a menu bar that does not have a parent. Create

Re: bug report

Am 05.01.2014 um 00:18 schrieb Scott Kostyshak : > On Thu, Jan 2, 2014 at 10:49 AM, Stephan Witt wrote: > >> There are no messages. LyX 2.0.7 is affected too on my system. >> It looks like the problem is a run-time effect and QFontMetrics::maxWidth() >> is the

Re: bug report

On Sun, Jan 5, 2014 at 6:42 AM, Stephan Witt wrote: > Am 05.01.2014 um 00:18 schrieb Scott Kostyshak : > >> On Thu, Jan 2, 2014 at 10:49 AM, Stephan Witt wrote: >> >>> There are no messages. LyX 2.0.7 is affected too on my system. >>> It looks

Re: bug report

On 01/04/2014 04:32 PM, Stephan Witt wrote: Am 04.01.2014 um 17:35 schrieb Richard Heck : On 01/04/2014 07:14 AM, Jürgen Spitzmüller wrote: Stephan Witt wrote: Did you possibly try the patch on Linux? Yes. I cannot see a problem with the patch. Agreed. Go ahead and apply,

Re: bug report

Le 04/01/2014 22:32, Stephan Witt a écrit : But sorry, now I have another unrelated problem, unfortunately. It's a really old one: when repeatedly open and close the main window LyX crashes in Qt-menu-code. There are references to this problem here: * http://www.lyx.org/trac/ticket/7959 *

Re: bug report

Am 05.01.2014 um 20:36 schrieb Jean-Marc Lasgouttes : > Le 04/01/2014 22:32, Stephan Witt a écrit : >> But sorry, now I have another unrelated problem, unfortunately. >> It's a really old one: when repeatedly open and close the main window >> LyX crashes in Qt-menu-code. There

Re: bug report

Le 05/01/2014 21:35, Stephan Witt a écrit : This looks interesting - from the Qt docs: "If you want all windows in a Mac application to share one menu bar, you must create a menu bar that does not have a parent. Create a parent-less menu bar this way: QMenuBar *menuBar = new QMenuBar(0);

Re: bug report

Am 05.01.2014 um 22:28 schrieb Jean-Marc Lasgouttes : > Le 05/01/2014 21:35, Stephan Witt a écrit : >> This looks interesting - from the Qt docs: >> >> "If you want all windows in a Mac application to share one menu bar, you >> must create a menu bar that does not have a

Re: bug report

Am 03.01.2014 um 17:14 schrieb Jürgen Spitzmüller sp...@lyx.org: Richard Heck wrote: I guess we'd better hold 2.0.7 until this is fixed Stephan's workaround seems to be just fine for that purpose. At least it looks innocent enough. I didn't find another solution until now.

Re: bug report

Stephan Witt wrote: Did you possibly try the patch on Linux? Yes. I cannot see a problem with the patch. Regards, Jürgen

Re: bug report

On 01/04/2014 07:14 AM, Jürgen Spitzmüller wrote: Stephan Witt wrote: Did you possibly try the patch on Linux? Yes. I cannot see a problem with the patch. Agreed. Go ahead and apply, and send me the corrected binary when it is ready. I'll rebuild the source packages. rh

Re: bug report

Am 04.01.2014 um 17:35 schrieb Richard Heck rgh...@lyx.org: On 01/04/2014 07:14 AM, Jürgen Spitzmüller wrote: Stephan Witt wrote: Did you possibly try the patch on Linux? Yes. I cannot see a problem with the patch. Agreed. Go ahead and apply, and send me the corrected binary when it is

Re: bug report

On Thu, Jan 2, 2014 at 10:49 AM, Stephan Witt st.w...@gmx.net wrote: There are no messages. LyX 2.0.7 is affected too on my system. It looks like the problem is a run-time effect and QFontMetrics::maxWidth() is the culprit. The attached patch helps. But I don't know if there is another

Re: bug report

Am 03.01.2014 um 17:14 schrieb Jürgen Spitzmüller : > Richard Heck wrote: >> I guess we'd better hold 2.0.7 until this is fixed > > Stephan's workaround seems to be just fine for that purpose. At least it > looks > innocent enough. I didn't find another solution until now.

Re: bug report

Stephan Witt wrote: > Did you possibly try the patch on Linux? Yes. I cannot see a problem with the patch. Regards, Jürgen

  1   2   3   4   5   6   7   8   9   10   >