home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.programmer.misc:3361 comp.os.ms-windows.programmer.win32:1913
- Path: sparky!uunet!ogicse!uwm.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!sgiblab!sti.com!westes
- From: westes@sti.com (Will Estes)
- Newsgroups: comp.os.ms-windows.programmer.misc,comp.os.ms-windows.programmer.win32
- Subject: How To Store Resources For Different Types Of Monitors
- Message-ID: <BxJAs3.2Mw@sti.com>
- Date: 11 Nov 92 04:21:38 GMT
- Article-I.D.: sti.BxJAs3.2Mw
- Sender: usenet@sti.com
- Organization: Mail Group
- Lines: 32
- Nntp-Posting-Host: smurf
-
- I have two questions regarding the support for different color schemes.
-
- Suppose you wanted one application to work with all kinds of monitors,
- from black-and-white through 24-bit, and that you had prepared a set of
- resources for each of five different color sets:
-
- - B&W
- - 4-color
- - 16-color
- - 256-color
- - 24-bit
-
- The two questions are:
-
- 1) What is the optimum way to save the resources? Is it better to
- create separate resource-only DLLs (i.e., one for each color scheme),
- and then load resources from the appropriate DLL, or is it better to
- keep all of the resources in a single DLL and then load as appropriate
- from the one DLL? To the extent that a LoadResource() takes up memory
- for just the resource and not the entire DLL, would it make any difference
- in terms of disk space (obviously not), memory utilization (?), or resource
- consumption (probably not)?
-
- 2) As a practical matter, which different color schemes do you need
- to be concerned about supporting? For example, I assume that a 24-bit
- resource would probably display pretty well on a 256-color monitor, so
- maybe it is best to just skip developing a separate set of resources for
- 256-color? I'm looking for comments from those who have had to support
- different color schemes.
-
- --
- Will Estes Internet: westes@netcom.com
-