Mobile

The problem with CE is that it will not support printing as we know it on the desktop. In another post, Daniel S talks about sending AT commands via IR to the printer. This may be one solution. Another one, might be using a third-party software. Check HP[^], they have a free printing tool for iPAQs.

You are right about the CPU type. As a matter of fact, you can produce executables for ARM (StrongARM) and the emulator. When you choose the emulator on your project setting, all the compiler's output (.obj, .dll, .exe) goes to the x86debug or x86release (or whatever they are named in your setup). Before generating any output, make sure you have selected the correct target. ;) Don't worry too much about this mistake: from my experience everybody does that, especially when targetting multiple platforms, or when transitioning from the debug to the shipping version of the product (it happended to me just yesterday). Regards, João

I'm a bit in the cold with that issue. Maybe you want to take a look at the bitmaps section here in CP. Good luck!

hi, this looks good. i'll try it out...thanx in advance! DasWeasel

Heed these words of caution, from someone already charred by tough experience: don't think about it! The emulator is not very stable in Windows 2000, so don't expect it to work on the nimble 98... My experience with the emulator on an updated W2K is one of sudden and unexpected reboots, not even blue screens! Beware of the wild emulator!

Thank you for the suggestions. I appreciate the input.

I don't know of any books, however, d/l either eVC++ 3.0/4.0 from msdn and the documentation with it will get you well on your way. There are also many examples in the SDK, depending on what platform your developing on. Also, depending on what you chose to program with, ie. MFC,WIN32, you can still get a book that isn't necessarily for embedded, but Windows itself. Like Programming Windows MFC - J.Prosise helps me learn MFC, which helps me program eVC++4.0 with MFC. Alot, maybe 90% of Windows programming can apply to embedded Windows programming. :-O Good luck! R.Bischoff | C++   .NET, Kommst du mit?

Found another one http://www.intrinsyc.com/products/pda[^] . R.Bischoff | C++   .NET, Kommst du mit?

It should be. As far as I can tell, the PXA250 publishes itself as a StrongARM. If you test the processor number, you will get 2577. If you want your app to run on the PXA250 only, I suggest you read the following article on PocketPC Developer's Network: http://www.pocketpcdn.com/qa/processor_type.html[^] Have fun!

Unfortunately, this doesn't work too. The white areas are painted after the background paint. And they are always white, even if you set different color for window background for entire Windows (in Control Panel ->Display Settings) Anyway, thanks for effort. Ortie

MFC is far more documented than WTL. It will generate bulkier executables, and its whole architecture is less elegant than WTL's. The problem with WTL is the lacking of an "official" documentation. But you can always find WTL docs on the web. You can start here in CP or go to the following sites: http://www.idevresource.com/wtl/[^] http://www.viksoe.dk/wtl/[^] http://63.193.123.11/wtl/[^] http://www.gurlpages.com/wtl/[^] If you find other sites, please let me know.

If you are using the PocketPC HTML control, you can set up a timer in the containing window, and have the timer handler send a navigate message to the control. Make sure that 15 seconds is enough to read in the full page.

Maybe this code might help Desc: is a sample demonstrating using the Pocket Outlook Object mode (via COM interop). The application lets you view all of the contacts on your Pocket PC, add new ones, and delete existing ones. It consists of a managed application built on top of the .NET Compact Framework and a native DLL written in C++ using eMbedded Visual C++ 3.0. The source for both the managed and native components is provided. Written in C# Source: http://www.gotdotnet.com/team/netcf/samples/POOM/POOM.zip Good Luck! R.Bischoff | C++   .NET, Kommst du mit?

How about eVC>Tools>Remote File Viewer? That allows you to import and extract files between (emulation) device and desktop. Once there, you can use regsvrce on the device to register the component as normal. -- Ian Darling

Hello, Try to use the registry. Use the following registry functions: RegCreateKeyEx RegOpenKeyEx RegCloseKey RegDeleteValue RegQueryValueEx RegSetValueEx RegEnumKeyEx Raphael Amorim Dantas Leite VC++, VB, Java, .NET and eMbedded Programmer

Hello, Try to use the registry. Use the following registry functions: RegCreateKeyEx RegOpenKeyEx RegCloseKey RegDeleteValue RegQueryValueEx RegSetValueEx RegEnumKeyEx Raphael Amorim Dantas Leite VC++, VB, Java, .NET and eMbedded Programmer

BUG: LNK2019 When Building For Pocket PC Emulation SYMPTOMS When building an application for Pocket PC emulation that uses the Windows CE operating system functions, errors similar to the following may be encountered: <filename>.obj : error LNK2019: unresolved external symbol _CeDeleteDatabase referenced in function <function> CAUSE These operating system functions use the _stdcall calling convention, but the compiler is declaring them as _cdecl. This problem occurs with the Windows CE Platform SDK for Pocket PC because the functions are incorrectly declared in the Windbase.h file without a linkage type. RESOLUTION Use one of the following workarounds: Add the /Gz compiler switch to the configuration's project settings when building for Pocket PC emulation. -or- If the first workaround prevents other functions/libraries from linking in your project, then modify the Windows CE database function declarations in the Windbase.h file. For example, for the error in the "Symptoms" section, change the following declaration BOOL CeDeleteDatabase (CEOID oid); to read: BOOL WINAPI CeDeleteDatabase (CEOID oid); STATUS Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. Raphael Amorim Dantas Leite VC++, VB, Java, .NET and eMbedded Programmer