Version 2.16
Version 2.16
2020-07-01
<startFeed />
Summary
<feedDate>2020-06-05</feedDate> <endFeed />
- Version 2.16 contains bug fixes, improvements of existing functionality (mostly UI-related), and one new feature.
- The new feature allows you to include complex expressions in reports (PlanWise and RegWise). With this, you can create report variable conditions that are functions of other variables. This feature resembles the Sql Query-builder tools often found in GIS-applications.
<startFeed />
Bug fixes and improvements
<feedDate>2020-06-05</feedDate> <endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.16.0, 2.16.1, 2.16.2, 2.16.3 orderby = fixed_in_version desc, category desc show = id,category,severity,summary,fixed_in_version,resolution summary_as_comment = true comment.344=Removal of overstorey propsals are now performed in the period closest to the defined year comment.346= Production.cs always used the ProductionModelControlTable's parent ControlCategory for construction of (plugin) models, meaning the TreatmentModelControlTable supplied to plugins were the TMCT from the ProductionModelControlTable's parent ControlCategory. For built-in models, this only applied to SaplingHeightGrowthElfving, which gets its breeding settings from the TreatmentModelControlTable. ProductionModelControlTable no longer keeps a reference to its parent ControlCategory. It was only used for this purpose, and the currently used ControlCategory is instead supplied to the plugin constructor at simulation time. comment.342=NC-areas management programs were not saved correctly in RegWise comment.347=Linking of retention patches to parent stands failed if AreaLevel2 and AreaLevel3 were missing. comment.329=Wrong array was updated when program corrected DiameterType in input data </mantis>