Hi - I'm adding a dynamic text field, place text in it and all is well.
When I add a second one, place different text in it all is not well.
Say I convert the second dyn text into a button, go to the states and make small (color only) adjustments. On mouse over it displays different text then on relese.
Can someone take a look and tell me if I'm doing something wrong or if it is .... dare I say it ... a bug?
I can't seem to repeat the error. Wierd I had to figure out how to convert a editbox to a button first. Never done that before.
Post source Please Also what version of KM are you using check your About page to verify As I recall there was a problem with Dynamic text in an earlier version.
The buttons are just simple squares with dyn text for a label. (otherwise the writing is not crisp enough).
When I convert the square and dynamic text to a button all is well but as soon as I go to the button states and change the color arrangement, all hell brakes loose.
See buttons one and two for an example.
Can this be fixed and if not, can swishmax do this? I really need to get this done today and don't have time to mess around any longer.
Getting a dead link Doc. Attach your FUN file using the "Manage Attachments" button below the submit button to browse for your local file. Bret had Flashkit add the FUN extension.
Looks like a bug to me. Apparently copy and pasting a dynamic text in a button state doesn't work right. Also it seems to be an issue of the text box names being the same.
Can this be fixed and if not, can swishmax do this? I really need to get this done today and don't have time to mess around any longer.
Wow not in a hurry are we? If you really must have it today don't use dynamic text. (the sharpness issues is a problem on all flash programs as far as I know)
Or don't use buttons. I almost never do. Make a button library item with a movie clip.
Bret,
I changed the dyn txt names but still no go. This is also bugging me because I need to have 2 or more dyn txt fields to explain the music theory for each step. There too I experience the mix up of text and we aren't even talking buttons.
Sooooooooo .... I'm swishin' it. See how that goes.
Bret,
I changed the dyn txt names but still no go.
Hi Dr John,
As usual, I'm responding too late to be of any practical use . Sorry, been busy. Maybe Bob will get something out of the following.
I did some experimenting with your fun file and found that in the event that the movie has dynamic text (DT) boxes with identical names in different buttons, the text boxes in the over or down state will display the value of the DT box in the up state (in your case, the duplicate named up state boxes were in Lessons 2 and 3). So even though a naming conflict error isn't generated, for the over and down state DT values displayed to be accurate, the DT box names need to be unique for the movie, not just the button.
You had the Export Setting "For backward compatibility, make the variable name of a dynamic text object its object name" checked - this is a good idea, because when I unchecked this and started copying DT boxes from button to button, the textvar name no longer was based on the box name (which I was manually changing) but remained the same as the source object, and this caused the new DT box to display the source object's value instead of what had been typed into the DT box (because both DT boxes now had the same textvar name, I guess).
I tried seeing if it was possible to populate the DT boxes dynamically w/ ActionScript from the root level, but couldn't get that to work . Anyway, attached file shows that DT in buttons can be done, but it is very tedious.
(Caveat on the above results - I'm working w/ 5.3 beta, but I don't think that should make a difference in this case.)
Anyway, Bret probably had the right idea about using movie clips - I don't think the DT box dupe names would have been an issue as, when they are embedded in movie clips they would have unique paths modifying their names. I hope this helps in your future projects.
The whole problem is caused by the variable names of the dynamic textfields.
If KM would allow to delete the variable name and export it as null when empty (not the string null) it would have worked fine. When you create a dynamic textfield using actionscript the variable is always null by default.
If you are creating a new appication it's always best to turn off the backward compatibility and use myTextField.text to assign text. Text variables can cause a lot of problems.
Reply With Quote
Originally Posted by Dr_John
. Sorry, been busy. Maybe Bob will get something out of the following. 
