Re: LyX+Qt5 build (CMake+XCode) on OS X

automatically by Qt. If someone wants to check this, see the attached patch, which includes all changes (but does not solve issue 1)). Patrick De Visschere Qt5-fix-Q_WS_MACX+GlobalMenuBar.diff Hi Patrick, the GlobalMenuBar() thing is a wonderful idea! I'm struggling since a while

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 19 Aug, 2014, at 14:12 , Stephan Witt st.w...@gmx.net wrote: Am 17.08.2014 um 20:13 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 15 Aug, 2014, at 13:57 , Stephan Witt st.w...@gmx.net wrote: Am 12.08.2014 um 22:07 schrieb pdv pdvissch...@edpnet.be: As a follow-up on reports

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 08:40 , Stephan Witt st.w...@gmx.net wrote: Am 19.08.2014 um 22:41 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 19 Aug, 2014, at 14:12 , Stephan Witt st.w...@gmx.net wrote: Am 17.08.2014 um 20:13 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 15

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 11:22 , Stephan Witt st.w...@gmx.net wrote: Am 19.08.2014 um 22:41 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 19 Aug, 2014, at 14:12 , Stephan Witt st.w...@gmx.net wrote: Am 17.08.2014 um 20:13 schrieb Patrick De Visschere pdvissch...@edpnet.be: My

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 22:40 , Stephan Witt st.w...@gmx.net wrote: Am 20.08.2014 um 20:46 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 20 Aug, 2014, at 08:40 , Stephan Witt st.w...@gmx.net wrote: Am 19.08.2014 um 22:41 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 19

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 23:15 , Stephan Witt st.w...@gmx.net wrote: Am 20.08.2014 um 22:45 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 20 Aug, 2014, at 11:22 , Stephan Witt st.w...@gmx.net wrote: Am 19.08.2014 um 22:41 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 19

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 23 Aug, 2014, at 14:50 , Stephan Witt st.w...@gmx.net wrote: Am 23.08.2014 um 12:01 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 20 Aug, 2014, at 23:15 , Stephan Witt st.w...@gmx.net wrote: Am 20.08.2014 um 22:45 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 20

Re: LyX+Qt5 build (CMake+XCode) on OS X

Sent from my iPad On 25 Aug 2014, at 07:55, Stephan Witt st.w...@gmx.net wrote: Am 23.08.2014 um 18:01 schrieb Patrick De Visschere pdvissch...@edpnet.be: On 23 Aug, 2014, at 14:50 , Stephan Witt st.w...@gmx.net wrote: Am 23.08.2014 um 12:01 schrieb Patrick De Visschere pdvissch

Re: LyX+Qt5 build (CMake+XCode) on OS X

enu, but the latter also happens >> in LyX211 and may not be related to Qt5). Building LyX + Qt4.8.6 confirms >> that GlobalMenuBar's event() is not called when issuing a shortcut with no >> window present. I assume that these standard mac-shortcuts are handled >> automat

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 19 Aug, 2014, at 14:12 , Stephan Witt <st.w...@gmx.net> wrote: > Am 17.08.2014 um 20:13 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: > >> On 15 Aug, 2014, at 13:57 , Stephan Witt <st.w...@gmx.net> wrote: >> >>> Am 12.08.201

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 08:40 , Stephan Witt <st.w...@gmx.net> wrote: > Am 19.08.2014 um 22:41 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: > >> >> On 19 Aug, 2014, at 14:12 , Stephan Witt <st.w...@gmx.net> wrote: >> >>> Am 17.08.2

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 11:22 , Stephan Witt <st.w...@gmx.net> wrote: > Am 19.08.2014 um 22:41 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: > >> On 19 Aug, 2014, at 14:12 , Stephan Witt <st.w...@gmx.net> wrote: >> >>> Am 17.08.2014 um

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 22:40 , Stephan Witt <st.w...@gmx.net> wrote: > Am 20.08.2014 um 20:46 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: > >> On 20 Aug, 2014, at 08:40 , Stephan Witt <st.w...@gmx.net> wrote: >> >>> Am 19.08.2014 um

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 20 Aug, 2014, at 23:15 , Stephan Witt <st.w...@gmx.net> wrote: > Am 20.08.2014 um 22:45 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: > >> On 20 Aug, 2014, at 11:22 , Stephan Witt <st.w...@gmx.net> wrote: >> >>> Am 19.08.2014 um

Re: LyX+Qt5 build (CMake+XCode) on OS X

On 23 Aug, 2014, at 14:50 , Stephan Witt <st.w...@gmx.net> wrote: > Am 23.08.2014 um 12:01 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: > >> On 20 Aug, 2014, at 23:15 , Stephan Witt <st.w...@gmx.net> wrote: >> >>> Am 20.08.2014 um

Re: LyX+Qt5 build (CMake+XCode) on OS X

Sent from my iPad > On 25 Aug 2014, at 07:55, Stephan Witt <st.w...@gmx.net> wrote: > >> Am 23.08.2014 um 18:01 schrieb Patrick De Visschere <pdvissch...@edpnet.be>: >> >>> On 23 Aug, 2014, at 14:50 , Stephan Witt <st.w...@gmx.net> wrote: >&g

Re: LyX-Workarea: Background not shown correctly

I’ve done some more debugging and I believe I’ve found the Qt code that turns the background black or white. Om macos (and probably also on windows) Qt uses a QBackingStore for painting. I couldn’t find a QPlatformBackingStore for linux so I assume the implementation is different on linux,

