Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Docs
提交
ef6d34f9
D
Docs
项目概览
OpenHarmony
/
Docs
大约 2 年 前同步成功
通知
161
Star
293
Fork
28
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
D
Docs
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
未验证
提交
ef6d34f9
编写于
6月 20, 2022
作者:
O
openharmony_ci
提交者:
Gitee
6月 20, 2022
浏览文件
操作
浏览文件
下载
差异文件
!5625 修改不规范标记对
Merge pull request !5625 from 张亚菲/zyfRelease
上级
db249146
340d1bba
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
12 addition
and
12 deletion
+12
-12
zh-cn/application-dev/ability/stage-ability.md
zh-cn/application-dev/ability/stage-ability.md
+9
-9
zh-cn/application-dev/ability/stage-call.md
zh-cn/application-dev/ability/stage-call.md
+3
-3
未找到文件。
zh-cn/application-dev/ability/stage-ability.md
浏览文件 @
ef6d34f9
...
...
@@ -210,14 +210,14 @@ Ability类拥有context属性,context属性为AbilityContext类,AbilityConte
**表3**
AbilityContext API接口功能介绍
|接口名|描述|
|:------|:------|
|startAbility(want: Want, callback: AsyncCallback
<void>
): void|启动Ability。|
|startAbility(want: Want, options?: StartOptions): Promise
<void>
|启动Ability。|
|startAbilityWithAccount(want: Want, accountId: number, callback: AsyncCallback
<void>
): void|带AccountId启动Ability。|
|startAbilityWithAccount(want: Want, accountId: number, options?: StartOptions): Promise
<void>
|带AccountId启动Ability。|
|startAbilityForResult(want: Want, callback: AsyncCallback
<AbilityResult>
): void|带返回结果启动Ability。|
|startAbilityForResult(want: Want, options?: StartOptions): Promise
<AbilityResult>
|带返回结果启动Ability。|
|startAbilityForResultWithAccount(want: Want, accountId: number, callback: AsyncCallback
<AbilityResult>
): void|带返回结果及AccountId启动Ability。|
|startAbilityForResultWithAccount(want: Want, accountId: number, options?: StartOptions): Promise
<AbilityResult>
|带返回结果及AccountId启动Ability。|
|startAbility(want: Want, callback: AsyncCallback
\
<
void>): void|启动Ability。|
|startAbility(want: Want, options?: StartOptions): Promise
\
<
void>|启动Ability。|
|startAbilityWithAccount(want: Want, accountId: number, callback: AsyncCallback
\
<
void>): void|带AccountId启动Ability。|
|startAbilityWithAccount(want: Want, accountId: number, options?: StartOptions): Promise
\
<
void>|带AccountId启动Ability。|
|startAbilityForResult(want: Want, callback: AsyncCallback
\
<
AbilityResult>): void|带返回结果启动Ability。|
|startAbilityForResult(want: Want, options?: StartOptions): Promise
\
<
AbilityResult>|带返回结果启动Ability。|
|startAbilityForResultWithAccount(want: Want, accountId: number, callback: AsyncCallback
\
<
AbilityResult>): void|带返回结果及AccountId启动Ability。|
|startAbilityForResultWithAccount(want: Want, accountId: number, options?: StartOptions): Promise
\
<
AbilityResult>|带返回结果及AccountId启动Ability。|
### 相同设备启动Ability
应用可以通过
`this.context`
获取Ability实例的上下文,进而使用AbilityContext中的StartAbility相关接口启动Ability。启动Ability可指定Want、StartOptions、accountId,通过callback形式或promise形式实现。具体示例代码如下:
```
ts
...
...
@@ -247,7 +247,7 @@ var want = {
context
.
startAbility
(
want
).
then
((
data
)
=>
{
console
.
log
(
"
Succeed to start remote ability with data:
"
+
JSON
.
stringify
(
data
))
}).
catch
((
error
)
=>
{
console
.
error
(
"
Failed to start remote ability with error:
"
+
JSON
.
stringify
(
error
))
console
.
error
(
"
Failed to start remote ability with error:
"
+
JSON
.
stringify
(
error
))
})
```
从DeviceManager获取指定设备的deviceId。具体示例代码如下:
...
...
zh-cn/application-dev/ability/stage-call.md
浏览文件 @
ef6d34f9
...
...
@@ -18,11 +18,11 @@ Caller及Callee功能如下:具体的API详见[接口文档](../reference/apis
**表1**
Call API接口功能介绍
|接口名|描述|
|:------|:------|
|startAbilityByCall(want: Want): Promise
<Caller>
|获取指定通用组件的Caller通信接口,拉起指定通用组件并将其切换到后台。|
|startAbilityByCall(want: Want): Promise
\
<
Caller>|获取指定通用组件的Caller通信接口,拉起指定通用组件并将其切换到后台。|
|on(method: string, callback: CaleeCallBack): void|通用组件Callee注册method对应的callback方法。|
|off(method: string): void|通用组件Callee去注册method的callback方法。|
|call(method: string, data: rpc.Sequenceable): Promise
<void>
|向通用组件Callee发送约定序列化数据。|
|callWithResult(method: string, data: rpc.Sequenceable): Promise
<rpc.MessageParcel>
|向通用组件Callee发送约定序列化数据, 并将返回的约定序列化数据带回。|
|call(method: string, data: rpc.Sequenceable): Promise
\
<
void>|向通用组件Callee发送约定序列化数据。|
|callWithResult(method: string, data: rpc.Sequenceable): Promise
\
<
rpc.MessageParcel>|向通用组件Callee发送约定序列化数据, 并将返回的约定序列化数据带回。|
|release(): void|释放通用组件的Caller通信接口。|
|onRelease(callback: OnReleaseCallBack): void|注册通用组件通信断开监听通知。|
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录