Known Issues

Graphics / Known Issues

Cylekx is 100% java. However, it used to include chunks of C++ code in the early days before we fully realized the potential of Java. For those who do not have knowledge in this area we would like to explain a little about what this means...

Java is a state of the art programming language, don't be fooled by Microsoft trying to trick you into thinking otherwise. Java programs are naturally robust at all levels. At the highest level it is a small language, easy and simple to write ~ this automatically removes around 95% of the usual errors. At the lowest level it has inbuilt security checks everywhere - divide by zero and pointer errors that normally crunch programs beyond recovery are impossible in java. Java is an interpreted language and therefore runs the code with yet another level of checks - this makes one of the worst types of error (namely illegal memory access that result in delayed or invisible crashes in other programs) very unlikely to occur.

The end result of using java adds up to make a highly reliable Cylekx! It is not perfect however, and if you find something that doesn't work please mail us with a note about it. You are the users, and we are improving the program based on your input as much as our own. Any remaining errors are likely to be mere annoyances rather than functional problems. Issues we are aware of are listed below:

1: Some tasks can fail if not enough memory is available. This is a common problem with imaging software. There is sometimes no warning that the process may be unable to complete normally. Some cases where memory may be insufficient are: 1) creating a new image of excess dimensions, 2) attempting to open very large project files. 3) attempting to resize a selection with a mask (e.g. an ellipse) to huge dimensions. 4) virtual memory settings too low or high.
Memory failure can occur at any point in a program, and a message may not always be displayed immediately. When a memory error is displayed, it is important to restart.

2: Complex selections render too slowly and can cause thread locking if generated by the wand or color range tools on large images and some types of quantized images. Do not use animated selections: Window menus->Looks->Animated.

3: Print and slideshow calibrated output may be incorrect. The calibration output proportions are OK but actual output size may not match physical units like centimeters. Output on certain printers with their own resolution settings may also not be correct.

4: In rare cases the escape key can register twice if it is held down, and modifier keys can register as still being down even after they are released. As a fix, pressing and releasing the modifier key again should restore it.

5: Information on the channel processing capabilities for a particular process is not shown. (Some processes support specific channel processing and others do not).

6: Text has some unfavorable quirks. (e.g. long words that are partly underlined get split up when wrapping). Our upcomming text graphic type will probably make this text component obsolete.

7: Inserting large images into a text object causes a memory leak.

8: Microsoft XPS Document Writer has a bug that causes Cylekx to go into unregistered mode temporarily while printing. The Microsoft XPS Document Writer somehow manages to confuse the Cylekx program directory with the user desktop.

9: Dialog graphics can sometimes get damaged. This is a UI graphics glitch and in no way affects other program functions.

10: Multiple Text Components do not display well when they intersect. This is a UI graphics glitch and in no way affects other program functions.

11: Slideshow does not loop in some cases.

12: The scroll position of a text object is not always preserved, this can effect playback of the “Make Layer” command.

13: Vector graphics do not print or slideshow inverted when the calibration is negative.

14: Virtualizing is a new feature and still has untested code, there are very complex issues involved here and maybe some modules don't work.

15: It is 100% java, but for ease of deployment we are only compiling it to native windows for the releases. We are concidering doing a java class file release to support other systems like Mac, Solaris, and Linux.