Version 2.15
Version 2.15
2020-02-06
<startFeed />
Summary
- Bug fixes and improvements that affects analysis that use FMPP-data as input data.
- "Conditional control tables" function released in version 2.14 had bugs, see below.
- If you copied a control category, nested properties were not copied correctly but pointed to the copied category, and vice versa. The error was unfortunately introduced in version 2.14 after some code refactorization.
- Forestand XML schema version 2020.1.0 supported when importing stand register data.
<feedDate>2020-02-06</feedDate> <endFeed />
Bug fixes and other changes
<feedDate>2020-02-06</feedDate> <endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.15.0, 2.15.1, 2.15.2, 2.14.3 orderby = fixed_in_version desc, category desc show = id,category,severity,summary,fixed_in_version,resolution summary_as_comment = true comment.305=Happens because "Random" was used as "Plot Allocation Method" for creating retention patches (see control table Nature Conservation). This will only have effect when a treatment units is represented by multiple sample plots, but will lead to unpredictable results. "Random" is no longer a possible choice. comment.306 = Bug comment.309 = User can now select species comment.308 = The regeneration and cleaning/tending proposals entered in an FMPP inventory have been imported correctly, but they have not been been applied. They are now always applied. In difference to treatment proposal that you can import and link to a stand register, FMPP regneration and cleaning proposals will be applied if even "Apply treatment proposals" is unselected. </mantis>