On Mon, 9 Feb 2015 16:42:47 +0200
Kaj-Michael Lang mil...@tal.org wrote:
I started to prepare my app for gstreamer 1.0 now that it is available
and soon possible to use in harbour apps.
But the souphttpsrc element that I need is missing. First I thought
this a mistake but it seems it was
You shouldn't worry about errors in ///usr/lib/qt5/qml/ yourself unless
you working in Jolla :)
09.02.2015 19:13, Kaj-Michael Lang пишет:
I think I started to get these after the latest update
unknown:134 - file:///usr/lib/qt5/qml/Sailfish/Silica/Page.qml:134:
TypeError: Cannot read property
On ma, 2015-02-09 at 17:43 +0200, Mohammed Hassan wrote:
Please also note that gstreamer has not yet been white listed for
harbour use.
I know.
Do you need to submit the app now or is it possible for you to wait
Yeah, I can wait. Just planned on preparing a branch so it is ready to
go.
--
I think I started to get these after the latest update
unknown:134 - file:///usr/lib/qt5/qml/Sailfish/Silica/Page.qml:134:
TypeError: Cannot read property of null
Am I doing something wrong and is that something I should worry about ?
--
Kaj-Michael Lang mil...@tal.org
I started to prepare my app for gstreamer 1.0 now that it is available
and soon possible to use in harbour apps.
But the souphttpsrc element that I need is missing. First I thought this
a mistake but it seems it was deliberately excluded:
- [gstreamer] drop soup support for now
why ?
--
I get the same too after latest update.
Haven't noticed any issues except annoyance though.
Kaj-Michael Lang kirjoitti ma helmikuuta 9 16:13:53 2015 GMT+0200:
I think I started to get these after the latest update
unknown:134 - file:///usr/lib/qt5/qml/Sailfish/Silica/Page.qml:134:
TypeError:
