Android Fragment中如何转换视图并调用方法？

Absolutely! Fragments have their own lifecycle callbacks tailored for handling view-related operations—even more granular than an Activity's onCreate(). Let's break down exactly how to implement view inflation and method calls in a Fragment:

1. onCreateView() – Inflate Your Fragment Layout #

This is the callback where you'll load your Fragment's layout file. It's responsible for returning the root View of your Fragment's UI. Think of it as the Fragment equivalent of inflating views in an Activity's onCreate(), but focused solely on layout setup.

Example (Kotlin):

override fun onCreateView(
    inflater: LayoutInflater,
    container: ViewGroup?,
    savedInstanceState: Bundle?
): View? {
    // Inflate the fragment layout and return it
    return inflater.inflate(R.layout.fragment_your_layout, container, false)
}

Example (Java):

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    // Inflate the fragment layout
    return inflater.inflate(R.layout.fragment_your_layout, container, false);
}

2. onViewCreated() – Perform View Setup & Method Calls #

Once onCreateView() finishes and the View hierarchy is fully created, onViewCreated() is called. This is the best place to:

• Reference views (using findViewById or ViewBinding)
• Modify view properties (text, visibility, etc.)
• Call custom methods that depend on the Fragment's UI being ready

Example with ViewBinding (Kotlin):

private var _binding: FragmentYourLayoutBinding? = null
private val binding get() = _binding!!

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    _binding = FragmentYourLayoutBinding.bind(view)

    // View manipulation example
    binding.welcomeTextView.text = "Hello from the Fragment!"
    
    // Call your custom method here
    initializeFragmentLogic()
}

private fun initializeFragmentLogic() {
    // Your business logic or method calls go here
    loadData()
    setupClickListener()
}

// Don't forget to clean up binding to avoid memory leaks
override fun onDestroyView() {
    super.onDestroyView()
    _binding = null
}

Important Notes #

• Avoid using onActivityCreated(): This callback is deprecated in newer Android versions. onViewCreated() is the modern replacement for post-view-creation setup.
• Don't use onCreate() for view operations: At this point in the lifecycle, the Fragment's View hasn't been created yet, so any attempt to reference views will result in null errors.
• If you need to run code when the Fragment becomes visible to the user (like refreshing data), you can use onStart() or onResume()—but only if those operations don't depend on the View being ready.

内容的提问来源于stack exchange，提问作者shariful islam