Why does an Android activity choose to call destroy() rather than just stay in the paused state? -


as new android app development, 1 thing have noticed in simplest of apps create, on losing focus, there preference app call destroy() rather stay in paused state.

i wondering factors drive decision. perhaps device itself. perhaps there programming factors or priority settings come play.

i comfortable handling destroy state, guess know if have control on frequency of occurrence. when focus regained how minimise performance hit caused repeatedly having go through oncreate() rather preferred onresume()?


Comments

Popular posts from this blog

javascript - jquery or ashx not working -

opencv - DataType<cv::detail::deriv_type>::depth what is it used for -

python 3.x - Mapping specific letters onto a list of words -