indicating APIs
-
You've got some great code examples. Was just wondering if there was a way to more clearly indicate what's required, MFC, Win32, other APIs, other class or GUI libraries, etc. I've seen some articles listed as MFC classes that don't require any MFC. While this code might be very helpful to a Win32 programmer, the basic description will scare them off. Some of the code might even be useful on non-Windows platforms if it strictly follows the C/C++ standards. It would be nice if developers could more easily tell what the intended development targets were. Thanks.
-
You've got some great code examples. Was just wondering if there was a way to more clearly indicate what's required, MFC, Win32, other APIs, other class or GUI libraries, etc. I've seen some articles listed as MFC classes that don't require any MFC. While this code might be very helpful to a Win32 programmer, the basic description will scare them off. Some of the code might even be useful on non-Windows platforms if it strictly follows the C/C++ standards. It would be nice if developers could more easily tell what the intended development targets were. Thanks.
Hi Laura, This is definitely something that is in the works. ================== The original message was: You've got some great code examples. Was just wondering if there was a way to more clearly indicate what's required, MFC, Win32, other APIs, other class or GUI libraries, etc. I've seen some articles listed as MFC classes that don't require any MFC. While this code might be very helpful to a Win32 programmer, the basic description will scare them off. Some of the code might even be useful on non-Windows platforms if it strictly follows the C/C++ standards. It would be nice if developers could more easily tell what the intended development targets were.
Thanks.