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
The ray casting functions assume that wall collections are sorted by their positions in relation to an axis in ascending order; if new walls are created and added to the collection, there might be the need of re-sorting collections to ensure that the processing order of the algorithms is correct. However, collections are protected so there is no way to directly sort their elements; we might need to make some improvements to CASES.js so that we can sort collections.
Alternatively we could solve the problem by implementing an abstraction layer that solves the problem, such as storing walls in an array inside another object, that provides free access to them; then storing that object at a collection named 'Scene'. The drawback is that more complexity is added, which could affect maintainability and performance.
The text was updated successfully, but these errors were encountered:
The ray casting functions assume that wall collections are sorted by their positions in relation to an axis in ascending order; if new walls are created and added to the collection, there might be the need of re-sorting collections to ensure that the processing order of the algorithms is correct. However, collections are protected so there is no way to directly sort their elements; we might need to make some improvements to CASES.js so that we can sort collections.
Alternatively we could solve the problem by implementing an abstraction layer that solves the problem, such as storing walls in an array inside another object, that provides free access to them; then storing that object at a collection named 'Scene'. The drawback is that more complexity is added, which could affect maintainability and performance.
The text was updated successfully, but these errors were encountered: