Re: [Interest] Rendering simple QPainterPath with Qt3D

2016-03-15 Thread Ch'Gans
On 15 March 2016 at 22:34, Sean Harmer wrote: > On Tuesday 15 Mar 2016 17:41:07 Ch'Gans wrote: >> On 14 March 2016 at 22:03, Sean Harmer wrote: >> > On Monday 14 Mar 2016 16:50:32 Ch'Gans wrote: >> >> >> >> Could anyone shed some light on how I could achieve this, like is the >> >> custom QMEsh/G

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 20:12:25 PDT Thiago Macieira wrote: > It's inside QtWebKit. Mac has another copy of it, inside its own WebKit > framework. Oh, QtScript has yet another copy of JSC. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source T

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 21:42:24 PDT Larry Martell wrote: > On Tue, Mar 15, 2016 at 9:14 PM, Thiago Macieira > > wrote: > > On terça-feira, 15 de março de 2016 19:15:03 PDT Larry Martell wrote: > >> So that led me to these questions: > >> > >> -What runs the JS code on the client? >

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Larry Martell
On Tue, Mar 15, 2016 at 9:14 PM, Thiago Macieira wrote: > On terça-feira, 15 de março de 2016 19:15:03 PDT Larry Martell wrote: >> So that led me to these questions: >> >> -What runs the JS code on the client? > > JavaScriptCore, WebKit's JS engine. Is that part of Qt? I googled it, and it seems

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 19:15:03 PDT Larry Martell wrote: > So that led me to these questions: > > -What runs the JS code on the client? JavaScriptCore, WebKit's JS engine. > -Is there a cache for the JS code and is it the case that 8000/# will > only actually go out on the wire if t

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Larry Martell
On Tue, Mar 15, 2016 at 12:45 PM, Thiago Macieira wrote: > On terça-feira, 15 de março de 2016 12:04:34 PDT Larry Martell wrote: >> > To make matters short, these two URLs are different: >> > >> > http://foo.bar.com:8000/#/workitem/12345 >> > >> > scheme = http >> > authority = foo

[Interest] Calling QCocoaMenuBar::updateMenuBarImmediately()

