How to make the activity load smoothly on the right side

android:ActivityOpenEnterAnimation An activity creates an incoming effect.

android:ActivityOpenExitAnimation An activity does not have an exit effect under finish(), for example, there are two activities A, B starts A first and then starts B, then A does not have finish() This A exit effect.

android:activitycloseenteranimation indicates that the previous activity returns to enter the effect, for example, there are two activities a, b b exits and a enters the effect.

ActivityCloseExitAnimation represents the effect of Activity Finish() For example, if there are two activities A, B B will be finish() after exiting, then the exit effect of B is defined here.

In Android, each interface is an activity, and switching interface operations is actually instantiation between multiple different activities. In Android, the startup mode of an activity determines how the activity starts.

There are four startup modes for Android total activities:

Activity Startup Mode Settings:

There are four startup modes for activities:

1. standard

Mode startup mode, each time an activity is activated, an activity is created and placed in the task stack.

2. singletop

If there happens to be an instance of the activity at the top of the stack of the task, reuse the instance, otherwise a new instance will be created and put on top of the stack (even if there is already an instance of the activity on the stack, as long as it is not on the top of the stack, the instance will be created).

3. singletask

If there is already an instance of the activity in the stack, reusing the instance (which will call the instance's onnewintent()) will bring the instance back to the top of the stack, so the instance on top of the stack will be removed from the stack. If the instance does not exist on the stack, a new instance will be created and placed on the stack.

4. singleinstance

Create an activity instance in a new stack and share the activity instance with multiple applications. Once the instance of the modified activity exists in a certain stack, any application will reuse the instance in the stack when reactivating the modified activity, which is equivalent to multiple applications sharing an application, and whoever activates the activity will enter the same application.

where standard is the default boot mode of the system.

It can be achieved.

However, the 3 layouts are a bit bloated, and should use viewstub or fragments, etc.

When entering the activity, open the thread to load the data needed to parse **, and display a waiting prompt or something. When the data is processed and the message is obtained, hide the prompt control and display the content that needs to be displayed.

First, the thread is used to load the data, and when the data is loaded, a message is sent to jump.

I will also do it in the xml file, mainly because the number of buttons I have is uncertain, and it depends on the data, so I have to write it to the activity to new

Layout declares this botton, buddy, it is recommended to take a look at some introductory tutorials first.

Since it's all written so much, it's almost enough,

Why do you need to restart the interface to end the thread, and what kind of logic is this? Refresh activity is to refresh the content.,It's not compatible with this.。。。

Generally speaking, you don't need to refresh, you just need to update your data!!

Blocking threads are interrupted by interrupt.