More problems with text fields stored as Flash swf assets


#1

Any dynamic text fields get moved slightly up from their original position in the swf file.

Static text fields stored in a movie clip as keyframes other than frame 1 are significantly moved.

If static text fields stored in keyframes are converted to symbols, they are in the correct position when displayed.

Text field with a filter assigned to it, e.g. Drop Shadow, doesn’t display the filter. I only tested this with Drop Shadow,.

I have updated to lime 6.3.1, openfl (8.0.2) and have (3.4.7)

Here’s a link to all the pertinent files stored in a zip file:

Open the swf file to see what supposed to happen. The top text line is the text field with a drop shadow filter. The second text line has static textfields except for the “Wash #2” field which is a dynamic field. The third text line has all static text fields converted to symbols.

Thanks in advance!


#2

Thanks for the sample, we’ll try and take a look :slight_smile:


#3

Hmm, this is a tricky one.

I believe (conceptually) the issue is that the matrix of the earlier static text instances are supposed to be applied to the later ones, but since they are separate objects, our parser is not connecting those two together. There is a big PR with improvements to MovieClip, which may account for this. I’ll need more time to look into that, and see what we can pull out. Thank you again for the sample


#4

hi, also when you right click on the input text field you will not get the default behavior of copy paste select all options which comes on any input text field anywhere.

unknown


#5

I’m not sure we could do this without a fake/custom context menu, since our text is rendered is commonly rendered with WebGL, so it isn’t a real text element


#6

:stuck_out_tongue: got it i will try with fake custom context menu for it , i don’t know if it will work or not but i will give it a try . at least for copy paste options it will be enough for my forms :smiley: thanks


#7

Another option is a DOMSprite with input text on the DOM target


#8

i will try it , but i never knew about it :smiley: i have to learn more .