SAPUI5 路由 - controlId 和 targetControl 之间的区别 [英] SAPUI5 Routing - Difference between controlId and targetControl

查看:45
本文介绍了SAPUI5 路由 - controlId 和 targetControl 之间的区别的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的路由配置中,我可以设置属性controlId"或targetControl"来指定我想要放置新视图的控件的 ID.到目前为止,我发现的唯一区别是controlId"似乎具有更高的优先级.意思是:如果我同时指定 controlId 使用.

In my routing configuration I can either set the property "controlId" or "targetControl" to specify the ID of the control where I want to put my new view. The only difference I figured out so far is that it seems that "controlId" has a higher priority. Means: If I specify both controlId is used.

尽管如此,这些键之间有什么区别还是它们是同义词?targetAggregation"和controlAggregation"也是如此?

Despite that, is there any difference between these keys or are they synonyms? The same goes for "targetAggregation" and "controlAggregation"?

我已经阅读了很多 SAP 文档,但是我找不到解释每个参数的页面,尤其是我无法找到这个问题的答案.

I've read a lot of SAP documentation but I couldn't find a page where every parameter is explained and especially I wasn't able to find the answer for this question.

推荐答案

documentation 声明 targetControltargetAggregation 自 1.28 起已弃用.

The documentation states targetControl and targetAggregation as deprecated since 1.28.

源代码 您可以找到一些地方,其中 1.28 之前的路由配置被转换为新的路由配置,包括在该版本中引入的目标.这或许可以解释命名:targetControltargetAggregation 起源于没有单独目标的时间配置对象,但所有内容都在路由中定义.

In the sourcecode you can find some places where the pre 1.28 route configs are converted to the new route config including targets, which were introduced at that version. That might explain the naming: targetControl and targetAggregation have there origin a time where there was no separate target configuration object but everything was defined within the route.

您可以在开发者指南中或多或少地找到可用的参数:概述 和有关参数的更多详细信息此处.

You can find the available parameters more or less explained in the developer guide: overview and more details on parameters here.

这篇关于SAPUI5 路由 - controlId 和 targetControl 之间的区别的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