UniPicture Class / Objects

Windows only permits 1024 active bitmap/icon handles to be in use at any time. UniPicture provides a method to store data for more than 1024 Bitmaps/Icons without depleting user/gdi heap memory and the restrictions imposed by the operating system.

screen-shot

UniPicture also provides you with Procedures to:

  1. Store the raw data of a StdPicture Object in the UniPicture Object
  2. Convert a Windows BitMap Handle to a StdPicture
  3. Convert a Windows Icon Handle to a StdPicture
  4. Obtain a Windows Bitmap Handle for a copy of a StdPicture
  5. Obtain a Windows Icon Handle for a copy of a StdPicture
  6. Render the BitMap held by a UniPicture Object to a hDC
  7. Render the Icon held by a UniPicture Object to a hDC
  8. Resize and Render the Icon held by a UniPicture Object to a hDC
  9. Retieve the Bitmap/Icon held by a UniPicture Object as an array of Bytes.
  10. Persist the Bitmap/Icon held by a UniPicture Object to a PropertyBag.
  11. Create a copy of a stdPicture or a BitMap/Icon Handle

UniPicture is supplied as 32 Bit Visual Basic 5.x and/or 6.x Source Code. You have a royalty-free right to use, modify, reproduce and distribute the code for UniPicture.cls and IuniPicture.cls in any way you find usefull, provided:

  1. You rename the class object UniPicture.cls
  2. You implement the IuniPict Interface
  3. You do not use the name UniPicture in any ActiveX object
  4. You do not alter the data types and procedure declarations herein or interfere with version compatability of the base UniPicture and IuniPicture interfaces
  5. Provided that you agree that Brian D. Parkinson has no warranty, obligations or liability for any Application Programs/Files distributed incorporating the code.

You may add your own procedures to perform additional operations only if you do not call the class object UniPicture or implement it as a member of the IuniPict Interface.

It is suggested you place UniPicture and IUniPicture in an ActiveX DLL. This maintains a constant GUID for the Objects UniPicture - file UniPicture.cls and UniPicture - file IuniPicture.cls.

COPYRIGHT

Copyright © 1999 Brian D. Parkinson(brian@Iceminster.com). All rights reserved.

CLASSWIZ5

UniPicture is one of a number of source code files in ClassWiz5 Add-In which generates Visual Basic Code for various types of Lists, Keyed Lists, Queues, PropertyBags and Classes and Interfaces.

FREE DOWNLOAD a fully operational demonstration version of ClassWiz5 from the author's homepage

ClassWiz5 is a Visual Basic Code Generator Add-In developed by Brian Parkinson of www.iceminster.com. Information about ClassWiz is provided at the end of the code for UniPicture.

Source code for ICWPropertyBag, CWPropertyBag and modClassWiz may not be distributed and you require a licenced version of ClassWiz to obtain the VB Code for these objects.

You are authorized to use/modify/distribute the code in this UniPicture.cls class object and IuniPicture.cls provided you include the notices enclosed by the words StartNotice and End Notice

REGISTER

If you register your use of this code by Email to 'brian@iceminster.com' you will be kept informed of any changes or other issues related to the code. You will also be provided with access to a special Code area of iceminster.com.

Download zipped Classes and Examples (36k)



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • On-demand Event Event Date: March 27, 2014 Teams need to deliver quality software faster and need integrated agile planning, task tracking, source control, auto deploy with continuous builds and a configurable process to adapt to the way you work. Rational Team Concert and DevOps Services (JazzHub) have everything you need to build great software, integrated seamlessly together right out of the box or available immediately in the cloud. And with the Rational Team Concert Client, you can connect your …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds