Known bugs in PMView Pro v3.00 - Known bugs that will be fixed soon Options

[Peter]

The following are known errors in the current version, and will be fixed in the upcoming v3.01 release scheduled for 6/16/03:

Both versions:

-Zooming may crash PMView
-Trial version: The evaluation period (time) is migrated from PMView 2000 with the rest of the settings (this was not intended).
-There is no way of knowing if PMView is showing the default or actual resolution of a file in the File Info dialog. v3.01 will add the text "(Default)" after the resolution if the actual resolution is unknown.
-Minimizing the PMView main window causes the scroll bar positions to be reset to their leftmost/uppermost positions when the window is restored.
-The red and blue colors are swapped when displaying JFIF (JPEG) files with RGB color space. (Such files are not common).
-The "ExposureTime" field in the EXIF data is not always displayed as a fraction. How it is displayed depends on how the camera stored the data. v3.01 will always display it as a fraction regardless of how it is stored.

OS/2 only:

-Loading an image when the main window is minimized crashes PMView.
-The info tip help in the File Open window may paint incorrectly when a popup menu is shown.
-The info tip of the File Open window may appear when the cursor is outside the window.
-Performance (speed) problem with conversion and EA Icon thumbnail creation in directories with many files (>1000).
-EA Icon thumbnails cannot be created on drives that do not have write permission enabled.
-Installer does not install an icon on Warp 3
-Installation fails if there is a space in the path name. (The v3.01 installer will have a notice telling not to use spaces in the installation paths. The actual problem will be addressed in a future release when an upgrade to the WarpIn installer is available that lets us solve the problem).

Thanks,



Edited By Peter on 1055546550

[Peter]

If that parameter utilizes the existing instance and replaces the existing image currently being displayed with the new file named in the second launch, then it sounds like we've got it licked.  Presumably it would also "restore" the display window if it was currently minimized.

Yes, this is what it would do. The existing instance must also have been started with the /EXI flag. This lets you start other instances without the flag and they can run "safely" without risk of being overtaken by the application(s) that use the /EXI flag. For instance, if you have manually launced a separate copy from the shortcut on the desktop and is editing a file, it is very unlikely that you would want this instance "hijacked" by another app. Don't you agree?

This feature, and the possibility to add a shortcut key for minimize will be in v3.10.

Thanks,



Edited By Peter on 1055108876