用于最小化和最大化窗口的事件处理程序-EventHandlerforMinimizeandMaximizeWindow

2  

The correct message is WM_SIZE, but Daemin's answer points to the wrong WM_SIZE help topic. Check the wParam. Be careful as your window may be maximized but hidden.

正确的消息是WM_SIZE,但Daemin的答案指向错误的WM_SIZE帮助主题。检查wParam。小心,因为您的窗口可能会最大化但隐藏。

2  

Going from my Windows CE experience you should handle either the WM_SIZE or WM_WINDOWPOSCHANGED messages. If you're working on PocketPC I would suggest you take a look at the WM_WINDOWPOSCHANGED message first because I'm not sure the WM_SIZE has the right parameters that you need.

从我的Windows CE经验来看,您应该处理WM_SIZE或WM_WINDOWPOSCHANGED消息。如果您正在使用PocketPC,我建议您首先查看WM_WINDOWPOSCHANGED消息,因为我不确定WM_SIZE是否具有您需要的正确参数。

From the WM_WINDOWPOSCHANGED message's WINDOWPOS structure take a look at the flags member, specifically SWP_SHOWWINDOW and SWP_HIDEWINDOW.

从WM_WINDOWPOSCHANGED消息的WINDOWPOS结构中看一下flags成员,特别是SWP_SHOWWINDOW和SWP_HIDEWINDOW。

The specific version of the messages that you need to look at vary with what operating system you're using. The Pocket PC OS is built on Windows CE 3.0 (and lower), while Windows Mobile is now built on Windows CE 5.0 (even Windows Mobile 6), but was also built on Windows CE 4. (Source)

您需要查看的消息的特定版本因您使用的操作系统而异。 Pocket PC OS基于Windows CE 3.0(及更低版本)构建,而Windows Mobile现在基于Windows CE 5.0(甚至Windows Mobile 6)构建,但也构建于Windows CE 4上。(来源)

So just look under the relevant section in MSDN for the OS that you're writing for.

因此,请查看MSDN中与您正在编写的操作系统相关的部分。

0  

I don't know what these are called in the C++ world, but in .NET Compact Framework your application form's Resize event would be called when you minimize/maximize a window, and then in the event code you would check the WindowState property of the form to see if its minimized or mazimized.

我不知道在C ++世界中调用了什么,但在.NET Compact Framework中,当您最小化/最大化窗口时,将调用应用程序窗体的Resize事件,然后在事件代码中检查WindowState属性。形式,看它是否最小化或mazimized。

Altering the state of your PDA from within your application is risky (although there are lots of good reasons to do it), because if your app crashes it will leave the PDA in whatever state it was in. I've done a lot of kiosk-type (full-screen) apps in Windows Mobile, and one of the tricks to doing this effectively is to hide the WM title bar (the top row with the Windows start button) to keep it from flashing up for a split second every time you open a new form. If the app crashes, the windows bar remains invisible until you reset the device, which isn't good. At least with screen rotation the user can restore it manually.

从你的应用程序中改变你的PDA的状态是有风险的(虽然有很多很好的理由去做),因为如果你的应用程序崩溃,它将使PDA处于它所处的任何状态。我做了很多自助服务终端Windows Mobile中的类型(全屏)应用程序,有效地执行此操作的一个技巧是隐藏WM标题栏(带有Windows开始按钮的顶行),以防止它每次闪烁一瞬间你打开一个新表格。如果应用程序崩溃,Windows栏将保持不可见,直到您重置设备,这是不好的。至少在屏幕旋转时,用户可以手动恢复它。

0  

It really depends on the platform, but I'd go with WM_WINDOWPOSCHANGED or the OnShow. It's not wm_size.. That one is not always thrown on all platforms. Casio's don't throw the size event when you'd expect them to. TDS and Symbol's do.

它真的取决于平台,但我会选择WM_WINDOWPOSCHANGED或OnShow。它不是wm_size ..并不总是抛出所有平台。当你期望它们时,卡西欧不会抛出尺寸事件。 TDS和Symbol的确如此。

Even though the MSDN is a great sourse for info, remember not all OS's are created equal. In the PPC world the hardware provider gets to create their own OS and sometimes the miss things, or purposfully ignore things.

即使MSDN是一个很好的信息源,但请记住并非所有操作系统都是平等的。在PPC世界中,硬件提供商可以创建自己的操作系统,有时可以创建错过的东西,或者有意忽略内容。

I've got a platform here (name withheld to protect... well me) that has left and right buttons.. When you press them, you'd expect to be able to catch VK_LEFT, VK_RIGHT.. You'd be wrong. You actually get ';' or ':'. How's that for a kick in the pants.

我有一个平台(名字保留,以保护......好吧),左右按钮..当你按下它们时,你希望能够捕捉到VK_LEFT,VK_RIGHT ..你错了。你真的得到';'要么 ':'。怎么样才能穿上裤子。