When searching for examples of Win32 API code, I see many of examples of constant values with names like "IDC_OUTPUT" in resource scripts, resource.h files or defined at the top of apps, typically being used to identify dialog controls or child windows, etc. However, the value that this constant evaluates to varies quite alot. For example, I see values such as 101, 1001, 1003, 1101, 2015, even 40003.
I suppose this is just a name that represents an arbitrary value. But why "IDC_OUTPUT"? Where did the name come from? Does this name infer some special meaning? Is there a reason that this name would be preferred over some other name such as "FOO_BAR"? For example, is there any good reason why I would want to choose the name IDC_OUTPUT instead of the name I picked in the following snippet?
#define FOO_BAR 1001 CreateWindowEx ( WS_EX_WINDOWEDGE, "SomeWindow", "SomeWindow", WS_CHILD|WS_VISIBLE|WS_SIZEBOX|WS_BORDER|WS_CAPTION, 10,10,200,200, hWnd, (HMENU)FOO_BAR, // instead of "IDC_OUTPUT" (HINSTANCE)GetWindowLongPtr(hWnd,0), 0 );