From 1c9cdbf19c4eb49a1e152e388d0025564d921a3d Mon Sep 17 00:00:00 2001 From: Martin Siggel Date: Wed, 30 Jun 2021 23:05:02 +0200 Subject: [PATCH] Bumped Version to 3.2.1 --- CMakeLists.txt | 4 ++-- ChangeLog.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 15e824b3d..0d29805ef 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -9,8 +9,8 @@ endif() cmake_minimum_required (VERSION 3.4.0) -project (TIGL VERSION 3.2.0) -set(TIGL_VERSION 3.2.0) +project (TIGL VERSION 3.2.1) +set(TIGL_VERSION 3.2.1) # enable C++11 support set(CMAKE_CXX_STANDARD 11) diff --git a/ChangeLog.md b/ChangeLog.md index eefe6a238..47679ec80 100644 --- a/ChangeLog.md +++ b/ChangeLog.md @@ -7,8 +7,8 @@ Version 3.2.1 - Fixes: - - Fixed function `::tiglWingGetSegmentEtaXsi` ignoring the GetPointBehaviour that was introduced in TIGL 3.1.0: Since TiGL 3.1.0, the getPoint functions - now use the parametrization of the wing surface geometries instead . This behaviour can be switched back to the old bevahiour using `::tiglWingSetGetPointBehaviour`. + - Fixed function `::tiglWingGetSegmentEtaXsi` ignoring the GetPointBehaviour that was introduced in TIGL 3.1.0: Since TiGL 3.0.0, the getPoint functions + now use the parametrization of the wing surface geometries instead . This behaviour can be switched back to the old bevahiour using `::tiglWingSetGetPointBehavior`. Before fixing now `::tiglWingGetSegmentEtaXsi`, the functions always used the old behaviour such that the back and fort computation etaXsi -> point -> etaXsi did not result in the same values.