Set text using PrecomputedFutureTextSetterCompat on a TextView that doesn't have a MovementMethod applied yet.
The CorePluginafterSetText function then tries to set a LinkMovementMethod as a suitable default.
InternallyTextView calls setText when setting the MovementMethod
Only sometimes, but it's fairly consistent in a few of the views in my app, the combination of future text setting and setting text whilst setting the MovementMethod means my text is set to the markdown I set, but then back to an empty String.
I can see this by setting a TextWatcher on the view and logging text changes.
Please specify conditions/steps to reproduce (layout, code, markdown used, etc)
I haven't had time to set up a dummy project with the repro steps, but the steps above describe the scenario.
I'd suggest we could move the code in CorePlugin that sets the movement method to before the text is set. This is what I've done for now in my project and it's working fine. Not sure if there are any issues doing so.
PrecomputedFutureTextSetterCompaton a TextView that doesn't have aMovementMethodapplied yet.CorePluginafterSetTextfunction then tries to set aLinkMovementMethodas a suitable default.TextViewcallssetTextwhen setting theMovementMethodOnly sometimes, but it's fairly consistent in a few of the views in my app, the combination of future text setting and setting text whilst setting the
MovementMethodmeans my text is set to the markdown I set, but then back to an emptyString. I can see this by setting a TextWatcher on the view and logging text changes.I'd suggest we could move the code in CorePlugin that sets the movement method to before the text is set. This is what I've done for now in my project and it's working fine. Not sure if there are any issues doing so.