SDK coding with Resource Dialog

[James C. Fuller]

Patrice,
  Is it possible to do your style of SDK coding using a resource dialog with the CLASS defined?

James

[Patrice Terrier]

James,

I am unsure of what you mean.
The CreateDialog API uses a limited subset of the CreateWondowEx API, thus i have never used a resource dialog editor, because for me it is like going back more than ten years ago 

Currently i am using a screen editor, to create my popup windows and populate them with child controls, then i grab the content with a utility working like "pbwinspy".
PCSoft (WinDev) starts its success story more than 20 years ago, with a utility named "HighScreen/HyperScreen" and so far it always seemed to me a good way to go. At the time I wrote the first WinLIFT i thought to write myself a super Form designer, with built-in custom controls, automatic anchor mode, skin theme support. But very soon i came to the conclusion that there was no market for it with PB, especially because there was already too much form designers for such a small market (PB Form, FireFly, EZGui, Phoenix).

...

[James C. Fuller]

Patrice,

The CreateDialog API uses a limited subset of the CreateWondowEx API

Would you explain this a little more?

My understanding is by using  CLASS in a resource dialog you are using your own class which you must register just like your sdk method.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa380883(v=vs.85).aspx

James

[Patrice Terrier]

Yes you are using your own class, however it is based on the CreateDialog not the CreateWindowEx.

One is using DefDlgProc callbak and the WM_INITDIALOG message.
While the other is using DefWindowProc callback and the WM_CREATE message, more universel, because there is not difference between a popup window and a child window, except the WS_POPUP/WS_CHILD style.

When using the default processing of the CreateDialog API, things are getting rather complex as soon as you want to control everything, especially when you have to deal with the caption or the non-client area of the form, because Windows redraws the default OS border and caption theme each time you maximize/restore a window.

...