** Changed in: openlp/trunk
    Milestone: None => 2.9.1

** Changed in: openlp/trunk
       Status: In Progress => Fix Committed

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

  Change double-click-osz-file behaviour

Status in OpenLP:
  Fix Committed
Status in OpenLP 2.0 series:
  Won't Fix
Status in OpenLP trunk series:
  Fix Committed

Bug description:
  With no OpenLP running, double-clicking a file starts the app and
  loads the service in the osz file.

  When double-clicking another file, OpenLP appears to start a 2nd
  instance and Errors saying "OpenLP is already running. Do you wish to
  continue?". When clicking No, the 2nd instance aborts. When Yes, the
  2nd instance runs.

  Can one configure OpenLP to behave like other apps, which don't run
  2nd instances but instead pass a msg or signal to the 1st/original
  instance with the filename to be opened. Then it's down to the 1st
  instance to behave accordingly.

  For example, if OpenLP has a service file open, and one drops a 2nd
  service file on the app, onto the Service Manager list panel, OpenLP
  replaces the active service with the newly-dropped file.

  My suggestions:

  1) That, when a user drops a different service file on the Service
  Manager list panel, instead of silently [current behaviour] replacing
  the current service with the dropped service, that OpenLP should
  prompt "Are you sure you want to replace 'old service filename' (4
  items) with 'new service filename' (7 items)" ? Of course, if no
  service file is currently loaded, then just load the dropped file. If
  a service is already opened, and modified but not saved, or items
  added but never saved, then an additional option to "save changes"
  should be made (which the user could choose to ignore/not save etc).

  2) When OpenLP is already running, and a user double-clicks a service
  file in their file manager of choice, that the 2nd instance of OpenLP
  that is started sends a signal to the 1st instance, passing the name
  of the file osz involved in the double-click operation, and that the
  msg signal/event triggers: 2.1) a focus/bring-to-front of the 1st
  instance, 2.2) the behaviour suggested in #1 and finally 2.3) silent
  closure of the 2nd instance.



To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~openlp-core
Post to     : openlp-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openlp-core
More help   : https://help.launchpad.net/ListHelp

Reply via email to