First Project - Page 2

gwinter · 07-22-06, 07:50 AM

Originally Posted by SiGriffin

1) I don't really understand what part the SDK plays. All I have so far is the SDK for Pocket PC 2002 which came with eVT3.0. I would like to keep the app backwards compatible, so is this what I should be using or should it be the SDK for WM5? Also should I actually be using eVC4?

The SDK contains 2 things are that important:
- declarations/prototypes (or, how the compiler know there's such a function call MessageBox, or what PAINTSTRUCT data type is.)
- the library files or the stubs that will will need to be linked into your program code. The stubs helps resolve function calls to system dlls.

Newer versions of SDK enables you to make use of new functions that are not available in older versions. eVT 3.0 is required to compile programs for PPC2000, PPC2002. evC 4 is required for WM2003 and later. Look at the summary that I posted over the PPCThoughts. I've a bit to say about WM5 SDK in a moment.

Originally Posted by SiGriffin

2) Why would the .exe run on my device but appear to be not supported on the supplied emulator?

This is not a bug or anything. The emulators that shipped prior to Visual Studio 2005, are actually x86 emulators. It CANNOT run .exe file for ARM, which is what runs on your device. Therefore normally during development, one would probably have at least 2 targets for each project: emulator (Debug or Retail) and ARM (Retail).

WM5 SDK is, frankly, a pain when you don't have Visual Studio. The last time I checked, it actually required VS2005 to install. Of course, one can still have the package extracted and use it with eVC4, which is what I did. Now, the problem arises with the library files, which you'll recall, are the stubs that get binded to your code. Therefore these library files are specific to a processor type. Normally this shouldn't be a problem, since WM2003 and WM5 both uses the same processors, right? Unfortunately, the signature for WM2003 and earlier libraries are ARM; whereas in WM5 it has been changed to ARM5I (Note: I don't remember the signature exactly, but you get the point).
During my test, programs with ARM signature will run on all system; but programs with ARM5I signature will only run on WM5 system. So I guess, you can't just use WM5 SDK for all platforms, even when your program is just using a small set of functions that should actually even run on PPC2000.

Pocketbrain · 07-22-06, 06:56 PM

Revised version of the landscape RipBoard layout...
Moved the D-keys and put math functions next to the numpad. Note it's not perfect.
http://www.aximsite.com/boards/showp...4&postcount=45

SiGriffin · 07-24-06, 03:27 AM

Thanks for the info gwinter, that is really helpful.

PocketBrain, that keyboard is coming along nicely!

SiGriffin · 07-26-06, 08:17 AM

The code that this project is ported from uses either mkstemp or tmpnam to generate a temporary file name. I am struggling to find an equivalent function in eVC3.0. Does anyone know if there is such a thing or do I need to write one myself?

Many thanks,
Si

SiGriffin · 07-31-06, 04:00 AM

Similarly there is a function called FrameRect that is used. I have found that it is in something called CDC which I assume is some sort of function library. Is this a part of VS or can I get hold of it for free?

Si

SiGriffin · 08-08-06, 10:06 AM

Originally Posted by SiGriffin

Similarly there is a function called FrameRect that is used.

Well in the end I rewrote this:
FrameRect(hdc, &rc, hbrYellow);
as:
hPenYellow = CreatePen(PS_SOLID, 1, win_clr[TERM_YELLOW]);
hOldPen = (HPEN)SelectObject(hdc, hPenYellow);
lines[0].x = rc.left;
lines[0].y = rc.top;
lines[1].x = rc.right - 1;
lines[1].y = rc.top;
lines[2].x = rc.right - 1;
lines[2].y = rc.bottom - 1;
lines[3].x = rc.left;
lines[3].y = rc.bottom -1;
lines[4].x = rc.left;
lines[4].y = rc.top;
Polyline(hdc, lines, 5);
SelectObject(hdc, hOldPen);
DeleteObject(hPenYellow);

Which does the trick, though I am sure there must be a more efficient way of doing this.

I haven't found a replacement for tmpnam yet, so I guess I will have to attempt to code something.

SiGriffin · 08-21-06, 04:00 AM

Originally Posted by SiGriffin

The code that this project is ported from uses either mkstemp or tmpnam to generate a temporary file name. I am struggling to find an equivalent function in eVC3.0. Does anyone know if there is such a thing or do I need to write one myself?

For info I managed to do the same job using GetTempPath and GetTempFileName.