Information about the use of third-party software and open source software in Armadain Photos

Information about the use of third-party software and open source software in Armadain Photos

The Independent JPEG Group’s JPEG software

The Independent JPEG Group's JPEG softwareThe Independent JPEG Group's JPEG software==========================================
README for release 6b of 27-Mar-1998====================================
This distribution contains the sixth public release of the Independent JPEGGroup's free JPEG software.  You are welcome to redistribute this software andto use it for any purpose, subject to the conditions under LEGAL ISSUES, below.
Serious users of this software (particularly those incorporating it intolarger programs) should contact IJG at to be added toour electronic mailing list.  Mailing list members are notified of updatesand have a chance to participate in technical discussions, etc.
This software is the work of Tom Lane, Philip Gladstone, Jim Boucher,Lee Crocker, Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi,Guido Vollbeding, Ge' Weijers, and other members of the Independent JPEGGroup.
IJG is not affiliated with the official ISO JPEG standards committee.

DOCUMENTATION ROADMAP=====================
This file contains the following sections:
OVERVIEW            General description of JPEG and the IJG software.LEGAL ISSUES        Copyright, lack of warranty, terms of distribution.REFERENCES          Where to learn more about JPEG.ARCHIVE LOCATIONS   Where to find newer versions of this software.RELATED SOFTWARE    Other stuff you should get.FILE FORMAT WARS    Software *not* to get.TO DO               Plans for future IJG releases.
Other documentation files in the distribution are:
User documentation:  install.doc       How to configure and install the IJG software.  usage.doc         Usage instructions for cjpeg, djpeg, jpegtran,                    rdjpgcom, and wrjpgcom.  *.1               Unix-style man pages for programs (same info as usage.doc).  wizard.doc        Advanced usage instructions for JPEG wizards only.  change.log        Version-to-version change highlights.Programmer and internal documentation:  libjpeg.doc       How to use the JPEG library in your own programs.  example.c         Sample code for calling the JPEG library.  structure.doc     Overview of the JPEG library's internal structure.  filelist.doc      Road map of IJG files.  coderules.doc     Coding style rules --- please read if you contribute code.
Please read at least the files install.doc and usage.doc.  Useful informationcan also be found in the JPEG FAQ (Frequently Asked Questions) article.  SeeARCHIVE LOCATIONS below to find out where to obtain the FAQ article.
If you want to understand how the JPEG code works, we suggest reading one ormore of the REFERENCES, then looking at the documentation files (in roughlythe order listed) before diving into the code.

This package contains C software to implement JPEG image compression anddecompression.  JPEG (pronounced "jay-peg") is a standardized compressionmethod for full-color and gray-scale images.  JPEG is intended for compressing"real-world" scenes; line drawings, cartoons and other non-realistic imagesare not its strong suit.  JPEG is lossy, meaning that the output image is notexactly identical to the input image.  Hence you must not use JPEG if youhave to have identical output bits.  However, on typical photographic images,very good compression levels can be obtained with no visible change, andremarkably high compression levels are possible if you can tolerate alow-quality image.  For more details, see the references, or just experimentwith various compression settings.
This software implements JPEG baseline, extended-sequential, and progressivecompression processes.  Provision is made for supporting all variants of theseprocesses, although some uncommon parameter settings aren't implemented yet.For legal reasons, we are not distributing code for the arithmetic-codingvariants of JPEG; see LEGAL ISSUES.  We have made no provision for supportingthe hierarchical or lossless processes defined in the standard.
We provide a set of library routines for reading and writing JPEG image files,plus two sample applications "cjpeg" and "djpeg", which use the library toperform conversion between JPEG and some other popular image file formats.The library is intended to be reused in other applications.
In order to support file conversion and viewing software, we have includedconsiderable functionality beyond the bare JPEG coding/decoding capability;for example, the color quantization modules are not strictly part of JPEGdecoding, but they are essential for output to colormapped file formats orcolormapped displays.  These extra functions can be compiled out of thelibrary if not required for a particular application.  We have also included"jpegtran", a utility for lossless transcoding between different JPEGprocesses, and "rdjpgcom" and "wrjpgcom", two simple applications forinserting and extracting textual comments in JFIF files.
The emphasis in designing this software has been on achieving portability andflexibility, while also making it fast enough to be useful.  In particular,the software is not intended to be read as a tutorial on JPEG.  (See theREFERENCES section for introductory material.)  Rather, it is intended tobe reliable, portable, industrial-strength code.  We do not claim to haveachieved that goal in every aspect of the software, but we strive for it.
We welcome the use of this software as a component of commercial products.No royalty is required, but we do ask for an acknowledgement in productdocumentation, as described under LEGAL ISSUES.

