Android LayoutInflater的用法详解

2023-10-22 13:50

本文主要是介绍Android LayoutInflater的用法详解,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

相信我们在开发过程中肯定接触过LayoutInflater,比如ListView的适配器里的getView方法里通过LayoutInflater.from(Context).inflater来加载xml布局,在Fragment里的onCreateView里面也是一样,加载布局一共三种方法。
1,在Activity里面调用getLayoutInflater()
2, 通过LayoutInflater.from(context).inflater()
3, context.getSystemService(Context.LAYOUT_INFLATER_SERVICE))
以上的三种方式从实现上都是一样的,Activity里面的getLayoutInflater()实际上调用的是PhoneWindow的实现,而PhoneWindow里源码的处理是LayoutInflater.from(context).inflater(),往下查找最终调用context.getSystemService。
context.getSystemService是Android里一个比较重要的api,是Activity的一个方法,根据传入的Name来取得对应的Object,然后转换成相应的服务对象。以下是系统相应的服务。
传入的Name返回的对象说明
WINDOW_SERVICE WindowManager 管理打开的窗口程序
LAYOUT_INFLATER_SERVICE LayoutInflater 取得xml里定义的view
ACTIVITY_SERVICE ActivityManager 管理应用程序的系统状态
POWER_SERVICE PowerManger 电源的服务
ALARM_SERVICE AlarmManager 闹钟的服务
NOTIFICATION_SERVICE NotificationManager 状态栏的服务
KEYGUARD_SERVICE KeyguardManager 键盘锁的服务
LOCATION_SERVICE LocationManager 位置的服务,如GPS
SEARCH_SERVICE SearchManager 搜索的服务
VEBRATOR_SERVICE Vebrator 手机震动的服务
CONNECTIVITY_SERVICE Connectivity 网络连接的服务
WIFI_SERVICE WifiManager Wi-Fi服务
TELEPHONY_SERVICE TeleponyManager 电话服务

但是LayoutInflater.from(context).inflater()的方法这么多,那它们到底是什么样的用法呢?

/**
341     * Inflate a new view hierarchy from the specified xml resource. Throws
342     * {@link InflateException} if there is an error.
343     *
344     * @param resource ID for an XML layout resource to load (e.g.,
345     *        <code>R.layout.main_page</code>)
346     * @param root Optional view to be the parent of the generated hierarchy.
347     * @return The root View of the inflated hierarchy. If root was supplied,
348     *         this is the root View; otherwise it is the root of the inflated
349     *         XML file.
350     */
351    public View inflate(int resource, ViewGroup root) {
352        return inflate(resource, root, root != null);
353    }
354
355    /**
356     * Inflate a new view hierarchy from the specified xml node. Throws
357     * {@link InflateException} if there is an error. *
358     * <p>
359     * <em><strong>Important</strong></em>&nbsp;&nbsp;&nbsp;For performance
360     * reasons, view inflation relies heavily on pre-processing of XML files
361     * that is done at build time. Therefore, it is not currently possible to
362     * use LayoutInflater with an XmlPullParser over a plain XML file at runtime.
363     *
364     * @param parser XML dom node containing the description of the view
365     *        hierarchy.
366     * @param root Optional view to be the parent of the generated hierarchy.
367     * @return The root View of the inflated hierarchy. If root was supplied,
368     *         this is the root View; otherwise it is the root of the inflated
369     *         XML file.
370     */
371    public View inflate(XmlPullParser parser, ViewGroup root) {
372        return inflate(parser, root, root != null);
373    }
374
375    /**
376     * Inflate a new view hierarchy from the specified xml resource. Throws
377     * {@link InflateException} if there is an error.
378     *
379     * @param resource ID for an XML layout resource to load (e.g.,
380     *        <code>R.layout.main_page</code>)
381     * @param root Optional view to be the parent of the generated hierarchy (if
382     *        <em>attachToRoot</em> is true), or else simply an object that
383     *        provides a set of LayoutParams values for root of the returned
384     *        hierarchy (if <em>attachToRoot</em> is false.)
385     * @param attachToRoot Whether the inflated hierarchy should be attached to
386     *        the root parameter? If false, root is only used to create the
387     *        correct subclass of LayoutParams for the root view in the XML.
388     * @return The root View of the inflated hierarchy. If root was supplied and
389     *         attachToRoot is true, this is root; otherwise it is the root of
390     *         the inflated XML file.
391     */
392    public View inflate(int resource, ViewGroup root, boolean attachToRoot) {
393        if (DEBUG) System.out.println("INFLATING from resource: " + resource);
394        XmlResourceParser parser = getContext().getResources().getLayout(resource);
395        try {
396            return inflate(parser, root, attachToRoot);
397        } finally {
398            parser.close();
399        }
400    }

上面的方法非常清晰,直接看下inflate(parser, root, attachToRoot);

/**
403     * Inflate a new view hierarchy from the specified XML node. Throws
404     * {@link InflateException} if there is an error.
405     * <p>
406     * <em><strong>Important</strong></em>&nbsp;&nbsp;&nbsp;For performance
407     * reasons, view inflation relies heavily on pre-processing of XML files
408     * that is done at build time. Therefore, it is not currently possible to
409     * use LayoutInflater with an XmlPullParser over a plain XML file at runtime.
410     *
411     * @param parser XML dom node containing the description of the view
412     *        hierarchy.
413     * @param root Optional view to be the parent of the generated hierarchy (if
414     *        <em>attachToRoot</em> is true), or else simply an object that
415     *        provides a set of LayoutParams values for root of the returned
416     *        hierarchy (if <em>attachToRoot</em> is false.)
417     * @param attachToRoot Whether the inflated hierarchy should be attached to
418     *        the root parameter? If false, root is only used to create the
419     *        correct subclass of LayoutParams for the root view in the XML.
420     * @return The root View of the inflated hierarchy. If root was supplied and
421     *         attachToRoot is true, this is root; otherwise it is the root of
422     *         the inflated XML file.
423     */
424    public View inflate(XmlPullParser parser, ViewGroup root, boolean attachToRoot) {
425        synchronized (mConstructorArgs) {
426            final AttributeSet attrs = Xml.asAttributeSet(parser);
427            Context lastContext = (Context)mConstructorArgs[0];
428            mConstructorArgs[0] = mContext;
429            View result = root;
430
431            try {
432                // Look for the root node.
433                int type;
434                while ((type = parser.next()) != XmlPullParser.START_TAG &&
435                        type != XmlPullParser.END_DOCUMENT) {
436                    // Empty
437                }
438
439                if (type != XmlPullParser.START_TAG) {
440                    throw new InflateException(parser.getPositionDescription()
441                            + ": No start tag found!");
442                }
443
444                final String name = parser.getName();
445
446                if (DEBUG) {
447                    System.out.println("**************************");
448                    System.out.println("Creating root view: "
449                            + name);
450                    System.out.println("**************************");
451                }
452
453                if (TAG_MERGE.equals(name)) {
454                    if (root == null || !attachToRoot) {
455                        throw new InflateException("<merge /> can be used only with a valid "
456                                + "ViewGroup root and attachToRoot=true");
457                    }
458
459                    rInflate(parser, root, attrs, false);
460                } else {
461                    // Temp is the root view that was found in the xml
462                    View temp;
463                    if (TAG_1995.equals(name)) {
464                        temp = new BlinkLayout(mContext, attrs);
465                    } else {
466                        temp = createViewFromTag(root, name, attrs);
467                    }
468
469                    ViewGroup.LayoutParams params = null;
470                    // 当父层不为空时
471                    if (root != null) {
472                        if (DEBUG) {
473                            System.out.println("Creating params from root: " +
474                                    root);
475                        }
476                        // Create layout params that match root, if supplied// 获取父层的参数并赋值
477                        params = root.generateLayoutParams(attrs);//  子布局不贴上也会被设置LayoutParams
478                        if (!attachToRoot) {
479                            // Set the layout params for temp if we are not
480                            // attaching. (If we are, we use addView, below)
481                            temp.setLayoutParams(params);
482                        }
483                    }
484
485                    if (DEBUG) {
486                        System.out.println("-----> start inflating children");
487                    }
488                    // Inflate all children under temp
489                    rInflate(parser, temp, attrs, true);
490                    if (DEBUG) {
491                        System.out.println("-----> done inflating children");
492                    }
493
494                    // We are supposed to attach all the views we found (int temp)
495                    // to root. Do that now.// 父布局不为空并且贴上会被add到父层
496                    if (root != null && attachToRoot) {
497                        root.addView(temp, params);
498                    }
499
500                    // Decide whether to return the root that was passed in or the
501                    // top view found in xml.// 父布局为空或者没有贴上,result就是View本身
502                    if (root == null || !attachToRoot) {
503                        result = temp;
504                    }
505                }
506
507            } catch (XmlPullParserException e) {
508                InflateException ex = new InflateException(e.getMessage());
509                ex.initCause(e);
510                throw ex;
511            } catch (IOException e) {
512                InflateException ex = new InflateException(
513                        parser.getPositionDescription()
514                        + ": " + e.getMessage());
515                ex.initCause(e);
516                throw ex;
517            } finally {
518                // Don't retain static reference on context.
519                mConstructorArgs[0] = lastContext;
520                mConstructorArgs[1] = null;
521            }
522          // 最后返回 result
523            return result;
524        }
525    }

由上源码我们可以得出:
inflate(layout, null)返回的是View本身,addView后View本身所设置的布局参数无效,由父层和子View决定大小。
inflate(layout, null, false)同上一样,当父层为空,第三个值是否为真没有意义。
inflate(layout, parent)子布局会被add到父层并为该View设置布局参数,具体大小由父层和子View决定。
inflate(layout, parent, false)同上一样,区别就是false父层不会addView。
inflate(layout, parent, true)同第三个方法一样,父层View会addView并为其设置参数。

这篇关于Android LayoutInflater的用法详解的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/261845

相关文章

Debezium 与 Apache Kafka 的集成方式步骤详解

《Debezium与ApacheKafka的集成方式步骤详解》本文详细介绍了如何将Debezium与ApacheKafka集成,包括集成概述、步骤、注意事项等,通过KafkaConnect,D... 目录一、集成概述二、集成步骤1. 准备 Kafka 环境2. 配置 Kafka Connect3. 安装 D

Java中ArrayList和LinkedList有什么区别举例详解

《Java中ArrayList和LinkedList有什么区别举例详解》:本文主要介绍Java中ArrayList和LinkedList区别的相关资料,包括数据结构特性、核心操作性能、内存与GC影... 目录一、底层数据结构二、核心操作性能对比三、内存与 GC 影响四、扩容机制五、线程安全与并发方案六、工程

JavaScript中的reduce方法执行过程、使用场景及进阶用法

《JavaScript中的reduce方法执行过程、使用场景及进阶用法》:本文主要介绍JavaScript中的reduce方法执行过程、使用场景及进阶用法的相关资料,reduce是JavaScri... 目录1. 什么是reduce2. reduce语法2.1 语法2.2 参数说明3. reduce执行过程

Android 悬浮窗开发示例((动态权限请求 | 前台服务和通知 | 悬浮窗创建 )

《Android悬浮窗开发示例((动态权限请求|前台服务和通知|悬浮窗创建)》本文介绍了Android悬浮窗的实现效果,包括动态权限请求、前台服务和通知的使用,悬浮窗权限需要动态申请并引导... 目录一、悬浮窗 动态权限请求1、动态请求权限2、悬浮窗权限说明3、检查动态权限4、申请动态权限5、权限设置完毕后

Spring Cloud LoadBalancer 负载均衡详解

《SpringCloudLoadBalancer负载均衡详解》本文介绍了如何在SpringCloud中使用SpringCloudLoadBalancer实现客户端负载均衡,并详细讲解了轮询策略和... 目录1. 在 idea 上运行多个服务2. 问题引入3. 负载均衡4. Spring Cloud Load

Springboot中分析SQL性能的两种方式详解

《Springboot中分析SQL性能的两种方式详解》文章介绍了SQL性能分析的两种方式:MyBatis-Plus性能分析插件和p6spy框架,MyBatis-Plus插件配置简单,适用于开发和测试环... 目录SQL性能分析的两种方式:功能介绍实现方式:实现步骤:SQL性能分析的两种方式:功能介绍记录

在 Spring Boot 中使用 @Autowired和 @Bean注解的示例详解

《在SpringBoot中使用@Autowired和@Bean注解的示例详解》本文通过一个示例演示了如何在SpringBoot中使用@Autowired和@Bean注解进行依赖注入和Bean... 目录在 Spring Boot 中使用 @Autowired 和 @Bean 注解示例背景1. 定义 Stud

如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别详解

《如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别详解》:本文主要介绍如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别的相关资料,描述了如何使用海康威视设备网络SD... 目录前言开发流程问题和解决方案dll库加载不到的问题老旧版本sdk不兼容的问题关键实现流程总结前言作为

SQL 中多表查询的常见连接方式详解

《SQL中多表查询的常见连接方式详解》本文介绍SQL中多表查询的常见连接方式,包括内连接(INNERJOIN)、左连接(LEFTJOIN)、右连接(RIGHTJOIN)、全外连接(FULLOUTER... 目录一、连接类型图表(ASCII 形式)二、前置代码(创建示例表)三、连接方式代码示例1. 内连接(I

Go路由注册方法详解

《Go路由注册方法详解》Go语言中,http.NewServeMux()和http.HandleFunc()是两种不同的路由注册方式,前者创建独立的ServeMux实例,适合模块化和分层路由,灵活性高... 目录Go路由注册方法1. 路由注册的方式2. 路由器的独立性3. 灵活性4. 启动服务器的方式5.