Issue 80713

Summary: XAnimation does not support XPropertySet interface
Product: App Dev Reporter: hub <hub>
Component: apiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: 3.3.0 or older (OOo)   
Target Milestone: ---   
Hardware: All   
OS: Linux, all   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description hub 2007-08-15 20:19:03 UTC
XAnimation does not support XPropertySet interface, making it inconvenient to
store a list of properties to assign to a XAnimationNode (or any derived interface).
Comment 1 jsc 2007-08-16 08:18:49 UTC
jsc -> thb: can you take a look on it. I don't know where Animation objects are
described, so i don't know the typical attributes/properties supported
interfaces etc. I miss some general Animation object description. I hope you can
enlighten me when you are back from vacation.
Comment 2 thomas.benisch 2007-08-16 08:44:03 UTC
reassigned to THB
Comment 3 thb 2007-08-26 21:51:33 UTC
@hub: just curious - why do you need this?
Comment 4 hub 2007-08-27 13:39:31 UTC
1/ be consistent with the rest of the API

2/ be able to transport / copy the attributes

I'm using it in the xml/oox module for PowerPoint 2007 PPTX import and not
having XAnimationNode support this interface makes it much more complicated.
If you look at
it shows a list of attributes.

This should also apply to any "subclass" of XAnimationNode.
Comment 5 clippka 2007-08-27 16:21:43 UTC
taking over.

I agree this can be a convinience, even though 'newer api' design should prefer
attributes because of theire type safty. Having both is a good choice.
Comment 6 thb 2007-12-19 16:06:03 UTC
@cl: now for real ;-)
Comment 7 clippka 2008-01-10 09:22:36 UTC
shifting target
Comment 8 clippka 2008-06-02 13:45:42 UTC
Comment 9 Marcus 2017-05-20 11:27:55 UTC
Reset assigne to the default "".