Windows Mobile 表单大小
我正在创建一个使用自定义 GUI 的 Windows 移动应用程序。 它有一个图像作为背景,并在其上呈现一些文本和图像。 我想在应用程序本身中进行尽可能少的图像处理,因此我为不同的屏幕分辨率创建不同的皮肤。 如果我需要支持其他屏幕分辨率,我只需添加另一个皮肤。
但令我担心的是,不同的模拟器图像在其任务栏和菜单栏上的大小不同,因此对于具有相同分辨率的所有设备,实际表单的大小并不相同。 到目前为止,我发现模拟器的任务栏和菜单要么是 104(通常是 VGA、WVGA…)要么是 52(QVGA、QWVGA…)像素高。 这些菜单是否总是占用 52 或 104 像素,或者设备供应商或高级用户是否安装了 3 像素高的电池表之类的东西,因此菜单突然占用了 107 像素?
I’m creating a windows mobile app which uses a custom GUI. It has an image as background and some text and images rendered on it. I want to do as little image processing in the app itself, so I’m creating different skins for different screen resolutions. If I need to support another screen resolution I’ll just add another skin.
But what concerns me is that different emulator images have different sizes on their taskbars and menu bars, so the size of the actual form is not the same for all devices with the same resolution. So far I’ve found emulators where the taskbar and menu is either 104 (usually VGA, WVGA…) or 52 (QVGA, QWVGA…) pixels high. Do those menus always take up 52 or 104 pixels, or do device vendors or power users install things like a 3px high battery meter so the menu suddenly takes up 107 pixels?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
从我在 Windows Mobile 上看到的情况来看,有一个标准的屏幕尺寸,并且各种模拟器的尺寸都是该标准尺寸的缩放比例,IE 104px 是 52px 上 2 的比例因子。 至少在 NETCF 中,绘图 API 可以很好地处理缩放。
From what I've seen with windows mobile, there is a standard screen size and the various emulator's sizes are scalings of that standard size IE 104px is a scale factor of 2 over 52px. In NETCF at least, the drawing API handled the scaling fairly well.
是的,我记得过去也遇到过这个问题 - iirc 默认条形大小是 26 的倍数或其他(所以 52 和 104 似乎合适) - 不幸的是,我这里没有代码,但我认为它使用了类似的东西这:
我记得应用程序检测底部按钮栏是否存在存在问题,但这可能只是我在加载时执行操作的顺序..
hth
福斯
yep i remember having problems with this in the past as well - iirc the default bar size was a multiple of 26 or something (so 52 and 104 seems to fit) - i dont have the code here unfortunately, but i think it used something like this:
i remember there being a problem with the apps detecting if the bottom button bar was present, but that might have just been the order i did things in at load-time..
hth
fusi