On Friday 29 January 2016 14:45:06 Simon Hausmann wrote:
> Judging from responses on the internet like
[...]
> I have the impression that the Media Foundation in Windows does not support
> h264 payloads in RTSP. Not sure there's much we can do on the Qt side about
> that :)
Would it be possible to
Hi!
We are trying to display an RTSP stream under Windows.
For the video encoding, h264 is used.
On the GUI side we are using the QML MediaPlayer component.
Unfortunately, we don't see any video output nor do we get any error.
VLC is able to playback the stream on the same machine.
Should this w
On Wednesday 23 September 2015 08:37:54 Heikkinen Jani wrote:
> We are targeting to release Qt 5.5.1 as soon as possible, most probably
> during next week.
Hi
Could you please give us a new estimate?
Unfortunately, we rely on one of the fixes in 5.5.1.
Thanks!
Best regards
Gerhard
_
Hi
The behavior of QString::trimmed has changed from 5.3.2 to 5.5.
.trimmed() on an empty string (" ") makes it null
.trimmed() on an empty string ("") doesn't make it null
Is this intended or a bug?
By the way: the output of qDebug is not as expected:
there are additional whitespaces before tru
On Monday 27 July 2015 23:21:02 Cristian Adam wrote:
> On Mon, Jul 27, 2015 at 6:03 PM, Thiago Macieira
> mailto:thiago.macie...@intel.com>> wrote:
>
> On Monday 27 July 2015 09:58:42 Gerhard Scheikl wrote:
> > > How is it licensed?
> >
>
On Monday 27 July 2015 09:47:34 Knoll Lars wrote:
>
> With the old QXmlReader or with QXmlStreamReader?
We are currently using QXmlSchemaValidator for the validation.
> QXmlStreamReader is not a SAX parser.
But the approach is very similar. Both are "iterative". :)
Best regards
Gerhard
___
> Did you consider using QXmlStreamReader/Writer instead of the old QXml?
> These classes are fully compliant, well tested and very fast. The only
> drawback is that there is no equivalent to the QDom* classes, but in most
> cases you’re better off parsing directly into your own data structures
>
On Friday 24 July 2015 08:50:07 Thiago Macieira wrote:
> On Friday 24 July 2015 15:26:30 Gerhard Scheikl wrote:
> Hello Gerhard
>
> Your question is answered mostly by your paragraph above: QtXml is in Done
> state, so we really don't want to do major surgery in it, which coul
Hi
Unfortunately, the QtXml classes contain a lot of bugs and are not really
maintained.
So we came up with the idea to replace the back-end with Xerces and try to
leave the Qt API part the same.
Has anyone tried such an approach already?
If we succeed, we would like to give this code back to
Hausmann Simon , 14.06.2015 17:57:
> Hi,
>
> This is a result of QVariant being a value type. If you make a copy and
> modify it, then the original remains as-is. The call to setContextProperty
> creates a copy. If you want explicitly shared data between the JavaScript
> environment and C++ then I
Ben Lau , 15.06.2015 01:45:
> var tmp = myMap.asdf;
> tmp.name = "asdf"
> myMap.asdf = tmp;
Thanks for the fast reply!
Unfortunately, this approach is very cumbersome for deeper hierarchies like:
a.b.c.d[2].e.f = "g"
I was hoping for a more convenient solution.
Best regards
Gerhard
Hi
I recently discovered some unexpected behavior when exchanging a QVariantMap
with QML code:
Here's what I'm doing on the C++ side:
my_map = json_document.toVariant();
engine.rootContext()->setContextProperty("myMap", my_map);
Then on the QML side:
myMap.asdf.name = "asdf"
This change is not
12 matches
Mail list logo
