FEATURES | SCREENSHOTS | FAQ | DOWNLOAD | REQUEST A FEATURE

8. Well, I am running this Control with C: XX, M: XX, Y: XX, K: XX and what I get in RGB is R: XX, G: XX, B: XX. In Something software, the same CMYK values produce different RGB value. Is it a bug or what?
9. Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003).

2. Why should I register / pay for a program?
Our programs are distributed as key-enabled trial software. That means you may install and test it free of charge for as long as you like, and then if you like it and want to continue to use it, you can register your copy by paying for it. You'll get a registration code back from us after paying. This will either allow you to continue to use the program after the trial period has expired, or unlock some additional features.

3. How can I find out about program updates or new versions?
Join our Mailing List! Use a form on site at Mailing List subscription page.

4. Can I use new versions of programs released after I register?
Yes, after registering, you're entitled to all updates released for software version you bought. Please visit our Update Policy page for complete details.

5. How do I download and install a program?
Generally, you just click on the download link, and your browser will download the file. After it is done, you'll double click on the downloaded file's icon on your hard drive (located wherever your browser stores downloads). The download will start installation process containing the program, documentation, and other files.

6. I don't want to download, can I just get a CD-ROM instead?
Not now.

7. I've registered a program, but my registration code doesn't seem to work, help!
First off, make sure you have the most recent version of the program. Make sure you are entering your name into the program exactly as shown in your registration email. Make sure you double-check your code entry so that it matches the code sent. Often people think they've entered it in correctly and actually have made a slight typo, which will cause the code to not work. Extra spaces in the name or number, leaving out the dashes in the number, or entering in or leaving out punctuation to the name that wasn't there on the registration email will all result in the code not working. Everything must be entered exactly as shown in the registration email. The code contains no letter "O's", so all 0 are zeros. Also, make sure you are not mistaking eights for "B's", as that is one thing many people have trouble with. If you continue to have trouble, please contact us.

8. Well, I am running this Control with C: XX, M: XX, Y: XX, K: XX and what I get in RGB is R: XX, G: XX, B: XX. In Something software, the same CMYK values produce different RGB value. Is it a bug or what?
One absolute color can be converted to another absolute color, and back again, in general; however, each color space has its own gamut, and converting colors that lie outside that gamut will not produce correct results. There are also likely to be rounding errors, especially if the popular range of only 256 distinct values per component (8 bits) is used.
Note that the conversions in our Contol are best described as "nominal". It will produce an invertible conversion between RGB and a subset of CMYK; that is, one can take an RGB color and convert to certain CMYK colors, and from these CMYK colors obtain the corresponding, original RGB equivalents. However, conversion of CMYK colors in general to RGB colors is not invertible; that is, given a CMYK color which is converted to RGB, performing the former conversion may not give the original CMYK color. In addition, CMYK colors may print wildly differently from how the RGB colors display on a monitor. There is no single "good" conversion rule between RGB and CMYK, because neither RGB nor CMYK is an absolute color space.

9. Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003).
From: MSDN: The ABCs of MFC ActiveX Controls
Debugging Output You Can Safely Ignore
When you're debugging a control, you may get a series of messages in Visual C++'s debugging window. Although it's not documented anywhere, some of these messages can be safely ignored. For instance, when I debug the StopLite control in the test container using Visual C++ version 4.2, I get the following:
 
Loaded symbols for 'C:\WINDOWS\system32\MFC42.DLL'
LDR: WARNING ! MAJOR PERFORMANCE LOSS in SAMPLE.EXE
LDR: Dll MFC42D.DLL base 5f400000 relocated due to collision with C:\WINDOWS\System32\MFC42.DLL
Loaded symbols for 'C:\WINDOWS\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MSVCRTD.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MFCO42D.DLL'
Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003).
First-chance exception in SAMPLE.EXE (MFCO42D.DLL): 0xE06D7363: Microsoft C++ Exception.
 
The first line is just notification that the debugging symbols for the release version MFC DLL were loaded when the test container, which uses the release version of the MFC DLL, was loaded.
The second and third lines (which begin with "LDR:") warn that the debugging version of the MFC DLL (used by the Sample control) had to be relocated in my address space because it conflicted with the release version of the same DLL (which is being used by the test container). Although this means that it took a little longer to load the MFC DLL, it isn't a big deal because it only happens when you're debugging in the test container. You can ignore these messages. (Since Visual Basic apps don't use the MFC DLL at all, you won't get this message if you use a Visual Basic app as your test container.)
The next three lines are notifications that debugging symbols have been loaded.
The last two lines are notification that an exception has been thrown because the test container didn't provide a Color property to be read. This is okay, because we've provided a default value for the property. You won't get this error if you use a container that provides the property, such as a Visual Basic application.
In Visual C++, the only line I got was a warning about the exception for properties that couldn't be loaded from the container.
First-chance exception in SAMPLE.EXE (MFC40.DLL): 0xE06D7363: Microsoft C++ Exception.
Depending on how your container handles threads, you may also get occasional messages about threads exiting. You don't need to worry about these, either.