-
-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
container is passed to renderer as a lambda return value, causing rendering to fail #837
Comments
Hello, I do not understand you. Could you please try again? |
I did have some questions to ask, but I made a mistake and published them without editing them. Then something happened, and I went to a meeting, and I didn't continue to edit. I am not a native English speaker, I want to express my sincerest apologies, but I can't speak English, I can only use translation software to translate, and I am a college student, not very good at technology, so the following questions, perhaps in your opinion will be relatively simple. Finally, I sincerely apologize. Next, I get to the point.
you can see that , I just use a In my country, it is very late now, so I need to go to bed, but in your country, it should be daytime now, so I may reply you after several hours, please forgive me, thank you |
well, by the way, the ftxui is so awesome! so I want to use it to develop a communication software , and use the operation like vi/vim(I like vim too, and I use arch), and I want to know that ,Is it really popular? if I done, Will full keyboard streamers like it? |
Thanks!
Don't worry. Me too ;-)
In v2, the same element is reused to draw multiple frames. Even if it might work, this is not supported. You should create a new one for every frames. |
Oh, I see what you mean. That said, it was possible for my version 1 to write vbox in lambda because lambda returns a different value each time it is rendered. Thus, it will show different effects, which is why it is necessary to write vbox in lambda. If it is not written in lambda, then no matter how many times it is rendered, the return value will not change, and it is always the outside start_container, so if it is written outside, it is theoretically OK, but it will cause the interface to render the same content many times, and it looks like there is no change. |
first of all for
The text was updated successfully, but these errors were encountered: