CGI Studio 3.6

• Candera 3.6
• Candera/FeatStd CMake Build System Changes
• Candera Engine 2D
• Candera Engine 3D
• Transitions
• Textengine
• Courier V3.6
• FeatStd 3.6
• FeatStd Util
• SceneComposer 3.6

Candera 3.6

Candera/FeatStd CMake Build System Changes

Added flags:

 

Candera Engine 2D

Node2d GetComputedBoundingRectangle, IsInsideBoundingRectangle, IsPickIntersectingBoundingRectangle and GetEffectiveBoundingRectangle interface extended

The method 'virtual void Node2d::GetComputedBoundingRectangle(Rectangle& boundingRectangle, bool ignoreInvisible = false) const' has been extended by the additional parameter ignoreInvisible. The default value of this parameter is false for full usage backwards compatibility. If the parameter is set to true only visible parts of the scene will be considered. This also means that clipped areas are not considered for picking and/or bounding box calculations. As a consequence it is now possible to pick only visible parts of the scene.

Pivot point for Transformable2D

New methods to Transformable2D have been added that allow to manipulate the real pivot point. Those are Transformable2D::SetPivotPoint and Transformable2D::GetPivotPoint .

---

Candera Engine 3D

Generic Transform is Optional

The Property "Generic Transform" of a 3D Node became optional. The reason for that is to have as few matrix multipilcations as possible which saves performance. Further wise Generic Transforms are only used for special needs.

Pivot point for Transformable

New methods to Transformable have been added that allow to manipulate the real pivot point. Those are Transformable::SetPivotPoint and Transformable::GetPivotPoint .

---

Transitions

Sequential Transitions - Extended Hint Constructor

The constructor for Transition Hints has been extended in order to reflect the newly added ability to execute Transitions in a sequential manner.

The added parameters are:

    const FeatStd::Optional<FragmentStrategy>& activationStrategy
    const FeatStd::Optional<FragmentStrategy>& deactivationStrategy
    const FeatStd::Optional<Float>& activationDelay
    const FeatStd::Optional<Float>& deactivationDelay

FragmentStrategy is a new enum type consisting of:

Transition Rules - Check if Rule is Bidirectional

The Rule class has a new method called bool Rule::IsBidirectional() const, which returns, whether the Transition Rule is set to be bidirectional or not.

---

Textengine

AssetFontStore support for Freetype streams

AssetFontStore is extended to support two font load strategies:

Use DefaultLoadStrategySelector::SetDefaultFontLoadStrategy to select one of these load strategies. Use DefaultLoadStrategySelector::SetDefaultFontLoadStrategyExceptionList to exclude a list of fonts from the selected font load strategy.

Example:

    // Load fonts with OnRequestLoadStrategy
    selector.SetDefaultFontLoadStrategy(Candera::AssetFontStore::LoadStrategySelector::OnRequestLoadStrategy);
    // "Bitstream Vera Sans" font shall be loaded with PreloadStrategy:
    const Char* g_fontName[2] = { "ConstructionKit##ConstructionKit#Resources#Fonts#Bitstream Vera Sans", 0 };
    selector.SetDefaultFontLoadStrategyExceptionList(g_fontName);
    fontStore.SetLoadStrategySelector(&selector);

Courier applications can use Courier::ViewHandler::SetFontStoreProviderCallback to provide specific settings for the Candera::AssetFontStore in use.

Support of Monotype's WorldType-Shaper

Candera supports the WorldType-Shaper of Monotype now. The integration is done to support the font engine 'iType'. With this release complex texts can be shaped. The behavior is similar to HarfBuzz with the difference of a huge performance boost. WT-Shaper may have a higher memory consumtion as a trade-off to performance. The implementation concept is aligned with HarfBuzz to support a flexible exchangeability.

With this the default shaper of iType switches from ComplexScript to WT-Shaper. The corresponding CMake flag CANDERA_TEXTSHAPER has been extended by the entry WorldType-Shaper.

---

Courier V3.6

Data Context

Support for a Candera node 2D/3D based local data context for binding sources. Behavior/widget property bindings will be bound to the nearest binding source instead of the global binding source from the model. This enables:

Data Context Item

Each binding source can be marked as a Data Context Item by setting the flag dataContextItem to true. As a result the binding source data struct will be derived from the Data Context Item base class. Data Context Items can be handled with shared pointers. However, they will be cloned automatically when they are used as a list item. this ensures that there is no need to add synchronization handling in the view. The cloning is only performed on the struct. Each member will be cloned by using its copy constructor. If this results in a shallow copy (e.g. like for other shared pointers, reference, pointers, ...) then the instance is shared between the model and the view. Synchronization handling has to be considered within the application code for those items. The Data Context Item also enables the binding to generic lists with items of different dynamic data type (e.g. for inhomogeneous lists).

Courier List model improvements

The list model has been improved:

FeatStd 3.6

FeatStd Util

Variant explicit constructor

The Variant constructor have been changed from conversion constructor to explicit constructor. Assignment similar to the following will no longer compile:

FeatStd::Variant variant = 1;

Furthermore, the direct usage of values (e.g. Int values) as paremeters will no longer compile:

FeatStd::Optional<FeatStd::Variant> optionalVariant = FeatStd::Optional<FeatStd::Variant>(1)

Since the constructor is no longer inserted automatically by the compiler it has to be inserted manually to make

FeatStd::Variant variant = FeatStd::Variant(1);
FeatStd::Optional<FeatStd::Variant> optionalVariant = FeatStd::Optional<FeatStd::Variant>(FeatStd::Variant(1));

the code compile again:

Variant explicit constructor

The list of supported types that a FeatStd::Variant can handle has been extended. Beside the converting getter methods also TryGet methods are provided that will indicate if the, conversion was limited by the value range of the result type (e.g. a value 256 converted to a UInt8 will result in the value 255 due to the range limit of UInt8).

---

SceneComposer 3.6

New Feature

Description of New Feature

---