Hi,
I tried to experiment with the MeeGo components, and I noticed that the
graphics for it are missing:
> Connecting to device...
>
> [D] QQmlDebuggingEnabler::QQmlDebuggingEnabler:1392 - QML debugging is
> enabled. Only use this in a safe environment.
>
> [D] QWaylandEglIntegration::QWaylandEgl
Hello Marcin,
the qt-components on Qt5 have a different version, which is 2.0
so, try with "import com.nokia.meego 2.0" if you want to keep testing with
qt-components ;)
2013/11/11 Marcin M.
> Hello,
>
> I am aware of that, that Sailfish native apps should use Silica. But it's
> not my point
Hello,
I am aware of that, that Sailfish native apps should use Silica. But it's
not my point in this case to switch I'm just experimenting with the old
com.nokia.meego components. They're available in the repos, so I tried, how
would the app basing on it work.
I installed it in Emulator only - I
Hi Marcin
Have you installed that package to both the Emulator and the SDK Build
Engine? (and synced in the SDK Control Center?)
My next guess is that you get this error from QML. Normally the qml
types are available in a version of the package with
import-declarative in the name (to be i
Hi,
Are you using the harmattan qml components with "import
com.nokia.meego 1.1" and "PageStackWindow" as the top level component?
If you are, I think you should change to using Sailifish Silica
components and ApplicationWindow as the top level component as shown here:
https://sailfisho
Hi,
I'm trying to run an app using qt-components-qt5 (installed in the
emulator). It fails though. The output is:
QML debugging is enabled. Only use this in a safe environment.
Using Wayland-EGL
Module 'com.nokia.meego' does not contain a module identifier directive -
it cannot be protected fr
