On Tue, Nov 18, 2014 at 7:13 AM, Attila Csipa wrote:
> HI,
>
> It turns out you can do a fully functional (ie. not a subset) Android UI
> just by using QAndroidExtras and it's QAndroidJNIObject class from C++,
> without ever touching QML or QtQuick. At this point, this is just an
> exercise, for
HI,
It turns out you can do a fully functional (ie. not a subset) Android UI
just by using QAndroidExtras and it's QAndroidJNIObject class from C++,
without ever touching QML or QtQuick. At this point, this is just an
exercise, for details see
http://achipa.blogspot.com/2014/11/native-ui-in-qt
Well it actually cannot be termed as *Crash* as it just silently exits with
error 255 which I guess here must be resource not found.
Should it be reported as a bug ?
On Fri, Nov 14, 2014 at 7:48 PM, Alejandro Exojo wrote:
> El Friday 14 November 2014, ashish dabhade escribió:
> > No need to clic
Thank you for sorting this out.
Regards,
Dmitrii.
2014-11-18 11:49 GMT+03:00 :
>
> > On 16 Nov 2014, at 14:21, Dmitrii Volosnykh
> wrote:
> >
> > Is such a behaviour is correct or this should be considered as a bug?
> >
> > onPaint handler gets triggered on requestPaint() and
> markDirty(Qt.rec
