Custom Query (324 matches)
Results (28 - 30 of 324)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#40 | fixed | Changes for the plugin API | ||
Description |
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. |
|||
#41 | fixed | closing Lucide with ALT-F4 is only possible right after starting Lucide | ||
Description |
When you double click the Lucide icon, or open a PDF document that is associated with Lucide, you can close Lucide with the keyboard by pressing ALT-F4. But this only works if you have not transfered focus inside Lucide to the document area. If the document area has the focus, you have to press CTRL-X to close Lucide (ALT-F4 will not work). If the menu or the navigation pane have the focus, you can also use ALT-F4 (and CTRL-X will also work). I do not vote for one or the other keyboard shortcut, I just would like to have it consistent. (well, actually, I would like ALT-F4 to work in Lucide from everywhere ;-) ) |
|||
#43 | fixed | Lucide selection of internal plug-ins | ||
Description |
I have noted that Lucide cannot select the correct internal plug-in (gives error message) when my browser hands it a file without the expected extension. For example, one of my employer's web sites hands off a pdf file with the name showdocument.cgi. I have my browser set to use Lucide as a helper application when either pdf or cgi is the extension. This is the same setup which I used with Acrobat 3.0. Apparently Lucide relies solely upon the extension for plug-in selection. However,if Lucide were to look inside the file when the extension is missing, incorrect, or not understood, it would find that PDF files all begin with something like "%PDF-1.4" and all DjVU files begin with something like "AT&TFORM". These phrases inside the file could then be used to select the proper plug-in. Thank you, Stu Updike Bedford, Texas USA |