Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: 自动化步骤中坐标相关操作的控件元素也可以使用参数化&安卓获取控件属性时可直接获取中心坐标值 #450

Merged

Conversation

YeungHoiChiu
Copy link
Contributor

Whether this PR is eventually merged or not, Sonic will thank you very much for your contribution.

无论此PR最终是否合并,Sonic组织都非常感谢您的贡献。

Checklist

  • The title starts with fix, fea, or doc. | 标题为fix、feat或doc开头。
  • I have checked that there are no duplicate pull requests with this request. | 我已检查没有与此请求重复的拉取请求。
  • I have considered and confirmed that this submission is valuable to others. | 我已经考虑过,并确认这份呈件对其他人很有价值。
  • I accept that this submission may not be used. | 我接受此提交可能不会被使用。

Description

image
例如上图一个城市选择器,使用控件定位可以获取到元素对象,但是滑动终点无法确定,考虑使用元素属性获取坐标后使用自定义脚本计算出滑动的起点、终点坐标,再使用坐标滑动方法操作,发现坐标系的控件参数化无效,因此增加这个参数化的代码

@prlabeler prlabeler bot added the feature label Jun 6, 2024
@YeungHoiChiu YeungHoiChiu changed the title feat: 自动化步骤中坐标相关操作也可以使用参数化 feat: 自动化步骤中坐标相关操作的控件元素也可以使用参数化 Jun 6, 2024
@YeungHoiChiu
Copy link
Contributor Author

YeungHoiChiu commented Jun 6, 2024

BTW,顺便在获取控件属性方法中添加获取中心坐标类型逻辑,测试效果

image

验证属性步骤:

image

@YeungHoiChiu YeungHoiChiu changed the title feat: 自动化步骤中坐标相关操作的控件元素也可以使用参数化 feat: 自动化步骤中坐标相关操作的控件元素也可以使用参数化&安卓获取控件属性时可直接获取中心坐标值 Jun 6, 2024
Copy link
Member

@ZhouYixun ZhouYixun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mg

@ZhouYixun ZhouYixun merged commit 342e80c into SonicCloudOrg:main Jun 7, 2024
1 check passed
@YeungHoiChiu YeungHoiChiu deleted the coordinate-globalParams-Support branch June 9, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants