Release R5.24

  

What is interfacing?

This is a simple yet powerful feature that drastically increases the modularity of Ventuz, making collaborative work more effective than ever. Interfaces are exposings that remain existent even if you delete the actual content of a container. This enables you to separate the logical work from the design part by allowing you to create a ‘communication’ interface with a container upfront, then implement the content later. Of course you can exchange such content easily or drag&drop the content from one container to another – without losing the bindings!


We have written a whitepaper that explains the full functionality of interface containers. Please find the whitepaper here!





Another big feature: Scene Ports now act ‘like’ containers and of course, they can have interfaces! Because of that Cross-Scene-Bindings are now possible!

Release Note of R5.24

FEATURE	F494	It is now possible to repeat a paste operation of nodes with the RMB if one copies via drag&drop with pressed Modifier keys!
FEATURE	F511	If the monitoring mode in the Animation Editor is enabled, it’s possible to play/pause/continue an animation by pressing Space key.
FEATURE	F517	The Hardware profile for serial com ports can now address the local hardware explicitly in addition to the system enumeration.
FEATURE	F522	It is now possible to navigate to source nodes which provide values for Input/Output properties. This even enables the navigation to nodes which expose certain properties. A long right mouse button click on the property name in the Property Editor brings up the context menu with several navigation options.
FEATURE	F523	Introducing the new Interface Container concept. Now it is possible to mark Content/Hierarchy Containers as Interface Container. The content of such containers can be exchanged leaving the bindings connected. See the Interfacing document for further details!
FEATURE	F524	It’s possible now to navigate to Nodes that have written messages to the Message Log window by double-clicking on the new icon left to the message.
CHANGE	C182	Bound and exposed Input properties are now displayed and handles as Output properties on higher Container levels.
CHANGE	C277	The Keyframe Animation node now hides its methods and output properties if it doesn’t have any State logic or if it is controlled by a Controller/Animation node.
CHANGE	C278	Content nodes (e.g. Text Effects) which can be dropped on bindings restore the original binding if these nodes are deleted.
CHANGE	C279	Changing the Blocked/Inactive state of a node in Ventuz Designer marks the scene as modified now!
BUG	B158	Copy & Paste of Slide nodes erased the settings in the Pivot and State properties. Fixed!
BUG	B439	Very huge DDS textures (8k x 8k) could cause a memory leak in the preview of the File Open dialog. Fixed!
BUG	B440	The internal memory statistics displayed incorrect values for DDS textures with DXT compression. Fixed!
BUG	B443	Bindings from output properties of container nodes were always added twice to the internal collections. This could corrupt the consistency of the scene. This issue is now detected when loading a scene to the Designer and can be fixed in the Consistency Check.
BUG	B444	Resource Loader (like ImageLoader, Movie nodes etc.) were not informed about missing resources. This caused errors in the following. Fixed!
BUG	B445	If one selected Hierarchy Nodes in the Hierarchy Editor, they were not always brought to view in the Content Editor. This is fixed now!
BUG	B446	After disconnecting embedded animations, references between the animations remained alive. Fixed!
BUG	B450	Texture Fonts and Advanced ImageLoader could produce wrong values for Memory Statistics. Fixed!

Please download the new release here!