Custom Query (324 matches)
Results (13 - 15 of 324)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #359 | fixed | Makefile changes needed to sync with current build layout | ||
| Description |
Currently, the manual makewpi.cmd used to package Lucide 1.4.0 depends upon the directory structure in that attached warpin-tree.txt (lucide.wis may just as easily be lucide.wis.tpl, and the same with the language scripts). I'll leave it to someone else to make the changes to the Makefile. This was why the packaging changes for 1.4.0 were never committed to SVN. See also #352. |
|||
| #358 | fixed | Search matches not highlighted | ||
| Description |
Prior versions of Lucide would highlight search matches. This no longer occurs with the Lucide 1.4GA and 1.4.1 betas. On a related note, it was not possible to clear the search highlighting by entering an empty search string. |
|||
| #357 | fixed | Lucide crash when attempting to open a supported filetype by name which is not a supported type | ||
| Description |
The supported filename extension list for GBM includes .img. Unfortunately, .img is also used for disk image files (not graphic files). Lucide 1.4.0 will open these files, rendering a single page with a thin line in the document window. 1.4.1, however, abends with no .TRP file and no POPUPLOG entry. Example: 512-byte AOSBoot MBR image from ArcaOS USB stick boot. This is a raw .img file from DFSee. The same behavior is observed when copying the .img file to another supported file type extension for the GBM plugin (e.g., .jpg). Copying the original .img to .pdf or to .djv produces the expected "File load error!" popup. |
|||
