Changes between Initial Version and Version 8 of Ticket #236


Ignore:
Timestamp:
Aug 9, 2016, 1:39:26 AM (8 years ago)
Author:
Lewis Rosenthal
Comment:

Related: #283

Removing the JPG plugin in favor of GBM would work around this issue for JPG files, but the underlying issue in the core remains that we have no way to specify a preferred plugin for a particular type of document when two or more plugins are loaded which can render the content, nor can we force a particular plugin for a particular file.

I would go one step further and say that if we provide a mechanism to record the plugin preference, we should store that data in Lucide's program directory somewhere or in a user profile directory (as multiple users on the same system may have different preferences - and that's yet another RFE).

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #236

    • Property Priority minor → Feedback Pending
    • Property Keywords plugin overlap added; advance file next jpg removed
    • Property Summary Cannot advance to next image (Shift-PgDn) when viewing JPG → Cannot advance to next image (Shift-PgDn) when viewing document when multiple plugins handle same type

  • Ticket #236 – Description

    initial v8  
    1 Shift-PgDn works as expected with all document types I've tested, except JPG, where the same image is simply reloaded. Shift-PgUp *does* work, however, even on these files. (1.3.4b2)
     1Shift-!PgDn works as expected with all document types I've tested, except JPG, where the same image is simply reloaded. Shift-!PgUp *does* work, however, even on these files. (1.3.4b2)
    22
    33I'm marking this as core, but it's liable to be in the JPG plugin; I don't know the code to make that determination.