Can I gain some efficiency by declaring appropriate members "static" in Android Activity -
If any action is singleton in practice, I think that appropriate members can achieve some efficiency by declaring "stable" Are risks with zero Yes?
-
There is more than one example "single task" Or "single instance" activity, so that all new intents are expected to handle.
It means you can use a static member .
In addition, require a thread-safe static member only in a standard
or one click . Let's assume that the current activity stack is A-B-C-D if the intent to arrive is for an activity of Type B, which is in "Standard" or "Single Top" mode. A new example of B will be launched (since B is not at the top of the heap), so the resulting stack will be A-B-C-D-B.
Comments
Post a Comment