{12} All tickets by change date (including closed) (252 matches)

The main menu has underscores to show the accelerator keys, but the drop down sub-menus do not. This is non-standard.

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!

Hello Lucide team, at the Acrobat Reader, I have possibility to write direct to the pdf document and then print it out. Another feature is, to save a copy of the current pdf document.

best regards, Jan Thiel

Following actions should be appended to the "Document" menu:

• Close
• Close All
• Print Preview

I have noted on DjVU Zone that when a file is a pure DjVu? file, the Lucide displays it properly. However, there are numerous links which point to index.html files. They hand off immediately to files named index.djvu. Lucide runs and shows the pages in the bookmarks panel, but nothing ever shows in the document panel. When this happens Lucide either becomes unresponsive and I must CTRL+ESC to close it in the Window List or Lucide disappears all by itself.

Thank you,

Stu Updike Bedford, Texas USA

When rendering a document page certain errors could arise in the plugin (e.g. out-of-memory, file no longer accessible, ...).

It is so far not possible for a plugin to report these errors to the Lucide core. Thus the user has no idea what went wrong. He/she probably just sees an empty page (or crap).

Proposal: Apply the same error reporting scheme used for loadFile() to renderToPixbuf() and renderToPS(). (boolean returned, error message via SOMMalloc)

Heiko Nitzsche proposed some changes for the plugin API, he implemented the GBM plugin:

​http://article.gmane.org/gmane.org.netlabs.lucide.general/6

Please have a look at that and post to the list if you have questions.

How To Reproduce:

Open a PDF file, make the navigation pane on the left hand side visible, double click somewhere in the navigation pane where there is no text

Expected Behavior:

Lucide should ignore the double click

Actual Behavior:

Lucide crashes

More Information:

This is from popuplog.os2

06-27-2006 18:27:27 SYS3175 PID 00d2 TID 0001 Slot 00bd E:\OS2PROG\MULTIMEDIA\LUCIDE\LUCIDE.EXE c0000005 00022888 P1=00000001 P2=0000001c P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=006a0002 ECX=000100d2 EDX=001a0ee0 ESI=00d20001 EDI=00000002 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:00022888 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:00064f54 SSACC=f0f3 SSLIM=ffffffff EBP=00065000 FLG=00012246

LUCIDE.EXE 0001:00012888

At present, there is no differentiation between the white document page and the white document window background. If the document window background could be changed to gray, the boundaries of the document would be clearly visible.

When Lucide is started from the root directory of a drive, its window shortly opens, closes again and the program terminates.

Workaround: Start Lucide from a subdirectory.

In the popuplog.os2 an entry about SYS3180 appears, e.g.

06-16-2006 14:28:44 SYS3180 PID 00ec TID 0001 Slot 0097 R:\LUCIDE.EXE c0000097 0001fa1d EAX=0000012f EBX=012f01f7 ECX=000100ec EDX=13e8af20 ESI=800000ee EDI=00000007 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:0001fa1d CSACC=f0df CSLIM=ffffffff SS:ESP=0053:000644d0 SSACC=f0f3 SSLIM=ffffffff EBP=00230208 FLG=00002202

LUCIDE.EXE 0001:0000fa1d

Each time you try to load a PDF-file in a new LUCIDE window it takes an awful lot of time to load the document. But if you keep on loading PDf's in the same LUCIDE instance which was once already opened by a PDF, the PDF documents are opening extremely fast.

Probably this is caused by each time reading/creating the fonts.cache-1 file in C:\PSFONTS each time a PDF is opened in a new LUCIDE window.

Furthermore the fonts.cache-1 file is also created by Alex Taylor's GIMP installation routine. I have noticed that starting HOBLink X11 and The GIMP some fonts from C:\PSFONTS were not available anymore when LUCIDE was run before. I got them back by running the font-script delivered by ALEX TAYLORS GIMP package. Conclusion: fonts.cache-1 created by Lucide is not the same as the one created by The GIMP installation routine. Most probably LUCIDE will cause the same trouble with XFree86/2 .

