home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!mcsun!sun4nl!tnofel!felfs!rioj7
- From: rioj7@fel.tno.nl (M.L.M.Veraart)
- Subject: Re: Custom Controls and their Properties
- Organization: TNO Physics and Electronics Laboratory
- Date: Thu, 21 Jan 93 07:43:52 GMT
- Message-ID: <1993Jan21.074352.17443@fel.tno.nl>
- References: <1426@ottawa.opl.com.opl.com>
- Lines: 34
-
- scott@opl.com (Scott Evernden) writes:
-
- >I want to build some installable custom controls.
-
- >These controls will maintain properties that I want interface designers be able
- >to set at design time via Dialog Editor or Resource Workshop. To work with
- >these tools, I develop a style dialog which my control DLL will run when its
- >ControlStyle() function is called. The style dialog collects values for the
- >properties of my control; most of these properties cannot simply be encoded as
- >some style bits..
-
- >My problem is: how do I stuff the values of properties set at design time
- >(collected via my style dialog) into the resource file produced by Dialog
- >Editor or Resource Workshop? Is this even possible?
-
- [.. further examples deleted ..]
-
- Scott,
-
- a possible solution is to build the dialog completely on your own
- using calls to CreateWindow for every dialog item you want. The settings
- of the individual controls can be stored in a private .INI file.
- Maybe it is possible to used a template resource in .rc file that has
- the controls that are not to be configured.
-
- Hoping this will be a solution, I haven't inplemented it myself.
-
- Mario Veraart
- email: mveraart@fel.tno.nl
- --
- Mario Veraart TNO Physics and Electronics Laboratory
- email: rioj7@fel.tno.nl The Hague The Netherlands
- "If all else fails, show pretty pictures and animated videos,
- and don't talk about performance", David Bailey
-