Home/ Questions/Q 7644223
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T09:38:00+00:00

Okay, serious dilemma. I am trying to wrap the Windows API. and the biggest

  • 0

Okay, serious dilemma. I am trying to wrap the Windows API. and the biggest design problem I’ve run into (for now) is what class is suitable for wrapping what? Since I’ve created a Windows API wrapper about three times before, always running into a design issue in the middle of things, this time, I intend to tread carefully, asking the confusing parts over here before implementing them.

Should the WNDCLASS and the main windows created by CreateWindow be wrapped in a single class or separate classes? Should I create a singleton to hold the WNDCLASS?

Also, if anyone can give me a flow-chart or general idea, on how to abstract the Windows API into classes, some good design tips?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    For a good source of inspiration, look at the .Net framework – there is no concept of WNDCLASS! You could have your library create a WNDCLASS that is shared by all your windows. You don’t need singletons (uurrgghhh) since the class can be used by a string. If you want to change some of the characteristics that WNDCLASS defines for a particular window, I think you can use the SetWindowLongPtr function.

    Things to consider:

    1. Would there be a need to have multiple WNDCLASS instances?
    2. Do you want clients to access the WNDCLASS data?
    3. Is there a one-to-one relationship between windows and WNDCLASS or is it one-to-many?
    • 0