calling to get a system from an off thread

[jwinarske]

[08:14:16.359206] [I] From FilamentViewPlugin::on_touch You're calling to get a system from an off thread, undefined experience! Use a message to do your work or grab the ecsystemmanager strand and do your work.
[08:14:16.359219] [I] From vOnTouch You're calling to get a system from an off thread, undefined experience! Use a message to do your work or grab the ecsystemmanager strand and do your work.
[08:14:16.359220] [I] From CameraManager::aGetRayInformationFromOnTouchPosition You're calling to get a system from an off thread, undefined experience! Use a message to do your work or grab the ecsystemmanager strand and do your work.
[08:14:16.359240] [I] From CameraManager::setDefaultCamera You're calling to get a system from an off thread, undefined experience! Use a message to do your work or grab the ecsystemmanager strand and do your work.

What is the remaining work to resolve this?

[tcadanklefsen]

This one can be seen as an issue or not. This simply means a message wasn't routed through the ECS system to be handled; as its being directly called and handled - ideally you shouldnt do that, but its just an information not a warning or error. It's undefined as it might work, might not, might explode, might cause daisies spawn; or might just be fine.

[tcadanklefsen]

Ones that involve cameras/viewports were not finished with messaging; as the architecture around windowing at a global level isn't believed to be enough information. As such, its only using [0] now, where ideally these functions are told which viewport something happened on.

For example platform_views_handler.cc has this snippet

if (const auto id = touch.getId();
        listeners_.find(id) != listeners_.end()) {
      auto [fst, snd] = listeners_[id];
      if (const auto callbacks = fst; callbacks->on_touch) {
        callbacks->on_touch(touch.getAction(), touch.getPointerCount(),
                            touch.getRawPointerCoords().size(),
                            touch.getRawPointerCoords().data(), snd);
      }
    }

which calls our function, but [0] of a viewport is assumed. If its able to send an identifier over; this can then route to the correct viewport within filament as a message.