KNOWN BUGS and PROBLEMS

1) You can still get into 2D region trouble with non-default margins and window

sizes. Occasional ghost images get left behind on some video displays moving

2D regions.

2) Variable pitch fonts won't work properly with tabbed text in stats windows.

You need to use Courier New for all the stat text in order to get the tabs & characters

to align properly. Arial works fine for the graphical windows, but messes up the text

windows.

3) Metafile doesn't always paste as expected. This seems to be more a function of how

the application executing the PASTE deals with the WinMDI MetafilePICT.

4) Overlaid single parameter listmode file histograms don't get gated along with first

parameter if the gate is changed after the inital read. Work around: Set up gates

BEFORE reading in any overlaid histograms.

5) Density plot axes extents are currently limited to a multiple of array size in order to

avoid graphical artifacts, or the addition of code that would slow things up in order

to overcome the effects.

6) Some LYSYS genereated mixed mode files may not scale properly on the 256

channel parameter if LYSYS fudged the byte boundary for a subsequent 1024

channel parameter. Work around: Avoid collecting mixed mode files where a

1024 channel parameter follows a 256 channel parameter with an odd number.

7) Histogram gates may be combined with 2D gate with only AND logic. For example,

setting histogram regions and then adding an OR gate logic to 2D region R1 does

not yield histogram_regions OR R1, but rather any events passing the histogram

regions are then gated through R1. The histogram regions, when used as gates,

function as a fast selection prior to any 2D gate logic.

8) There have been problems reported with very large (>500,000 events) FCS files with

mixed modes (256 AND 1024 channels in the same file).

  1. The Printer device context handling was still buggy through version 2.4 after making any changes to the printer(s) from within WinMDI. After changing printers or printer setup, the default printer device context was still used by WinMDI. Workaround: set default printer configuration from the Control Panel before running WinMDI. This has been fixed in Version 2.5.

  2. FCS files generated by BDIS CellQUEST version 3.x could be partially read, or improperly read when CYTNUM was set in the header before all the parameter values were read by stdheader.c. This has been fixed in version 2.5.

Joe