Re: [Interest] Undefined symbols when porting from Qt5 to Qt6

On Thursday 23 May 2024 19:06:59 GMT-3 Corentin Bacqué-cazenave via Interest wrote: > So I probably have to link LibX11 in CmakeList.txt, not sure how however 🙁 > > Thanks for the help 🙂 https://cmake.org/cmake/help/latest/module/FindX11.html -- Thiago Macieira - thiago.macieira (AT) intel.com

[Interest] Update widget geometry BEFORE window shown

I need to do something like this: windowP->layout()->updateGeometry(); // causes all widget geometry to update DoSomethingImportant(windowP->GetWidget(“someWidget”).geometry()); // do something with the geometry of a widget (which must be up to date) windowP->setGeometry(windowP->GetInitialGeomet

Re: [Interest] Undefined symbols when porting from Qt5 to Qt6

Hi, yes, it's from my application. So I probably have to link LibX11 in CmakeList.txt, not sure how however :( Thanks for the help :) Corentin : expert certifié 2022 et Sponsor NVDA, Référent commission Cécité & Co et Ma

Re: [Interest] Undefined symbols when porting from Qt5 to Qt6

On Thursday 23 May 2024 18:14:01 GMT-3 Corentin Bacqué-cazenave via Interest wrote: > Hi, > > I'm trying to port an application from Qt5 to Qt6. > > I get a lot of errors regarding undefined symbols reference like > XUngrabKey, XFree, XStringToKeysym, XFlush... > > All symbols related to X11 se

[Interest] Undefined symbols when porting from Qt5 to Qt6

Hi, I'm trying to port an application from Qt5 to Qt6. I get a lot of errors regarding undefined symbols reference like XUngrabKey, XFree, XStringToKeysym, XFlush... All symbols related to X11 seam to be missing. Does anyone have an idea? Thanks -- Corentin : expert certifié 2022 et

Re: [Interest] Exceptions

On Thursday 23 May 2024 11:57:39 GMT-3 Turtle Creek Software wrote: > *Qt 6.7 > Best Practice Guides > Exception Safety* as currently written > seems very reasonable. We'd much rather see that extended to ARM rather > than abandoned. That is pending an investigation on whether the frames provided

Re: [Interest] Exceptions

*Qt 6.7 > Best Practice Guides > Exception Safety* as currently written seems very reasonable. We'd much rather see that extended to ARM rather than abandoned. This link states that ARM fully supports C++ exception handling: https://developer.arm.com/documentation/dui0491/i/C-and-C---Implementatio