Solution? LUCIDE must check if there is a FONTS.CACHE-1 file already present. Furthermore FONTS.CACHE-1 files should be independent from the program they were created by, or Lucide should create it's own cachefile (with an unique name)

This is more or less aduplicate of ​http://svn.netlabs.org/lucide/ticket/30

It seems that the fontscache is initialized each time Lucide is invoked. This also overwrites the fontscache that may have been generated by other programs like The Gimp installer.

This is bad for two reasons:

1) performance (!) 2) Lucide drops fonts that The Gimp did add (for example from other fontdirectories)

This has been reproduced on two systems.

Comment from a beta-tester:

Often when I get a pdf, depending on the subject, I prefer to print it. Back problems make online study a painful experience. What really bugs me is the lack of an option to print it on both sides of the paper. With a regular text document, I can do this with Wordperfect... Even works on dot matrix printer, which I prefer. To me, that feature would be a real Adobe buster.

regards, Malcolm

Lucide does not show the dots in the graph in my pdf file(which I will gladly send to you). It displays correctly in Acrobat and in ghostview.

The document window is not redrawn correctly when opening a new file. Probably not all parts are invalidated.

Open the files in "read" mode, so they can also be accessed by other programs and it is allowed to write the file while it is already opened by Lucide. If the file has changed it has to be re-read! This is needed to use it as PDF-Viewer when someone creates PDF files with VTEX/2 (LaTeX).

You have to compare the last saved timestamp with the current timestamp when the Lucide window will be activated. If you have a background thread that will check the timestamps in the background this would be an option too. Look at the GSView source, which is supporting this feature since ages.

06-08-2006 11:32:11 SYS3180 PID 004d TID 0001 Slot 00a9 R:\LUCIDE.EXE c0000097 0001f404 EAX=0000012d EBX=012d01f5 ECX=0001004d EDX=1cb4af20 ESI=80000285 EDI=00000007 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= CS:EIP=005b:0001f404 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:00062f04 SSACC=f0f3 SSLIM=ffffffff EBP=00220d08 FLG=00002206

LUCIDE.EXE 0001:0000f404

First of all my congratulations to the very good idea of a generic document viewer. It looks really promising. For developers the plugin API needs to be documented but I guess this is planned already.

I just had a quick look at the plugin sources of the PDF reader because it takes quite long to open a PDF file with many pages.

The Plug-in API seems to support only loading a file as a whole with all pages. This might not be possible for large documents (e.g. big multipage images or complex PDFs) due to system memory constraints. Also it forces the user to wait unecessarily long time and finally the user might not even want to have a look at all pages of the document.

As a workaround plugins could defer loading pages to view during rendering but this is obviously not intended as there is no way to report read errors.

I'd suggest to either enhance the loadFile function or introduce some kind of page switching function with a return code that allows plugins to load a document page on demand. This might be also helpful for supporting document streaming from an URL if this is planned sometime. If memory gets low, the plugin could drop pages from memory if not needed to reduce memory footprint.

Heiko

It would be convenient to have a 'recently opened' files history, like Acrobat Reader has. Amazingly enough, I use that quite a lot ;)

I asked Ulrich Möller about the license, Poppler is GPL but I would like to release Lucide itself as LGPL/CDDL dual-license if possible.

There should be context-sensitive help available for Lucide. Probably we should talk to Christian Langanke about how to implement that properly.

Again, support from the community is very welcome!

There are PDF documents with comments in it, those don't work with Acrobat on OS/2 so far. Lucide does obviously support it somehow, at least I can see some nice flags in the document but the comment itself are not shown.

See the attached PDF

Implement printing support for documents

There should be an option to show the document in fullscreen-mode, for example for PDF presentations

All icons should be replaced, we will give the job to Wizzard to create some icons.

If I open a document it will always show the document open dialog in the executable directory, make sure it remembers the last directory the user navigated too