Bug 81879 - Presentation > Interaction > Play sound should accept relative paths
Summary: Presentation > Interaction > Play sound should accept relative paths
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevEval
Depends on:
Blocks: Media ImpressDraw-Enhancements
  Show dependency treegraph
 
Reported: 2014-07-29 16:34 UTC by Christopher Brown
Modified: 2022-04-20 10:51 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brown 2014-07-29 16:34:41 UTC
The 'Play Sound' option in the 'Interaction' dialog should accept relative paths to the soundfiles. As it is now, it appears to accept only absolute paths, which makes this feature essentially broken/unusable if the presentation will occur on a different machine than the one used to create the presentation, since the file system will likely be different. Embedding the sound files would be a better improvement, but this would seem to be much more work. I am on linux, haven't tested on other platforms.
Comment 1 A (Andy) 2014-07-31 19:00:02 UTC
I would agree and mark it as an enhancement request.
Comment 2 Christopher Brown 2014-08-01 17:39:10 UTC
I view it more as a bug since to me, the feature cannot reasonably be expected to work (a user cannot/should not be expected to create and give the presentation on the same machine), and there is no way to make it work.
Comment 3 QA Administrators 2015-09-04 02:49:12 UTC Comment hidden (obsolete)
Comment 4 Robinson Tryon (qubit) 2015-12-10 07:26:34 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-01-03 19:40:58 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2019-12-03 14:17:54 UTC Comment hidden (obsolete)
Comment 7 brenbarn 2022-03-24 02:27:27 UTC
Yes the bug is still present.

Version: 7.2.5.2 (x64) / LibreOffice Community
Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Here's a hint for you guys: when a bug report is left untouched for more than a year, you know what that usually means?  It means you ignored it and didn't fix it.  It doesn't usually mean it magically fixed itself.  It is ridiculous to keep asking users to repeatedly re-confirm that bug exists.  Once the bug is known to exist it should be assumed to still exist until you affirmatively demonstrate that it has been fixed.
Comment 8 Buovjaga 2022-03-24 07:40:58 UTC
(In reply to brenbarn from comment #7)
> Here's a hint for you guys: when a bug report is left untouched for more
> than a year, you know what that usually means?  It means you ignored it and
> didn't fix it.  It doesn't usually mean it magically fixed itself.  It is
> ridiculous to keep asking users to repeatedly re-confirm that bug exists. 
> Once the bug is known to exist it should be assumed to still exist until you
> affirmatively demonstrate that it has been fixed.

Here's an interesting statistic for you: with thorough testing of groups of bugs untouched for a year, it has been consistently demonstrated that around 25% of such bugs could be closed as "silently" fixed. However, this one is really more an enhancement, so let's mark it accordingly and then it will not get the automated requests for testing.