2016-03-15 Thread Jim Prouty
I'm trying to work around a problem on Macintosh where Qt 5.6 leaves the menu bar and menu items in a disabled state (Qt mistakenly believes a modal window exists, apparently). I'd like to try calling QCocoaMenuBar::updateMenuBarImmediately() in the Qt library, implemented here: /qtbuild5/qt/q

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 12:04:34 PDT Larry Martell wrote: > > To make matters short, these two URLs are different: > > > > http://foo.bar.com:8000/#/workitem/12345 > > > > scheme = http > > authority = foo.bar.com:8000 > > path = / > > fragment = /worki

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Larry Martell
On Tue, Mar 15, 2016 at 11:54 AM, Thiago Macieira wrote: > On terça-feira, 15 de março de 2016 11:45:12 PDT Larry Martell wrote: >> >> QString urlStr = "http://foo.bar.com:8000/#/workitem/12345";; >> >> QUrl reportUrl(urlStr); >> > >> > So I'm assuming you're misusing the term and that you

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 11:45:12 PDT Larry Martell wrote: > >> QString urlStr = "http://foo.bar.com:8000/#/workitem/12345";; > >> QUrl reportUrl(urlStr); > > > > So I'm assuming you're misusing the term and that you did want a fragment. > > I realize that using # is typically

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Larry Martell
On Tue, Mar 15, 2016 at 11:37 AM, Thiago Macieira wrote: > On terça-feira, 15 de março de 2016 07:04:49 PDT Larry Martell wrote: >> Sorry for not giving more details. It's not a fragment - it's an > > You say "it's not a fragment" and then your URL uses a fragment: > >> QString urlStr = "http:

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 07:04:49 PDT Larry Martell wrote: > Sorry for not giving more details. It's not a fragment - it's an You say "it's not a fragment" and then your URL uses a fragment: > QString urlStr = "http://foo.bar.com:8000/#/workitem/12345";; > QUrl reportUrl(urlStr

Re: [Interest] Compiling Qt from source 64 bit on Windows

2016-03-15 Thread Thiago Macieira
On terça-feira, 15 de março de 2016 08:30:33 PDT Koehne Kai wrote: > > The Openssl libs are pre compiled and they provide binaries for both 32 > > and > > 64 bit. > > I never tried building Qt 64 bit with openssl statically. So I'm afraid I've > nothing to add. Suggestion: give up, use dynamic ru

Re: [Interest] getting symbols in deployed mac app

2016-03-15 Thread Croitor Alexandr
Yes, IIRC some of the debug plugins do not get copied over when using -use-debug-libs, and some release libraries do get copied. There are also issues regarding this: https://bugreports.qt.io/browse/QTBUG-48800 https://bugreports.qt.io/browse/QTBUG-4

Re: [Interest] getting symbols in deployed mac app

2016-03-15 Thread Larry Martell
On Tue, Mar 15, 2016 at 10:33 AM, Larry Martell wrote: > I am building my Qt app with symbols so I can use lldb. I use this > cmake option "-DCMAKE_BUILD_TYPE=Debug". That indeed does make an > executable that I debug locally on the machine I built it on. > > But if I then use macdeployqt to gener

[Interest] getting symbols in deployed mac app

2016-03-15 Thread Larry Martell
I am building my Qt app with symbols so I can use lldb. I use this cmake option "-DCMAKE_BUILD_TYPE=Debug". That indeed does make an executable that I debug locally on the machine I built it on. But if I then use macdeployqt to generate a dmg file, the executable in there does not seem to have sym

Re: [Interest] Qt3D : using a custom projection matrix with QCamera

2016-03-15 Thread Xavier Bigand
Already done : https://bugreports.qt.io/browse/QTBUG-48573 Thank you. 2016-03-15 12:30 GMT+01:00 Sean Harmer : > On Tuesday 15 Mar 2016 12:14:03 Xavier Bigand wrote: > > Hi, > > > > We are considering to replace our 3D engine by Qt3D, I can already load > our > > models and textures and now I tr

Re: [Interest] Qt3D : using a custom projection matrix with QCamera

2016-03-15 Thread Sean Harmer
On Tuesday 15 Mar 2016 12:14:03 Xavier Bigand wrote: > Hi, > > We are considering to replace our 3D engine by Qt3D, I can already load our > models and textures and now I try to fix the camera. > > I need to set my own projection camera, because we use a custom matrix. I > our software we have a

[Interest] Qt3D : using a custom projection matrix with QCamera

2016-03-15 Thread Xavier Bigand
Hi, We are considering to replace our 3D engine by Qt3D, I can already load our models and textures and now I try to fix the camera. I need to set my own projection camera, because we use a custom matrix. I our software we have a transition between an orthographic camera and a perspective one, we

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Larry Martell
On Tue, Mar 15, 2016 at 1:32 AM, Thiago Macieira wrote: > On segunda-feira, 14 de março de 2016 18:30:13 PDT Larry Martell wrote: >> We have an app that emits a URL with a hashtag in it (#) and that is >> processed by some Angular JS code we have >> (https://docs.angularjs.org/guide/$location). Th

Re: [Interest] bug with # in URL when using setUrl?

2016-03-15 Thread Konstantin Tokarev
15.03.2016, 01:31, "Larry Martell" : > We have an app that emits a URL with a hashtag in it (#) and that is > processed by some Angular JS code we have > (https://docs.angularjs.org/guide/$location). That URL is emitted with > setUrl. It works fine on a Mac, but on Windows it acts as if the # > w

Re: [Interest] Rendering simple QPainterPath with Qt3D

2016-03-15 Thread Sean Harmer
On Tuesday 15 Mar 2016 17:41:07 Ch'Gans wrote: > On 14 March 2016 at 22:03, Sean Harmer wrote: > > On Monday 14 Mar 2016 16:50:32 Ch'Gans wrote: > >> > >> Could anyone shed some light on how I could achieve this, like is the > >> custom QMEsh/Geometry the right approach for this kind of problems?

Re: [Interest] Compiling Qt from source 64 bit on Windows

2016-03-15 Thread Koehne Kai
> -Original Message- > From: Nuno Santos [mailto:nunosan...@imaginando.pt] > Sent: Tuesday, March 15, 2016 9:15 AM > To: Koehne Kai > Cc: interest@qt-project.org > Subject: Re: [Interest] Compiling Qt from source 64 bit on Windows > > Kai, > > To whom should I pass the -static-runtime

Re: [Interest] Compiling Qt from source 64 bit on Windows

2016-03-15 Thread Nuno Santos
Kai, To whom should I pass the -static-runtime option? To Qt configure or to Openssl libs? When I compile Qt from source I modify msvc-desktop.conf to use MT instead of MD which comes by default. The Openssl libs are pre compiled and they provide binaries for both 32 and 64 bit. With a 32 b

Re: [Interest] Upcoming mobile Qt features?

2016-03-15 Thread Bo Thorsen
Den 14-03-2016 kl. 20:26 skrev Jason H: I'm being asked for more modern features, I don't know where these are on the Qt roadmap? - TouchID/FingerprintManager: Now that both mobile platforms have platform-level APIs for fingerprints, is Qt going to support them in some way? - Streaming vid

Re: [Interest] Compiling Qt from source 64 bit on Windows

2016-03-15 Thread Koehne Kai
> -Original Message- > From: Interest [mailto:interest- > bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of > Nuno Santos > Sent: Monday, March 14, 2016 7:12 PM > To: interest@qt-project.org > Subject: [Interest] Compiling Qt from source 64 bit on Windows > > Hi, > > Is t