Windows Mobile Shell Blog

hey ammon, great to see some LAP expertise up in the blogosphere. i've been developing my own WM5 LAP for a while now and it's pretty confusing at times, especially given the errrr fluid state of the API, doc, and available samples.

but anyway...

here's a question for you. what's the WS_EX_ABOVESTARTUP style bit all about?

it's not doc'd anywhere i've seen, yet i've seen it in some samples, and in my own experimentation, it's the only way i can get a LAP verify dialog to show up properly (my LAP verify dlg is a popup, created with the owner being the dialog handle passed to me from the LASS.

Craig, thanks for your question. It's been a while, so hopefully you're still monitoring this post for an answer.

In Windows Mobile 5.0, WS_EX_ABOVESTARTUP was a bit confusing. Sometimes you need it set, sometimes you don't (for anyone else reading, this is an EXSTYLE for LAP windows). If your LAP creates a new thread, any windows on that thread will require this flag (the LAP sample from the WM5.0 SDK has a separate thread). Otherwise, anything in the main LAP thread will receive that setting automatically.

In WM 5.0 AKU2 we simplified it. Now all windows that are part of a LAP *must* include this style in order to be displayed. You'll see this documented in the next SDK release.

Hi Ammon, I have written a password LAP which works fine in general, but my app has a reauthenticate timout feature which forces a VerifyUser after a set time. This is fine, unless the unit is powered off while the LAP window is active. If this happens, when I power on  I simply get a white screen with the word Start in the top bar.

I am creating the main dialog in the VerifyUser call, which waits until completion, but not fully sure if this want's to be asyncronous or not?

You mention a threaded sample  in the WM5.0 SDK, but I can't seem to locate this. Would it be possible to post a link on this blog?

Thanks Mark

Hello Ammon.  
I have written a replacement password LAP that has worked fine on both Pocket PC and Smart Phone for some time now;  however, with the advent of AKU2.0, it no longer works.  I have made the documented changes to facilitate the NO_UI option bit, but my verification dialog is never displayed.  I get a stream of the customary init, activate, and sizing messages, but I never get a paint before the start screen covers me forever.  There is a mysterious RegisteredMessage and a WM_WININICHAGE that I don't recall getting before.  I have several PPC devices with updated AKU2 ROMs that exhibit identical behavior.  I have done numerous experiments with the adapted LetMeIn and WM5 platform builder PLUGIN pwlap sample, but neither works correctly. Is there any updated WM5 documentation and/or sample available?  
Thanks David

Hello,
I'd like to know if there is a way to manually lock the device ? I read that there is a SHDeviceLockAndPrompt() function but it is seems not to be available in the Pocket PC SDK yet. A call to VerifyUser is not sufficient because it does not block the UI and ActiveSync connections.
Thanks Nicolas

Where can i find sample example for creating a custom LAP in Windows Mobile 5 Pocket PC as well as Windows Mobile 5 Smart Phone?

The Sample i got from Marcus Perryman's WebLog does not seem to work on my HP hx6960 WM5 Smart Phone which is using AKU2 (MSFP) OS build of WM5.

I wanted the LAP to load everytime i power on / off the PDA, it works for my Pocket PC which is using an older OS build of WM5, however when it comes to Smart Phone it fails to load.

I wonder if the cause is due to the different OS builds or due to the differences in Pocket PC and Smart Phone platform.

I found out that everytime i power on/off, the dwoption parameter pass in to the verifyUser is always VU_NO_UI. How is this so?

Hello Ammon.

I wrote custom LAP on  Windows Mobile 5.0 ppc.

The name of my device is Dopod D600.

My custom lap is working well on the emulator.

On the device, enrollment dialog is displayed, but verify dialog is not displayed after soft reset.

So I checked the parameter of verifyuser(LAP) function, and found out the dwOption parameter was always VU_NO_UI on device unlike emulator.  

Because of this problem, I have spent a lot of time.

I can't this solution anywhere.

Please help me.!!!

Regards.