You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sol::this_environment doesn't have a value, i.e. the underlying std::optional is nullopt. However , the problem goes away
when either one of the prints is enabled in the Tick function !
It seems that the prints cause some side effect that sets the this_environment ?
Tested with Sol 3.3.0 (which reports 3.2.0 in sol.hpp) and with GCC 12.2.1.
Thanks!
The text was updated successfully, but these errors were encountered:
ensisoft
added a commit
to ensisoft/detonator
that referenced
this issue
Mar 9, 2023
Add a scripting variable private flag for limiting access scope to
only to the Lua script that is associated with the entity/scene.
The goal is to ensure smaller scope for variable access and help
reduce possible game code spaghetti.
Currently, there seems to be a Lua/sol2 bug related to the Lua
environment so this means that the access check cannot always be
performed. ThePhD/sol2#1464
ensisoft
added a commit
to ensisoft/detonator
that referenced
this issue
Mar 20, 2023
Add a scripting variable private flag for limiting access scope to
only to the Lua script that is associated with the entity/scene.
The goal is to ensure smaller scope for variable access and help
reduce possible game code spaghetti.
Currently, there seems to be a Lua/sol2 bug related to the Lua
environment so this means that the access check cannot always be
performed. ThePhD/sol2#1464
ensisoft
added a commit
to ensisoft/detonator
that referenced
this issue
Mar 20, 2023
Add a scripting variable private flag for limiting access scope to
only to the Lua script that is associated with the entity/scene.
The goal is to ensure smaller scope for variable access and help
reduce possible game code spaghetti.
Currently, there seems to be a Lua/sol2 bug related to the Lua
environment so this means that the access check cannot always be
performed. ThePhD/sol2#1464
Hello,
I have the following code
sol::this_environment doesn't have a value, i.e. the underlying std::optional is nullopt. However , the problem goes away
when either one of the prints is enabled in the Tick function !
It seems that the prints cause some side effect that sets the this_environment ?
Tested with Sol 3.3.0 (which reports 3.2.0 in sol.hpp) and with GCC 12.2.1.
Thanks!
The text was updated successfully, but these errors were encountered: