Converting text into a button doesn't work properly.

[No Thankyou]

I am converting text into a button and then inserting the following
action:

on (press) {
gotoAndStop(14);
}

When you press on the button it will bring you to frame14. The area
around the button is not totally clickable. It is like Macromedia only
converting an outline of the text into a button because when I pass my
mouse pointer over the button certain areas you cannot click on even
though you are still over the button.

Making the text in a third-party program and importing it as a graphic
into my library will get rid of this problem (the whole area of the
button is clickable), but doing this has some often disadvantages -
time, size and it's freakin annoying.

I also created a transparent box and put text in the box. I then
converted both the text and the box into a button. I still have the
same problem with some areas over the button not being clickable.

Any help greatly appreciated. Thank you.

Colin

[Duh NuhnKa]

When you only have text in a button, the text itself will serve as the
'clickable' area (hotspot, hitframe). To solve this you have to edit the
button and put a solid shape (a rectangle or a circle or whatever you
want as a 'clickable' area) in the 4th frame (labelled "Hit"). Anything
you put in there will not be visible in the final swf but only server as
the 'clickable' area.

No Thankyou wrote:

> I am converting text into a button and then inserting the following
> action:
>
> on (press) {
> gotoAndStop(14);
> }
>
> When you press on the button it will bring you to frame14. The area
> around the button is not totally clickable. It is like Macromedia only
> converting an outline of the text into a button because when I pass my
> mouse pointer over the button certain areas you cannot click on even
> though you are still over the button.
>
> Making the text in a third-party program and importing it as a graphic
> into my library will get rid of this problem (the whole area of the
> button is clickable), but doing this has some often disadvantages -
> time, size and it's freakin annoying.
>
> I also created a transparent box and put text in the box. I then
> converted both the text and the box into a button. I still have the
> same problem with some areas over the button not being clickable.
>
> Any help greatly appreciated. Thank you.
>
> Colin

[No Thankyou]

On Mon, 21 Mar 2005 09:22:15 +0100, Duh NuhnKa <rlitjens@indespot.nl>
wrote:

Thank you. Much appreciated. That did the job.

>When you only have text in a button, the text itself will serve as the
>'clickable' area (hotspot, hitframe). To solve this you have to edit the
>button and put a solid shape (a rectangle or a circle or whatever you
>want as a 'clickable' area) in the 4th frame (labelled "Hit"). Anything
>you put in there will not be visible in the final swf but only server as
>the 'clickable' area.
>
>No Thankyou wrote:

>> I am converting text into a button and then inserting the following
>> action:
>>
>> on (press) {
>> gotoAndStop(14);
>> }
>>
>> When you press on the button it will bring you to frame14. The area
>> around the button is not totally clickable. It is like Macromedia only
>> converting an outline of the text into a button because when I pass my
>> mouse pointer over the button certain areas you cannot click on even
>> though you are still over the button.
>>
>> Making the text in a third-party program and importing it as a graphic
>> into my library will get rid of this problem (the whole area of the
>> button is clickable), but doing this has some often disadvantages -
>> time, size and it's freakin annoying.
>>
>> I also created a transparent box and put text in the box. I then
>> converted both the text and the box into a button. I still have the
>> same problem with some areas over the button not being clickable.
>>
>> Any help greatly appreciated. Thank you.
>>
>> Colin