Re: LyX-Workarea: Background not shown correctly

> On 16 Oct 2017, at 11:41, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > > Le 13/10/2017 à 11:00, Patrick De Visschere a écrit : >> But I see your point; >> When I remove the line setting WA_OpaquePaintEvent the problem remains but >> (most of) the

Re: LyX-Workarea: Background not shown correctly

> On 12 Oct 2017, at 21:30, Jean-Marc Lasgouttes wrote: > > Le 08/10/2017 à 18:57, pdv a écrit : >> The new code contains twice a viewport()->update() without specification of >> a rectangle. Since > Qt normally erases the widget's area before the >> paintEvent() call >> I

Re: LyX-Workarea: Background not shown correctly

> On 22 Oct 2017, at 23:11, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > > Le 21 octobre 2017 14:56:36 GMT+02:00, Patrick De Visschere > <pdvissch...@edpnet.be> a écrit : >> Jean-Marc, >> >> This works because every update is turned into a FullSc

Re: LyX-Workarea: Background not shown correctly

This works as far as I can see. > On 19 Oct 2017, at 17:34, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > > Le 16/10/2017 à 14:48, Patrick De Visschere a écrit : >> I’ve defined a watchpoint on what I believe is the backingstore image and >> this

Re: LyX-Workarea: Background not shown correctly

> > Can you try to set/unset documentMode in DragTabBar::DragTabBar and see what > it does? > > JMarc I’ve inserted setDocumentMode(true/false); and it doesn’t make any difference. I’ve then set breakpoints in : QCocoaNativeInterface::setContentBorderEnabled(QWindow *window, bool enable)

Re: LyX-Workarea: Background not shown correctly

> On 25 Oct 2017, at 12:21, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > > Le 23/10/2017 à 23:34, Patrick De Visschere a écrit : >> With the patch in place, SingleParUpdate in bufferView::draw is never >> reached. > > So finally you mean that an Updat

Re: LyX-Workarea: Background not shown correctly

> On 25 Oct 2017, at 16:28, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > > Le 25/10/2017 à 16:15, Patrick De Visschere a écrit : >>> So finally you mean that an UpdateRequest is really fired for each update >>> event (which makes sense :), right

Re: LyX-Workarea: Background not shown correctly

I should pass the coordinates of the current row instead, to begin with. The selection/cursor problems might be more difficult to solve. What’s your opinion on this? pdv > On 19 Oct 2017, at 23:24, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > > Le 19 octobre 2017 22:34:07 GMT

commit ca4426e broke macos-build

Commit ca4426e (bugfix #10888) broke (at least my) macos-build (qt5.10 and macos 10.12); A change from menu to menuptr in Menus.cpp escaped attention. patch included. pdv menutomenuptr.diff Description: Binary data

Re: Document Settings dialog partially broken on macos

With “not highlighted” I meant that they are greyed out. When e.g. I select “Vertical space” in “Text Layout” instead of the default “Indentation” the OK, Apply and Reset buttons remain greyed out. Apparently the problem is that the screen is not updated immediately: when I subsequently resize

Re: LinkBack support (on MacOS)

> On 12 Sep 2019, at 18:23, Stephan Witt wrote: > > Am 08.09.2019 um 10:57 schrieb Stephan Witt : >> >> Am 25.09.2018 um 17:21 schrieb Stephan Witt : >>> >>> Am 25.09.2018 um 17:10 schrieb Jürgen Spitzmüller : Am Freitag, den 21.09.2018, 15:55 +0200 schrieb pdv: > I came

Re: linking error due to missing boost::assertion_failed_msg()

> On 9 Sep 2019, at 00:41, Stephan Witt wrote: > > Am 08.09.2019 um 22:44 schrieb Patrick De Visschere : >> >> >> >>> On 8 Sep 2019, at 21:03, Stephan Witt wrote: >>> >>> Am 08.09.2019 um 20:47 schrieb pdv : >>>>

Re: linking error due to missing boost::assertion_failed_msg()

t; Two more remarks: >> >> 1) I don't understand why this problem surfaces now and not earlier; >> >> 2) There are additional definitions of assertion_failed() in >> client/boost.cpp and in tex2lyx/boost.cpp; > > I cannot find the commit 01ee3bf1f5. Is it a loc

Re: linking error due to missing boost::assertion_failed_msg()

references to it in my XCode project and I think I’m actually using my macports boost (which is 1.71). This might explain it: I’ve upgraded my macports boost and this breaks my lyx-build. > On 8 Sep 2019, at 10:14, Stephan Witt wrote: > > Am 08.09.2019 um 10:02 schrieb Patrick De

Re: linking error due to missing boost::assertion_failed_msg()

> On 8 Sep 2019, at 21:03, Stephan Witt wrote: > > Am 08.09.2019 um 20:47 schrieb pdv : >> >> On 08/09/2019 17:47, Kornel Benko wrote: >>> Am Sonntag, 8. September 2019, 14:14:15 CEST schrieb Patrick De Visschere: >>>> In the source files (Convert

Re: Blanket permission

Kornel, I hereby grant permission to use my work for LyX under the license GPL version 2 or later. Patrick De Visschere smime.p7s Description: S/MIME cryptographic signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Citation with multiple keys is always labeled as broken

Since commit 4ddc9e… (master, 14 march 2020) citations with multiple keys are always labeled as broken, because the key list is handled as a single key. Included is a possible fix. Patrick citationspatch.diff Description: Binary data smime.p7s Description: S/MIME cryptographic signature --