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
when using screen-print in query.iterator may loss message #2
Comments
Yeah, each // WORKAROUND:
// do not do this
for foo in &iterator {
screen_print!("{foo:?}");
}
// do this instead
let foos: Vec<_> = iterator.iter().collect();
screen_print!("{foos:#?}"); This is not a trivial fix because, I need to be able to "identify" the line to print, so that calling it once per frame doesn't spawn an additional line per frame, but rather just replaces the previous line. |
all right, thanks for you reply |
Would you consider changing this? I'm using this for my game and I would like to log messages when clients connect. Naturally, if two clients connect in quick succession, I don't see what I expect. Maybe an optional parameter? |
I've missed this functionality myself a bunch. This is a good reason to add it. |
Fixed by 0e19579 |
Wow, awesome! Thank you so much! |
hello , i feel confused when i am using the
screen_paint!
in my query in the system function, my query type is such asquery: Query<&GlobalTrasnform>
, then the using postion isscreen_print!("{:?}", trans.translation())
The text was updated successfully, but these errors were encountered: