mrmaxm
mrmaxm
> Yes, via identifying parameters which are sensor type specific, e.g. (completely made-up identifying parameters): That makes good sense. Providing default behaviour assuming it subscribes to "first", and allowing devs...
> Just to clarify, gyro.x is a getter for the last, asynchronously polled x value of the gyroscope, which is stored in a shared memory buffer. It is not a...
If sensor has `reading` property, which is an object, with properties, then developer in event might assume it is immutable and/or instanced. This could lead to confusion like: ```javascript var...
@alexshalamov @tobie - have answered pretty well. GC stalls is very known problem working with real-time apps. Current design on it's own wont lead to long GC, but it makes...
> Could we instead provide a method that will fill sensor reading data, e.g. Sensor.getReading(Dictionary out); or Sensor.read(Dictionary out);? This will allow to reuse object, yet, main interface is not...
> I don't think a function call is a huge perf drag nowadays. It was in the days of IE6, but those are behind us at this point. I'm more...
I believe if force updating projects to clustered lighting will result in the need for migrations and/or break some existing projects due to their custom setup, then it should not...
> * Having a right click context menu of some sort that lists all the parents This is a good method, that I've seen in similar context in other places....
Swapping permissions between users - will be a workaround for team size limits for some. Although, it is doable already by removing/adding users. Good idea though, especially when working with...
> There's also the opposite problem of wanting to hide an entity in the scene without disabling it. That is doable by disabling model/render/element component. > Enabling an entity that...