Dear all,

I've created a button from a bitmap. In the 'up' state it's just the bitmap.
In the 'over' state it's another bitmap in the same size, with some text on it
(written in flash on top of the bitmap). Down and Hit state are the same as
'over', only a different color text.

Now what happens when I do a publish preview, is that the button doesn't work
properly. It does show the 'over' state, but when my mouse is anywhere near the
text it starts to very fast flicker between the up and the over state..

I tried breaking the text apart and I tried a different browser (normally use
firefox), but the problem stays!

Who knows what I'm doing wrong?

thanks a million..:)

The problem is u may have varying size for the objects in the states(up,over,down, hit) of the btn.
try keeping them of the same size...it'll work.

Try putting a hit area on your button - that's the 4th frame of your button
symbol. Make it as large as the largest visible button part.

--
-------------------------------
Remove '_spamkiller_' to mail
-------------------------------

So you got your flash working then ?????
Make the button a movie clip and use the swap or _visible methods. You can
adjust many things on a button for the diff states but you are tring to bring
in another bitmap to an already established button object.

Dudiedood, what you say sounds reasonable. But what I've done now is I've written the text in photoshop on the different bitmaps, and now it does work..

Thanks all for you help!

[quoted text, click to view]

What!? Sorry, but that's just weird. If you don't know the answer, best to
stay schtum i think, rather than posting misleading, confusing answers.
--
-------------------------------
Remove '_spamkiller_' to mail
-------------------------------

[quoted text, click to view]

In what way have I failed to grasp the concept of forums? Your post was a)
incorrect, b) almost incomprehensible, c) incorrect again. I simply pointed
that out. Pretty much how forums work no?


[quoted text, click to view]
offering other ways around a problem.

Ok. lets look at your answer in the cold, hard light of day shall we?

[quoted text, click to view]

Use them how, and to do what? Not very helpful I would guess. There is no
'swap' method. And _visible is a property, not a method. Other than that,
bang on.

[quoted text, click to view]

So? There is no problem at all with adding a new bitmap to an existing
button. Again, a meaningless statement.

I stand by my previous post ;)



--
-------------------------------
Remove '_spamkiller_' to mail
-------------------------------

cool off boys......

Indeed I've found there's no problem with adding a new bitmap to a buttonstate.
I've solved the problem by writing the text in the actual bitmap in photoshop.

But about the hit area - isn't that automaticly the whole button??

Thanks

no . when u have a text for a button it takes only the area of the text , so u
have no hit area between the text, which was creating ur problem. All u had to
do was create a keyframe for the hitarea and make a square over the text. Note
the hitarea is only for button hit and is not visible in any way.

So even if the button is a bitmap with some text written on top, it still won't take the bitmap as a hit-area? hm.. weird.

thanks for the tip!

Missing the point somewhere. what has this topic got to do with "saving a SharedObject"

Just a facile reference to an unrelated post wherein this guy has said 'no,
you're wrong, nah nah nah nah nah'. Ignore it, i have.

--
-------------------------------
Remove '_spamkiller_' to mail
-------------------------------

IF you have a flash text field in a button state and no HIT area, then
the *active* area will be the actual text - which causes the flickering.
Since you added the text to the bitmap, and the HIT frame is simply a
continuation of the OVER state frame, then yes, the hit area is the
exact size of your bitmap. So no need to assign a different HIT state.


chris georgenes
www.mudbubble.com
www.keyframer.com
team macromedia

[quoted text, click to view]