I expect that's just not feasible. I'm also not sure how it'd behaved if the attached atom is really an atom - when you click on it, whose Click proc is called?Undecided, perhaps both with a special parameter.
Images aren't awkward.The very creation of an /image is awkward, you have to attach it to another atom.
The only problem with images is that their capabilities are limited but being able to flick() them and having them animate to match the object they're attached to would fix this.Far from the only problem(s), and it doesn't address the issue that if there were better visibility settings, we could use standard objects, and special /images would be completely unnecessary to begin with.
I expect that's just not feasible. I'm also not sure how it'd behaved if the attached atom is really an atom - when you click on it, whose Click proc is called?
Images aren't awkward. You're code example shows nearly identical code for both the image and attached mob. The only problem with images is that their capabilities are limited but being able to flick() them and having them animate to match the object they're attached to would fix this.