LEGAL ISSUES============
In plain English:
1. We don't promise that this software works.  (But if you find any bugs,   please let us know!)2. You can use this software for whatever you want.  You don't have to pay us.3. You may not pretend that you wrote this software.  If you use it in a   program, you must acknowledge somewhere in your documentation that   you've used the IJG code.
In legalese:
The authors make NO WARRANTY or representation, either express or implied,with respect to this software, its quality, accuracy, merchantability, orfitness for a particular purpose.  This software is provided "AS IS", and you,its user, assume the entire risk as to its quality and accuracy.
This software is copyright (C) 1991-1998, Thomas G. Lane.All Rights Reserved except as specified below.
Permission is hereby granted to use, copy, modify, and distribute thissoftware (or portions thereof) for any purpose, without fee, subject to theseconditions:(1) If any part of the source code for this software is distributed, then thisREADME file must be included, with this copyright and no-warranty noticeunaltered; and any additions, deletions, or changes to the original filesmust be clearly indicated in accompanying documentation.(2) If only executable code is distributed, then the accompanyingdocumentation must state that "this software is based in part on the work ofthe Independent JPEG Group".(3) Permission for use of this software is granted only if the user acceptsfull responsibility for any undesirable consequences; the authors acceptNO LIABILITY for damages of any kind.
These conditions apply to any software derived from or based on the IJG code,not just to the unmodified library.  If you use our work, you ought toacknowledge us.
Permission is NOT granted for the use of any IJG author's name or company namein advertising or publicity relating to this software or products derived fromit.  This software may be referred to only as "the Independent JPEG Group'ssoftware".
We specifically permit and encourage the use of this software as the basis ofcommercial products, provided that all warranty or liability claims areassumed by the product vendor.

