Re: [Interest] QProcess performance issues

Hello, Is OpenCV an option? http://docs.opencv.org/doc/tutorials/highgui/video-write/video-write.html On Tue, May 12, 2015 at 8:21 PM, Matthew Woehlke < mw_tr...@users.sourceforge.net> wrote: > I have an application that generates a series of images (QImage) and > writes them to disk as a vid

Re: [Interest] QProcess performance issues

On Tuesday 12 May 2015 17:36:59 Matthew Woehlke wrote: > After further testing, it seems that the problem is caused by writing to > the process's stdin? Is there some issue with writing to a QProcess's > input pipe on Windows? (We are writing quite a lot - many MiB's - of > data...) Yes. The QWind

Re: [Interest] QProcess performance issues

On 2015-05-12 14:21, Matthew Woehlke wrote: > I have an application that generates a series of images (QImage) and > writes them to disk as a video. I am encoding the video using an > external FFmpeg process, which I start and communicate with via > QProcess. I feed this the images via its stdin, u

Re: [Interest] cross-language matching of QStrings: partial success only?

On Monday May 11 2015 23:00:36 Till Oliver Knoll wrote: > - Have fun! In case anyone wants to share the fun, here's my little test thingy: https://github.com/RJVB/fontweightissue-qt5 Cheers, R. ___ Interest mailing list Interest@qt-project.org http://

Re: [Interest] Cross-platform font normalization best practice

On 5/12/2015 11:08 AM, René J.V. Bertin wrote: > On Tuesday May 12 2015 10:00:06 Bob Hood wrote: > >> 2. Add platform-aware code to the C++ file that manually changes the font >> for each UI component under OS X builds. > I think that's the safest option(*)... Indeed. This is the option I'm mov

[Interest] QProcess performance issues

I have an application that generates a series of images (QImage) and writes them to disk as a video. I am encoding the video using an external FFmpeg process, which I start and communicate with via QProcess. I feed this the images via its stdin, using QImage::save to write them to the QProcess in B

Re: [Interest] Cross-platform font normalization best practice

On Tuesday May 12 2015 10:00:06 Bob Hood wrote: > 2. Add platform-aware code to the C++ file that manually changes the font >for each UI component under OS X builds. I think that's the safest option(*) which will also allow you to give the user the choice what font s/he wants (which I for one

Re: [Interest] QGLWidget::drawTexture transparency woes

On 2015-05-12 12:18, Matthew Woehlke wrote: > I'm trying to use QGLWidget::drawTexture to draw a texture with an alpha > channel, but it is not working; the areas that should be transparent are > instead black, as if the alpha channel is missing in the GL texture. Never mind... I had a shader bein

[Interest] QGLWidget::drawTexture transparency woes

I'm trying to use QGLWidget::drawTexture to draw a texture with an alpha channel, but it is not working; the areas that should be transparent are instead black, as if the alpha channel is missing in the GL texture. Here's a quick sketch of what I am doing: MyWidget::initializeGL() { d->te

[Interest] Cross-platform font normalization best practice

I see that on Windows, Designer defaults to the "MS Shell Dialog 2" 8-point font, and on OS X (Yosemite) it is ".Helvetical Neue DeskInterface" 13-point (in one field, while another oddly reports an "Al Bayan" typeface). I have found that changing the OS X interface to use "Lucida Grande" 11-po

[Interest] Let's talk about the upcoming Camera breakage in 5.4.2

I wanted to open this discussion up to anyone who is using a Camera, who has working code in 5.4.1. Brief backstory: At 5.4.1 introduced a fix that is is being removed in 5.4.2, because it is considered a "behavior" change and not a bug fix. I think this categorization is wrong, and I'm going

Re: [Interest] No lupdate.exe/lrelease.exe when building Qt from source as "shared"

On Tuesday 12 May 2015 13:34:08 Sascha Offe wrote: > Hi, > > I've got a question regarding building Qt from source: > I've done that successfully (on Windows) both for "shared" (DLL) and > "static" -- so far, so good. > > But only in the "static" version I can find linguist.exe, lupdate.exe and >

[Interest] No lupdate.exe/lrelease.exe when building Qt from source as "shared"

Hi, I've got a question regarding building Qt from source: I've done that successfully (on Windows) both for "shared" (DLL) and "static" -- so far, so good. But only in the "static" version I can find linguist.exe, lupdate.exe and lrelease.exe in the "bin" path. In the "shared" build, there are o

Re: [Interest] No network reply received in WinRT after calling QNetworkAccessManager::post

Hi, On 5/12/2015 11:05, Rogerio Nicolau wrote: > Hi > > I'm using Qt 5.4.1 and have an App which runs fine on all the other > platforms except on winrt where after a QNetworkAccessManager::post, the > QNetworkAccessManager::finished signal never gets triggered. The post is > just an http message

[Interest] QML Settings

Hi list(s) I was considering the usage of Settings QML for an app I'm working on. I just need to store two-three strings across mobile platforms and the API seems to fit my use case. However, I'm not able to make it work properly and I'm w

[Interest] No network reply received in WinRT after calling QNetworkAccessManager::post

Hi I'm using Qt 5.4.1 and have an App which runs fine on all the other platforms except on winrt where after a QNetworkAccessManager::post, the QNetworkAccessManager::finished signal never gets triggered. The post is just an http message and I can see that the server receives and responds to t

[Interest] fonts & the Assistant (spin-off from cross-language matching of QStrings: partial success only?)

Hi, I was trying some more fonts/weights/styles when writing my earlier messages in the other thread, using the Qt Assistant as a sample application. It turns out that even in an English locale it fails to restore a common font like Segoe UI Semibold properly, and even when you select Segoe UI R

Re: [Interest] cross-language matching of QStrings: partial success only?

On Tuesday May 12 2015 08:08:57 Till Oliver Knoll wrote: Hi, >And we even haven't yet talked about X11 font formats ;) (altough there it >might actually be /simpler/). Should that read "tongue-in-cheek simpler"? Because from what I remember, it isn't simple at all (is there even a "hard" stand