Version 1.2 Release Notes

From CwWiki

Jump to: navigation, search

1 Changelog (in 1.2.9.1)

[edit]

Changelog (in 1.2.9.1)

Hello all, Corelyzer version 1.2.9.1 is released!

You now can download it from: <a href="http://www.corewall.org/download">www.corewall.org/download</a>

Changes include:

- Logging DB interface update. FMS images with the same "Pass info" will be loaded into the same track

- Replace DXT texture generation algorithm from Squish to FastDXT (Intel processor only) to make 1st time texture generation faster.

- Optimize 2nd time image blocks loading: less than 1 second if texture blocks are already generated.

- First release of the function working Correlator to do visual affine table adjustment

- Retire ChronosJanus plugin with the ChronosJanus tab (with similar UI as the logging DB tab) in the IODP-related tables window

- Logging DB UI update. Get available sites info from the service when the leg info is input.

- Fix BMP image vertical flipping

- New splashscreen

- Fixes keyboard action activation in Windows

- Add visual correlation support with Correlator

- Put DIS Import into a separate thread

- Fixes and UI tweaks

- Fix JanusChronos plugin due to service changes

- New graph dialog (with original data min/max values)

- DIS interop format import/export

- New annotation input steps: select the annotation input mode and crop a annotation rectangle block

- Section splicing

- Commands_to_control_Corelyzer commands (Correlator slave mode)

- Add multi-screen display offset

- Add keyboard key '[' and ']' to change graph vertical scales

- Add load images from section lists (accept both LIMS and Chronos format)

- Add loading and applying affine table and splice table

- Accessing logging db from Bob Arko's web services (http://brg.ldeo.columbia.edu/services/) function is added. It will query, download, convert and load the numerical data files.

- For FMS images, it will download and convert it from GIF to JPG and loaded into Corelyzer. But since there's no metadata about the FMS images' length, depth or DPI, I used a naive way to "guess" depth and length from the file name. Because there is always white spaces around the FMS image form, so the "guess" value will not be precise.

- Description about using it is described in Corelyzer manual:

[edit]