ManimCommunity / ManimCommunity/manim

issue using both add_fixed_in_frame_mobjects and TransformMatchingTex

Open
#4,085 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
40.9k
Forks
3.1k
Avg merge
3d 12h
Merged PRs (30d)
25

Description

I have an issue when displaying a LaTeX equation in a ThreeDScene using add_fixed_in_frame_mobjects , and then trying to update the equation with TransformMatchingTex.

The initial equation displays perfectly, but there is a glitch when updating the equation.
The updated equation is first displayed on the (x,y) plane of the 3d scene, then disappear, then correctly displays on the frame like it should, but without the smooth transformation expected by TransformMatchingTex

```
self.add_fixed_in_frame_mobjects(eq3.shift(DOWN*3.3))
self.play(Write(eq3))
self.wait()
self.add_fixed_in_frame_mobjects(eq4.shift(DOWN*3.3))
self.play(TransformMatchingTex(eq3,eq4))
self.wait()
```

Is it a known issue, or am I doing this incorrectly?

Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with a minimal ThreeDScene reproduction using the shown add_fixed_in_frame_mobjects and TransformMatchingTex sequence. Compare the behavior of the initial and updated equations, and consider the issue done when the update stays fixed to the frame and performs the expected smooth transformation without appearing on the scene plane.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex, python
Domain
computer-graphics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.