thanks for the info. unfortunately i don't use mfc so the macro won't help me. since printf is supported via coredll.lib, i thought i'd read somewhere of folks creating a console driver and putting it in the windows directory of the ppc for quick-n-dirty debugging. i'll play with console redirects to a file via the undocumented SetStdioPathW() function from coredll.lib to see easy logging to a file is. any other ideas would be appreciated....thanks
Hi John, I remember that you once asked about how to write a Wizard-like dialog for the Pocket PC. Here is one answer: QA: How can I use a property sheet to implement a Wizard?[^]. Hope you find it useful! Regards, João Paulo
To solve the font-side of the problem, try to locate a set of TrueType fonts that will have all the character sets you need. Download them to the device's \Windows\Fonts directory to make them available. Regards, João Paulo
Had the same problem! It's because C Run-Time libraries are linked before MFC libraries. Take a look at http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q148/6/52.asp&NoWebContent=1[^] for the solution!
Hi Atlantys - did I ever reply to this? :-O If I didn't, I'm sorry - didn't notice that there was a reply here :-O Anyway, the answer is yes, I'll be using plain WinCE. I'll wait till .NET CF comes standard with the OS first. I'm the same, I also don't want to mess my PPC up :-D I'm really enjoying programming with eVC++ - I think it's a geekish novelty value, seeing my creations run on that small mobile device :-) Paul ;)
Tiny problem with said member has been corrected.
Chris Maunder