Why build a simple interface if we can make it complicated for everyone...
Ok. Keep us posted. Nice to know that it is working.
Best,
Scuri
On Tue, Dec 13, 2016 at 10:37 PM, Ranier VF <ranier_...@hotmail.com> wrote:
> Hi Eric,
> I am happy to know, you have better way.
> I had no idea of the problems with "native activity"
>
> Best regards,
>
> Ranier Vilela
> ________________________________________
> De: Eric Wing <ewmail...@gmail.com>
> Enviado: terça-feira, 13 de dezembro de 2016 20:58
> Para: IUP discussion list.
> Assunto: Re: [Iup-users] Android IUP implementation question/problem for
> IupDialog
>
> On 12/13/16, Ranier VF <ranier_...@hotmail.com> wrote:
> > Eric, I believe that is you need (lifecycles events).
> >
> > http://www.ikerhurtado.com/android-ndk-native-activity-
> app-glue-lib-lifecycle-threads
> > "Commands (lifecycle events) from Main (UI) thread"
> >
> > Best regards,
> > Ranier Vilela
> >
>
> Thanks Ranier for the thought, but no, I am deliberately not doing
> this. I've been down this path before multiple times and it always
> ends in tears. The so called "Native Activity" is a misnomer (false
> advertising) and it is half-baked. I have swapped notes with other
> experienced Android developers in this realm trying to push hard on
> actual native GUI applications and we all came to the same conclusion
> that "Native Activity" should be disregarded.
>
> There are tons of problems with it, but ultimately, the biggest
> problem is that Native Activity runs on a background thread. This
> basically makes your code a second class citizen on the platform and
> makes it extremely hard to do anything because you are constantly
> worrying about threading issues and locking issues because every
> native API provided by the system is not accessible on your thread.
> You can't just do a simple direct call to anything which makes it many
> times harder to implement anything. There are also performance
> problems and this became an issue for me on a prior project. I was
> involved with another big cross-platform project that did stuff on a
> background thread. Their designers thought this was a good thing, but
> they never talked to a game engine person such as my self and didn't
> understand things like latency and determinism (and other things like
> the costs of context switching). Basically their APIs worked in one of
> two ways...either async so I got the result back some time later,
> usually way too late for my 16 ms window for a game or there was a
> massive thread sync point that brought everything to halt for a simple
> little function (which add up).
>
> The design I'm pursuing for IUP is truly native Android UI on the
> main/UI thread. This will keep IUP programs as a first class citizen
> and make it easier to both develop for and integrate more advanced
> widgets in the future.
>
> Thanks,
> Eric
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Iup-users mailing list
> Iup-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iup-users
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Iup-users mailing list
> Iup-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iup-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
