Issue 103706 - Sound/video files inserted into a slide need a way to determine properties
Summary: Sound/video files inserted into a slide need a way to determine properties
Status: CLOSED DUPLICATE of issue 99573
Alias: None
Product: Impress
Classification: Application
Component: editing (show other issues)
Version: OOO300m9
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2009-07-21 18:43 UTC by eclypse
Modified: 2017-05-20 10:06 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description eclypse 2009-07-21 18:43:11 UTC
I ran into an issue this morning where one of our staff had created a
presentation with a video file in the first slide of the presentation. The
person saved the presentation in another location where it would be accessible
by the people who needed it.

Another staff member was called upon to help get the presentation working this
morning because the video was missing. When they tried to find the object that
the big "?" question mark was looking for, there was no way to determine what
file was missing to try to locate and/or replace. I tried in OOO300m15 (000300m9
was the highest listed in the tracker) and I tried in an older version 2.4.0.14
for OpenSUSE 11.0.

In neither place could I find any menu or context menu option that would show
the path of the missing file.
Comment 1 wolframgarten 2009-07-22 07:27:42 UTC
Reassigned.
Comment 2 wolframgarten 2009-07-22 07:32:31 UTC
A workaround for this problem might be to unpack the file and have a look into
the content.xml file. Name and path of the inserted video are stored there.
Comment 3 hennerdrewes 2009-07-22 10:08:08 UTC
I already filed a similar issue 99573.

@eclypse: you might want to vote for issue 99573.
Comment 4 oooforum (fr) 2017-03-31 14:35:57 UTC
Already reported

*** This issue has been marked as a duplicate of issue 99573 ***