ManimCommunity / ManimCommunity/manim
Text repr to display current text
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40.9k
- Forks
- 3.1k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 25
Description
Currently, Text objects have
https://github.com/ManimCommunity/manim/blob/2462d0d0118f2b671c5d795636b09083ed8d2641/manim/mobject/text/text_mobject.py#L591-L592
and similarly for SingleStringMathTex
https://github.com/ManimCommunity/manim/blob/2462d0d0118f2b671c5d795636b09083ed8d2641/manim/mobject/text/tex_mobject.py#L108-L109
I recently made an animation that involved Transforming text objects repeatedly, during which the logging displays the original text of the objects and not their current state. This makes debugging problems slightly more work, as it can be more difficult to differentiate at what part of the scene something went wrong.
Is there a reason for the current behavior? And is there interest in changing it to display updated information? I imagine self.original_text may be changed to self.text and maybe the Transform can update tex_string itself.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read manim/mobject/text/text_mobject.py around lines 591–592 and manim/mobject/text/tex_mobject.py around lines 108–109 to understand how Text and SingleStringMathTex representations are built. Then inspect the Transform behavior mentioned in the issue. Done means logging displays the objects’ current text after repeated transformations rather than their original text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100