Grouping Animations

Hi, i've just been working exporting animations for multiple objects and i'm trying 2 use the grouping options for the animation so that i can export animations for different objects from the same point in the timeline.

So i have 2 objects in my scene box1, box2 and sphere2, 1 animated from 0-100 the other from 50-100.

1. box1 and box2 i give the name "boxes" in the 'objectanim name'
   
   sphere2 i give the name "sphere" in the 'objectanim name'[/list:u]
   
   Then in the export setup i make 2animations:
   
   
   1. 
      translation, 0-100, then selected a group (changed name) 'boxes'.
      
      rotation, 50-100, then selected a group (changed name) 'sphere'.[/list:u]
      
      Now what i was hoping would happen when i exported this was that the boxes would each have 1 animation under them (ie boxes translation) and the sphere would have 1 animation under it (ie sphere rotation) but instead i get 2 animations under each object:
      
      1. 
         boxes animations - "boxes translation" and "boxes rotation"
         sphere animations - "sphere translation" and "sphere rotation"[/list:u]
         
         is this supposed 2 happen? i was hoping i cud specify which animation went with which group otherwise i'll end up giving the programmer an OSM with 20 animations under each entity with only 1 of the animations being relevant?
         
         Am i setting the animations up wrong? is there a better way of achieving this result?
         
         If any 1 can shed some light i'd be very grateful.

so has no1 else tried to animate using the ofusion exporter or experienced similar issues?

The entries in the animation list are global animations, this means that any object that has any supported animation during the defined range will create an animation using the animation entry name

Currently anim groups are used to create a subset of the animation with a different name for selected entities, using the defined base group name

What you suggest seems to be a good idea, i will add this to the list (to be handled asap), expect it to be implemented for the next update