blocks|key|5874080|text|仿真器有一个应用程序，用于创建大小恰到好处的预览：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5874081|http://developer.android.com/guide/topics/appwidgets/index.html#preview|offset|length|5874082|我的建议是使用该应用程序获取您的小部件的previewImage，然后查看其大小。|5874083|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1Z|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

The emulator has an application for creating a preview with just the right size:

<a href="http://developer.android.com/guide/topics/appwidgets/index.html#preview" rel="noreferrer">http://developer.android.com/guide/topics/appwidgets/index.html#preview</a>

My suggestion would be to grab a previewImage of your widget with that application and then look at the size.

blocks|key|3664603|text|根据我的测试，小部件预览连接到小部件XML文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3664604|小部件1x1的小部件预览：|offset|length|style|BOLD|3664605|图片大小:+width=138pixels，height=138pixels|3664606|xml文件定义:+android:minHeight="50dp"，android:minWidth="50dp“|3664607|小部件2x1的小部件预览：|3664608|图片大小:+width=236pixels，height=138pixels|3664609|xml文件定义:+android:minHeight="50dp"，android:minWidth="120dp“|3664610|entityMap^0|0|7|6|0|0|0|7|6|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|S|$]]

According my tests widget preview is connected to widget XML file. 

widget preview for widget 1x1:

picture size: width=138pixels, height=138pixels

xml file definition: android:minHeight="50dp", android:minWidth="50dp"

widget preview for widget 2x1:

picture size: width=236pixels, height=138pixels

xml file definition: android:minHeight="50dp", android:minWidth="120dp"

blocks|key|5874280|text|我建议预览的大小应该直接反映小部件的“默认”大小。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5874281|根据安卓网站：http://developer.android.com/guide/practices/ui_guidelines/widget_design.html|offset|length|5874282|它给出了多个小部件“单元格”的大小指南：70dp+×+n+−+30dp+(其中n是单元格计数)|style|CODE|5874283|例如，2x1单元格小部件将分别是:+MDPI、HDPI和XHDPI中的110x40、165x60和220x80。|5874284|根据经验，我还没有100%25确认这一点，在XXHDPI设备(Nexus+10等)上，由于单元大小较大，该规则不再相关。|5874285|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/guide/practices/ui_guidelines/widget_design.html^0|0|7|25|0|0|K|F|0|Z|6|16|6|1D|6|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@$D|11|E|12|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@$D|14|E|15|H|I]|$D|16|E|17|H|I]|$D|18|E|19|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

I would suggest that the size of your preview should directly reflect the "default" size of your widget.

As per the Android website: <a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html" rel="noreferrer">http://developer.android.com/guide/practices/ui_guidelines/widget_design.html</a>

It gives a guide on the size of multiple widget "cell": <code>70dp × n − 30dp</code> (where n is the cell count)

So, for instance, 2x1 cell widget would be: <code>110x40</code>, <code>165x60</code> and <code>220x80</code> in MDPI, HDPI and XHDPI respectively.

From experience though, and I've not managed to 100% confirm this yet, on XXHDPI devices (Nexus 10 etc) this rule stops being relevant as the cell size is larger.

blocks|key|315970|text|由于网上几乎没有关于这个话题的内容，这里也没有明确的答案，以下是我的一些观察结果：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|315971|315972|应用程序肯定会从mdpi，hdpi和xhdpi文件夹中绘制图像，所以可能有意义的是，这些文件夹有不同的分辨率|unordered-list-item|315973|我认为它没有意义的附加像素分辨率到单元格大小-有相同的空间，所有的小部件|315974|基于以前的，并观察到，谷歌使用201垂直大小为其小部件预览，这是有意义的，使用垂直分辨率，并乘以单元格比例为水平分辨率。可能有一些水平值以上，你应该做相反的事情(计算垂直分辨率从水平)，但现在最好是猜测它...|315975|这并不总是一个好主意直接使用从仿真器的窗口小部件预览图像(虽然这个函数会在我的仿真器产生错误)。通常情况下，最好是预览图像的大部分，所以图像上不应该有填充。我认为谷歌利用这一点来使其数字时钟预览变得更大。|315976|315977|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

As there is next to nothing on this topic on the web, and not definite answer here, these are some my observations:

<ul>
<li>Application definitely draws images from mdpi, hdpi and xhdpi folders, so it might make sense to have different resolutions for those folders</li>
<li>I think that it makes no sense to attach pixel resolution to cell size - there is the same space for all widgets</li>
<li>Based on previous, and on observation that Google use 201 vertical size for its widget preview as stated here, it makes sense to use that for vertical resolution and multiply that with cell ratio for horizontal resolution. There is probably some horizontal value above which you should do the opposite (calculate vertical resolution from horizontal), but for now it is best to guess it...</li>
<li>It is not always a good idea to use directly image from Widget preview from emulator (though this function produces error on my emulator). It is usually better if preview takes most of the image, so there shouldn't be paddings on image. I think Google uses this to make its digital clock preview as big.</li>
</ul>

blocks|key|4146174|text|Gmail+app有一个单独的png，格式为drawable-nodpi-v4，大小为638x504。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4146175|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Gmail app has a single png in drawable-nodpi-v4, size 638x504.

I have a widget in Android for which I am setting a previewImage. Unfortunately, I am having issues figuring the good size for the widget: if it's too big, it gets cropped at the bottom of the frame.

I have been trying to find the recommended size, or even better, the pixel dimensions of this frame where the preview image gets displayed, but I cannot find it in the documentation.

Does anyone please know where to look for that information please?

Thank you.

Android Widget: previewImage size

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我在安卓中有一个小部件，我正在为它设置一个previewImage。不幸的是，我在计算小部件的合适大小时遇到了问题:如果它太大，它会被裁剪到框架的底部。我一直在尝试找到推荐的大小，或者更好的，预览图像显示的帧的像素尺寸，但我在文档中找不到它。有没有人知道在哪里可以找到这些信息？谢谢。

问Android小部件: previewImage大小
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android小部件: previewImage大小EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android小部件: previewImage大小
EN