ansi2knr.c is included in this distribution by permission of L. Peter Deutsch,sole proprietor of its copyright holder, Aladdin Enterprises of Menlo Park, CA.ansi2knr.c is NOT covered by the above copyright and conditions, but insteadby the usual distribution terms of the Free Software Foundation; principally,that you must include source code if you redistribute it.  (See the fileansi2knr.c for full details.)  However, since ansi2knr.c is not needed as partof any program generated from the IJG code, this does not limit you more thanthe foregoing paragraphs do.
The Unix configuration script "configure" was produced with GNU Autoconf.It is copyright by the Free Software Foundation but is freely distributable.The same holds for its supporting scripts (config.guess, config.sub,ltconfig,  Another support script, install-sh, is copyrightby M.I.T. but is also freely distributable.
It appears that the arithmetic coding option of the JPEG spec is covered bypatents owned by IBM, AT&T, and Mitsubishi.  Hence arithmetic coding cannotlegally be used without obtaining one or more licenses.  For this reason,support for arithmetic coding has been removed from the free JPEG software.(Since arithmetic coding provides only a marginal gain over the unpatentedHuffman mode, it is unlikely that very many implementations will support it.)So far as we are aware, there are no patent restrictions on the remainingcode.
The IJG distribution formerly included code to read and write GIF files.To avoid entanglement with the Unisys LZW patent, GIF reading support hasbeen removed altogether, and the GIF writer has been simplified to produce"uncompressed GIFs".  This technique does not use the LZW algorithm; theresulting GIF files are larger than usual, but are readable by all standardGIF decoders.
We are required to state that    "The Graphics Interchange Format(c) is the Copyright property of    CompuServe Incorporated.  GIF(sm) is a Service Mark property of    CompuServe Incorporated."

We highly recommend reading one or more of these references before trying tounderstand the innards of the JPEG software.
The best short technical introduction to the JPEG compression algorithm is Wallace, Gregory K.  "The JPEG Still Picture Compression Standard", Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.(Adjacent articles in that issue discuss MPEG motion picture compression,applications of JPEG, and related topics.)  If you don't have the CACM issuehandy, a PostScript file containing a revised version of Wallace's article isavailable at  The file (actuallya preprint for an article that appeared in IEEE Trans. Consumer Electronics)omits the sample images that appeared in CACM, but it includes correctionsand some added material.  Note: the Wallace article is copyright ACM and IEEE,and it may not be used for commercial purposes.
A somewhat less technical, more leisurely introduction to JPEG can be found in"The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published byM&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1.  This book providesgood explanations and example C code for a multitude of compression methodsincluding JPEG.  It is an excellent source if you are comfortable reading Ccode but don't know much about data compression in general.  The book's JPEGsample code is far from industrial-strength, but when you are ready to lookat a full implementation, you've got one here...
The best full description of JPEG is the textbook "JPEG Still Image DataCompression Standard" by William B. Pennebaker and Joan L. Mitchell, publishedby Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.  Price US$59.95, 638 pp.The book includes the complete text of the ISO JPEG standards (DIS 10918-1and draft DIS 10918-2).  This is by far the most complete exposition of JPEGin existence, and we highly recommend it.
The JPEG standard itself is not available electronically; you must order apaper copy through ISO or ITU.  (Unless you feel a need to own a certifiedofficial copy, we recommend buying the Pennebaker and Mitchell book instead;it's much cheaper and includes a great deal of useful explanatory material.)In the USA, copies of the standard may be ordered from ANSI Sales at (212)642-4900, or from Global Engineering Documents at (800) 854-7179.  (ANSIdoesn't take credit card orders, but Global does.)  It's not cheap: as of1992, ANSI was charging $95 for Part 1 and $47 for Part 2, plus 7%shipping/handling.  The standard is divided into two parts, Part 1 being theactual specification, while Part 2 covers compliance testing methods.  Part 1is titled "Digital Compression and Coding of Continuous-tone Still Images,Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS10918-1, ITU-T T.81.  Part 2 is titled "Digital Compression and Coding ofContinuous-tone Still Images, Part 2: Compliance testing" and has documentnumbers ISO/IEC IS 10918-2, ITU-T T.83.
Some extensions to the original JPEG standard are defined in JPEG Part 3,a newer ISO standard numbered ISO/IEC IS 10918-3 and ITU-T T.84.  IJGcurrently does not support any Part 3 extensions.
The JPEG standard does not specify all details of an interchangeable fileformat.  For the omitted details we follow the "JFIF" conventions, revision1.02.  A copy of the JFIF spec is available from: Literature Department C-Cube Microsystems, Inc. 1778 McCarthy Blvd. Milpitas, CA 95035 phone (408) 944-6300,  fax (408) 944-6314A PostScript version of this document is available by FTP at  There is also a plain textversion at, but it is missingthe figures.
The TIFF 6.0 file format specification can be obtained by FTP from  The JPEG incorporation schemefound in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).Instead, we recommend the JPEG design proposed by TIFF Technical Note #2(Compression tag 7).  Copies of this Note can be obtained from orfrom  It is expected that the next revisionof the TIFF spec will replace the 6.0 JPEG design with the Note's design.Although IJG's own code does not support TIFF/JPEG, the free libtiff libraryuses our library to implement TIFF/JPEG per the Note.  libtiff is availablefrom

ARCHIVE LOCATIONS=================
The "official" archive site for this software is (Internetaddress  The most recent released version can always be foundthere in directory graphics/jpeg.  This particular version will be archivedas  If you don't havedirect Internet access, UUNET's archives are also available via UUCP; for information on retrieving files that way.
Numerous Internet sites maintain copies of the UUNET files.  However, is guaranteed to have the latest official version.
You can also obtain this software in DOS-compatible "zip" archive format fromthe SimTel archives (, oron CompuServe in the Graphics Support forum (GO CIS:GRAPHSUP), library 12"JPEG Tools".  Again, these versions may sometimes lag behind the ftp.uu.netrelease.
The JPEG FAQ (Frequently Asked Questions) article is a useful source ofgeneral information about JPEG.  It is updated constantly and therefore isnot included in this distribution.  The FAQ is posted every two weeks toUsenet newsgroups, news.answers, and other groups.It is available on the World Wide Web at other news.answers archive sites, including the official news.answersarchive at you don't have Web or FTP access, send e-mail to body send usenet/news.answers/jpeg-faq/part1 send usenet/news.answers/jpeg-faq/part2

RELATED SOFTWARE================
Numerous viewing and image manipulation programs now support JPEG.  (Quite afew of them use this library to do so.)  The JPEG FAQ described above listssome of the more popular free and shareware viewers, and tells where toobtain them on Internet.
If you are on a Unix machine, we highly recommend Jef Poskanzer's freePBMPLUS software, which provides many useful operations on PPM-format imagefiles.  In particular, it can convert PPM images to and from a wide range ofother formats, thus making cjpeg/djpeg considerably more useful.  The latestversion is distributed by the NetPBM group, and is available from numeroussites, notably PBMPLUS/NETPBM is not nearly as portable as the IJG software is;you are likely to have difficulty making it work on any non-Unix machine.
A different free JPEG implementation, written by the PVRG group at Stanford,is available from  This programis designed for research and experimentation rather than production use;it is slower, harder to use, and less portable than the IJG code, but itis easier to read and modify.  Also, the PVRG code supports lossless JPEG,which we do not.  (On the other hand, it doesn't do progressive JPEG.)

FILE FORMAT WARS================
Some JPEG programs produce files that are not compatible with our library.The root of the problem is that the ISO JPEG committee failed to specify aconcrete file format.  Some vendors "filled in the blanks" on their own,creating proprietary formats that no one else could read.  (For example, noneof the early commercial JPEG implementations for the Macintosh were able toexchange compressed files.)
The file format we have adopted is called JFIF (see REFERENCES).  This formathas been agreed to by a number of major commercial JPEG vendors, and it hasbecome the de facto standard.  JFIF is a minimal or "low end" representation.We recommend the use of TIFF/JPEG (TIFF revision 6.0 as modified by TIFFTechnical Note #2) for "high end" applications that need to record a lot ofadditional data about an image.  TIFF/JPEG is fairly new and not yet widelysupported, unfortunately.
The upcoming JPEG Part 3 standard defines a file format called SPIFF.SPIFF is interoperable with JFIF, in the sense that most JFIF decoders shouldbe able to read the most common variant of SPIFF.  SPIFF has some technicaladvantages over JFIF, but its major claim to fame is simply that it is anofficial standard rather than an informal one.  At this point it is unclearwhether SPIFF will supersede JFIF or whether JFIF will remain the de-factostandard.  IJG intends to support SPIFF once the standard is frozen, but wehave not decided whether it should become our default output format or not.(In any case, our decoder will remain capable of reading JFIF indefinitely.)
Various proprietary file formats incorporating JPEG compression also exist.We have little or no sympathy for the existence of these formats.  Indeed,one of the original reasons for developing this free software was to helpforce convergence on common, open format standards for JPEG files.  Don'tuse a proprietary file format!

TO DO=====
The major thrust for v7 will probably be improvement of visual quality.The current method for scaling the quantization tables is known not to bevery good at low Q values.  We also intend to investigate block boundarysmoothing, "poor man's variable quantization", and other means of improvingquality-vs-file-size performance without sacrificing compatibility.
In future versions, we are considering supporting some of the upcoming JPEGPart 3 extensions --- principally, variable quantization and the SPIFF fileformat.
As always, speeding things up is of great interest.
Please send bug reports, offers of help, etc. to

Google Maps Library

(C) Xavier Martinez (cadetill)
Created with DelphiCodeToDoc. To obtain the latest revision, please visit

 Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. <>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.

0. Additional Definitions.

As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.

"The Library" refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.

An "Application" is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.

A "Combined Work" is a work produced by combining or linking an
Application with the Library. The particular version of the Library
with which the Combined Work was made is also called the "Linked

The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.

The "Corresponding Application Code" for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.

1. Exception to Section 3 of the GNU GPL.

You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.

2. Conveying Modified Versions.

If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified

a) under this License, provided that you make a good faith effort to
 ensure that, in the event an Application does not supply the
 function or data, the facility still operates, and performs
 whatever part of its purpose remains meaningful, or

b) under the GNU GPL, with none of the additional permissions of
 this License applicable to that copy.

3. Object Code Incorporating Material from Library Header Files.

The object code form of an Application may incorporate material from
a header file that is part of the Library. You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:

a) Give prominent notice with each copy of the object code that the
 Library is used in it and that the Library and its use are
 covered by this License.

b) Accompany the object code with a copy of the GNU GPL and this license

4. Combined Works.

You may convey a Combined Work under terms of your choice that,
taken together, effectively do not restrict modification of the
portions of the Library contained in the Combined Work and reverse
engineering for debugging such modifications, if you also do each of
the following:

a) Give prominent notice with each copy of the Combined Work that
 the Library is used in it and that the Library and its use are
 covered by this License.

b) Accompany the Combined Work with a copy of the GNU GPL and this license

c) For a Combined Work that displays copyright notices during
 execution, include the copyright notice for the Library among
 these notices, as well as a reference directing the user to the
 copies of the GNU GPL and this license document.

d) Do one of the following:

0) Convey the Minimal Corresponding Source under the terms of this
 License, and the Corresponding Application Code in a form
 suitable for, and under terms that permit, the user to
 recombine or relink the Application with a modified version of
 the Linked Version to produce a modified Combined Work, in the
 manner specified by section 6 of the GNU GPL for conveying
 Corresponding Source.

1) Use a suitable shared library mechanism for linking with the
 Library. A suitable mechanism is one that (a) uses at run time
 a copy of the Library already present on the user's computer
 system, and (b) will operate properly with a modified version
 of the Library that is interface-compatible with the Linked

e) Provide Installation Information, but only if you would otherwise
 be required to provide such information under section 6 of the
 GNU GPL, and only to the extent that such information is
 necessary to install and execute a modified version of the
 Combined Work produced by recombining or relinking the
 Application with a modified version of the Linked Version. (If
 you use option 4d0, the Installation Information must accompany
 the Minimal Corresponding Source and Corresponding Application
 Code. If you use option 4d1, you must provide the Installation
 Information in the manner specified by section 6 of the GNU GPL
 for conveying Corresponding Source.)

5. Combined Libraries.

You may place library facilities that are a work based on the
Library side by side in a single library together with other library
facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your
choice, if you do both of the following:

a) Accompany the combined library with a copy of the same work based
 on the Library, uncombined with any other library facilities,
 conveyed under the terms of this License.

b) Give prominent notice with the combined library that part of it
 is a work based on the Library, and explaining where to find the
 accompanying uncombined form of the same work.

6. Revised Versions of the GNU Lesser General Public License.

The Free Software Foundation may publish revised and/or new versions
of the GNU Lesser General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the
Library as you received it specifies that a certain numbered version
of the GNU Lesser General Public License "or any later version"
applies to it, you have the option of following the terms and
conditions either of that published version or of any later version
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.

If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the


License agreement

© Xequte Software

All users of the ImageEn/IEvolution/ImageEn OCX/ImageEnASP/ImageEnCMD components should agree with the following Licence agreement statements:


This License Agreement constitutes a valid and binding agreement between you and author for the use of the software named ImageEn/IEvolution/ImageEn OCX/ImageEnASP/ImageEnCMD.
You are required to read this Agreement and agree to all of its terms and conditions in order to download and use the software.

You are granted a License to use this Software product without royalties.
Modify, Translate or Create derivative components/libraries from the Software are prohibited!
Author grants you the right to include the compiled component in your application, whether COMMERCIAL, SHAREWARE or FREEWARE.
The Software may not be included in any commercial, shareware or freeware "libraries" or "components".


This software is provided "as is" without express or implied warranties, including warranties of merchantability and fitness for a particular purpose or non infringement. Author shall not be liable under any theory or any damages suffered by you or any user of the software. In no event will the author be liable for any loss of information, damage to computer or monitor, any incidental, special, indirect or similar damages, or consequential damages (including damages for loss of business profits, business interruption, loss of business information and the like) arising out of the use of or inability to use the software or its documentation even if the author has been advised and warned of the possibility of such damages.

In no event does Author warrant that the Software is error free or that Customer will be able to operate the Software without problems or interruptions. This warranty does not apply if the sofware has been altered, except by Author, has not been installed, operated, repaired, or maintained in accordance with instructions supplied by Author, has been subjected to abnormal physical or electrical stress, misuse, negligence, or accident, or is used in ultra-hazardous activities.


ImageEn/IEvolution/ImageEn OCX/ImageEnASP/ImageEnCMD is protected by copyright laws and international treaty provisions.
You acknowledge that no title to the intellectual property of ImageEn/IEvolution/ImageEn OCX/ImageEnASP/ImageEnCMD is transferred to you. 
You further acknowledge that title and full ownership rights to ImageEn/IEvolution/ImageEn OCX/ImageEnASP/ImageEnCMD will remain the exclusive property of Author and you will not acquire any rights to ImageEn/IEvolution/ImageEn OCX/ImageEnASP/ImageEnCMD except as expressly set forth in this license.
No Rental. Customer may not rent or lease the SOFTWARE to someone else.
All title and copyrights in and to the SOFTWARE (including but not limited to all images, photographs, animations, video,audio, music, text, and other information incorporated into the SOFTWARE), the accompanying printed materials, and any copies of the SOFTWARE, are owned by Author.

BASS 2.4

Copyright (c) 1999-2016 Un4seen Developments Ltd. All rights reserved.

 Delphi Chromium Embedded

 * Usage allowed under the restrictions of the Lesser GNU General Public License
 * or alternatively the restrictions of the Mozilla Public License 1.1
 * Software distributed under the License is distributed on an "AS IS" basis,
 * WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for
 * the specific language governing rights and limitations under the License.
 * Unit owner : Henri Gourvest <>
 * Web site :
 * Repository :
 * Group :


//**! ---------------------------------------------------------- 
//**! This unit is a part of GSPackage project (Gregory Sitnin's 
//**! Delphi Components Package). 
//**! ---------------------------------------------------------- 
//**! You may use or redistribute this unit for your purposes 
//**! while unit's code and this copyright notice is unchanged 
//**! and exists. 
//**! ---------------------------------------------------------- 
//**! (c) Gregory Sitnin, 2001-2002. All rights reserved. 
//**! ---------------------------------------------------------- 


Often, users are wondering - how to make beautiful
  ProgressBar for example to display the degree of occupancy
  Some vessel or something similar to the graphic
  Equalizer on the radio and music centers. Search spets.
  Component is often long. I want to propose my own solution -
  TProgressBar with support for images (in fact - skins).
  The demonstration shows how I myself propose to use it.
  The poor quality of the pictures used is conditioned by the desire
  Make a small size of the executable, the component successfully
  Works with pictures with a color depth of 32 bits. Component
  Completely free for any use.

  Author: Python (Smirnov Petr)
  System requirements: Windows 98 / 98SE / ME / 2000 / XP, 486DX2
    The size of the executable, the requirements for HDD and RAM are determined
    The sizes of the used pictures.
  The component is provided specifically for the Kingdom of Delphi


Copyright ©2017. Klever on Delphi


AC Team (c) 2002-2017



Liability disclaimer:



You may not attempt to reverse compile, modify, translate or disassemble the software in whole or in part. You may not remove or modify any
Copyright notice or the method by which it may be invoked.

Operating license:

Once you have registered, you will receive a link to personal registered copy via email. This copy may not be copied or lend. You have the non-exclusive right to use registered version of the software only by a single person, on a single computer at a time. YOU MAY use the components and classes from
this units in any your (or your company's) FREEWARE/SHAREWARE or COMMERCIAL application. YOU MAY derive your own components based on components
from this unit as you like if someone else will decide to use it they will have to register ALPHACONTROLS too. YOU MAY NOT DISTRIBUTE REGISTERED VERSION OF ALPHACONTROLS. IT WILL BE VIOLATION OF INTERNATIONAL COPYRIGHT LAWS.

You may physically transfer the software from one computer to another, provided that the software is used only by a single person, on a single computer
at a time. In group projects where multiple persons will use the software, you must purchase an individual license for each member of the group or 
special Site License for unlimited using. Use over a "local area network" (within the same locale) is permitted provided that the software is
used only by a single person, on a single computer at a time. Use over a "wide area network" (outside the same locale) is strictly prohibited under any
and all circumstances.

Back-up and transfer:

You may make one copy of the software solely for "back-up" purposes, as prescribed by international copyright laws. You must reproduce and include the
copyright notice on the back-up copy.


This license is effective until terminated. You may terminate it by destroying the program, the documentation and copies thereof. This license will
also terminate if you fail to comply with any terms or conditions of this agreement. You agree upon such termination to destroy all copies of the program and of the documentation, or return them to author

Other rights and restrictions:

All other rights and restrictions not specifically granted in this license are reserved by us.

If you have any questions regarding this agreement, please write to