I’m noticing the cameraViewport buttons Setpreset1 and Setpreset2 work when clicked via the parameter editor but seem to be ignoring .pulse() code triggers!?
The code runs but the positions and angles do not update.
Also, semi-related and almost a bug: when I disable the comp displaying a cameraViewport, I expect any keys to also be ignored. Currently, if I disable a cameraViewport comp container, the cameraViewport still responds to WASD et. al keys. Workaround is switching focus to another comp but expectation is for the cameraViewport to ignore all keys if its comp is disabled, no?
Sorry this has taken so long to get back to, but I was experimenting in the latest build and couldn’t reproduce either issue that you mentioned.
When you mention disabling the comp, what specifically are you doing? If I turn off the ‘enable’ parameter on the panel it no longer allows the WASD keys as I would expect.
If you are still having problems, could you send us the project file (either post here or to support@derivative.ca) and I can see if I can reproduce it?
No worries Rob, I’ve also been away travelling Le France. Fantastique!
The issues remain- check them out- but workarounds are:
Setpreset1 and Setpreset2 results can be grabbed directly from the object using op.CAM.CameraTransform.decompose() for example and this is what I was really after. When I tried to pulse() the preset buttons, nothing happened!?
If we have a stack of, e.g., 3 comps and only 1 should be active at a time, I found that the cameraViewport comp still hogs and responds to keyboard even when told not to. As stated, the workaround was to explicitly set focus to another comp.
