Custom Query (324 matches)
Results (46 - 48 of 324)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #49 | fixed | File open dialogue does not include *.PDF | ||
| Description |
Sine one of the primary uses of Lucide is to read PDF files, wouldn't it be better to include *.PDF in the list of files displayed when one selects document open ? |
|||
| #50 | worksforme | Application exits after attempt to open .PDF or .JPG | ||
| Description |
The application start up okay. I can navigate through the menus. Howeve, after clicking Document-Open and then selecting [PDF or JPG file] followed by OK, the application exits. There are no error messages and no POPUPLOG.OS2 file. This is the same for all versions of LUCIDE; that is, v1.0, v1.1 and v2.0. Since I have a couple of compilers, it's possible that my SOM paths and files are missing or nonstandard. What SOM files and what SOM paths are required by LUCIDE? Currently, I have tried to separate the SOM stuff from Visualage C++ v3.09; from the Warp Toolkit v4.52; and from the eCS v1.1 base into their appropriate sections. That is the only thing I can think of that might be causing the problem. Is there a debug mode for LUCIDE? Sorry, but I'm kind of stuck! |
|||
| #51 | fixed | LUGBM.DLL access violations on BMP, JPEG graphics | ||
| Description |
Whereas Lucide v 2.0 Beta appears to work a lot better opening PDF files, unfortunately it appears to now have a problem opening graphics files. I have tried opening BMP files (handled I expect by the GBM Plugin) and Jpeg files (handled I hope by the JPG plugin) and in all cases the program aborts and reports an access violation in LUGBM.DLL. Upon testing, by moving GBM.DLL once again out of the working directory and trying to open the JPEG file again - it opens without problems, so I start to suspect that there may be a compatibility between the GBM plugin and version Beta2 of Lucide ? Ed. |
|||
