-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Property Pages #140
Comments
I never used property sheets before, but as far as I could see, its implementation isn't straightforward... so far, I found this example, is it enough for your needs? Do you have a better one? I will start implementing |
I just uploaded a barebones example of making a property sheet page here: propsheetpage-example. What I was thinking winsafe could do is give me the same type of abstraction as a normal window or dialog from resource id, except instead of running the dialog directly, it could give me an HPROPSHEETPAGE. The |
Yes, I'm think the same: provide a high-level abstraction, reusing the same existing dialog event API. But besides that, the foundation must also exist and be usable on itself, and I'm really careful writing the best possible abstraction around it, and your example will be greatly useful. Thank you very much. |
I pushed the preliminar versions (still very unsafe) of See how much of a lifetime hell this is... |
I'm working on writing an MMC Snap-in, and I'd like to use winsafe to handle property sheet pages. All MMC wants is for you to create your property sheet pages using the Win32
CreatePropertySheetPage
function, then pass the returnedHPROPSHEETPAGE
to the supplied COM interface (IPropertySheetCallback). It seems like property sheet pages are simply modeless dialog boxes presented in a tabular format, so I think that adapting should be simple enough.I briefly tried extending the library, creating a
PropsheetPage
struct similar to theRawModeless
struct, but I still haven't traced how everything would fit together. I could continue to try implementing it, but it would help if I could get some guidance on a preferred structure for the implementation.The text was updated successfully, but these errors were encountered: