Just FYI, I'm not sure how long this has been going on--probably since
moving to the LayerGroups system--but I found an issue just now where
if a new layer was added and there were another new layer previously
added, the new layer would not function correctly. It had to do with
object identity and the indexOf function in the ArrayList class, which
is to say, it's sort of a surprise bug. What could happen then is if
you say, started a new project and added two layers, trying to add a
new object to the 2nd layer wouldn't show anything but the operation
would occur. Switching to another project then coming back to the
original would then show the object.
Suffice to say, it was an odd one I didn't know how to reproduce and
fix until now. I have fixed in the 2.6 branch. If I do a 2.5.11
release, I will be backporting the fix.
I'm not sure it is related. However, one of the things that has taken
me so long for 2.6 is that I've had to totally rewrite all of the
actions and internal coding for object selection to handle the
heterogenous layers (i.e. copying/moving/pasting of both SoundObjects
and AudioClips). I imagine #83 will go away once this is complete.
I'm working with the Milestone system now on Github and have added the
SF bug 83 to Milestone 2.6.0: