Alternatively base the hash on:

    <file name without the hash>+<file size in bytes>+<last modification

And then make sure the last modification date is not changed when it is
copied into the servicemanager folder.

If currently only the full file name is used in the hash what happens
when a new version of the file is copied over the original? Do the
thumbnails get regenerated? Adding the size and mod-time to the hash
would address this too, but if there already is some mechanism to spot
and cope with this it could cause a conflict.

You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.

  Powerpoint is slow to load

Status in OpenLP:

Bug description:
  Originally reported in forum:

  The problem is that when we load a PPT we generate thumbnails for the preview 
and the slidecontroller, and extract notes and titles for showing on the stage 
view. This data is stored in a folder which name is a md5-hash of the full path 
of the ppt-file.
  When a presentation is placed in the servicemanager, the file is copied to 
the servicemanager folder, and when going live OpenLP creates a hash of the new 
full path of the file (now in the servicemanager folder) which of course is 
different from the old hash, and therefore OpenLP generates the thumbnails etc 

  A few solutions could be made:
   * Make the hash based on the file content instead of the file path (might be 
a bit slow on big files).
   * When adding a ppt-file to the servicemanager, copy the old folder to the 
new hash-folder.
   * Add the thumbnails etc to the service file.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to