i tried i as described but the same problem occured.
but i finally found a way. it's incredebly confusing but it somehow works.
when the mouse hovers over the 1st button it loads a new swf, which is the field, that is supposed to pop up. in that is the button and a button which is very slim and surrounds the field. when you click on the button it opens the link and if you you move your mouse out of the field and therefore out of the framing button it unlaods itself.
wow... thats some ****. but when i didn't have the framing button it would either not unload itsef or the button wouldn'T trigger
i have to use it now the way it is, because i'm running out of time and it's 4:05 a.m. here already.
but maybe someone has a better solution for upcomming generations...
problem is you can't say: someButton.onRelease... if someButton is not present.
Your button being on the second frame of that movie makes it "not present"
Solution:
Have that button on frame 1 also and have it invisible with: someButton._visible = false;
or have that someButton.onRelease function in the same frame that the button sits.
gparis
i tried the second solution (had treid it before, btw) but no result. am i stupid?
the first solution won't work because i the actual file the uppopping field will be much bigger then the one from the first frame. at least i don't see how it could work without already triggering when the cursor gets over the big invisible field.
you're welcome. Maybe you've heard it is best practice to put your code on frame1 on the main timeline. It's true in the sense that readability, clarity etc.. are better. But, in my opinion, not ALL code always needs to be on frame1, not in ALL cases.
For any other application, there may be impossibilities (like in your case: button only on frame2 of a nested clip) and there is no way writing an extra 5 lines of code (sometimes involving the use of cpu intensive loops) just to make it work, is worth it.
just my opinion.