Code oftain sets the action of an Intent after it's constructor. Until now a call to such a setter caused the Intent to become "unbound" (conservative). This approch allows setting the target once for each Intent - only on the second call the Intent gets unbound. This new variant could be dangerous: Setting the target in a branch of execution may be invalid. This should be detected - no guarantees so! Methods in question are: * Intent.setAction * Intent.setComponent * Intent.setClass * Intent.setClassName |
||
---|---|---|
.. | ||
dalvik |