[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Microwindows Win32 API doc.
From: Fabrice Gautier ####@####.#### Date: 30 Jan 2002 04:35:35 -0000 Message-Id: <B1F6452C89AFD411AE0800A0CC734C239DBAFE@EMAIL1> Hi, The only win32 API docs i found is in the "architecture" document. Is there anything more up to date? Or is it simply that the win32 API is less maintened than the nano-X api and i shoudl stick to nano-X for new projects? Thanks -- Fabrice Gautier, ####@####.#### | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Microwindows Win32 API doc.
From: "Greg Haerr" ####@####.#### Date: 30 Jan 2002 04:46:11 -0000 Message-Id: <031f01c1a947$31e44460$3aba46a6@xmission.com> : The only win32 API docs i found is in the "architecture" document. : : Is there anything more up to date? The Win32 API is almost exact so the reference docs are available in most bookstores. Yes, we should have a list of the GDI that's implemented, most are, for the lowest level stuff. Resource management and dialogs aren't implemented. : : Or is it simply that the win32 API is less maintened than the nano-X api and : i shoudl stick to nano-X for new projects? Nano-X is required for multi-process works or anything where there may be more than one graphical application at a time. Win32 is good for a single dedicated application that was previously written for Windows or where the programmer is a Windows-oriented. Regards, Greg : : Thanks : -- : Fabrice Gautier, : ####@####.#### : : --------------------------------------------------------------------- : To unsubscribe, e-mail: ####@####.#### : For additional commands, e-mail: ####@####.#### : | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |