Version 1.0.2 - Revision history

Peder at 14:13, 14 November 2017

2017-11-14T14:13:39Z

← Older revision		Revision as of 15:13, 14 November 2017
Line 1:		Line 1:
	{{Languages}}		{{Languages}}
			[[Category:ReleaseNotes archive]]
	[[Category:~~Release~~]]		[[newsdate::2010-01-15]]
	[[~~Release date~~::2010-01-15]]

	== New features ==		== New features ==

Peder: /* Next release */

2010-02-15T12:20:08Z

Next release

← Older revision		Revision as of 13:20, 15 February 2010
Line 51:		Line 51:

	==Next release==		==Next release==
	The next version is planned to be released in only two weeks, that is February 26. It will include functionality ~~for~~		The next version is planned to be released in only two weeks, that is February 26. It will include functionality to
	~~auomatically creating~~ a forest database, so that ~~users~~ will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.		automatically create a forest database, so that you will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.

Peder: /* Installation */

2010-02-15T12:19:21Z

Installation

← Older revision		Revision as of 13:19, 15 February 2010
Line 38:		Line 38:
	* The growth and yield predictions are very sensitive to the choice of height growth functions (up to 20% diff in volume). We are currently investigated this issue.		* The growth and yield predictions are very sensitive to the choice of height growth functions (up to 20% diff in volume). We are currently investigated this issue.

	==Installation ==		==Important! Installation instructions ==
	# Because of name and path changes, the automatic upgrade with ClickOnce will not work, and '''you must uninstall previous versions av all programs'''. You do this through Add/Remove programs in the Controlpanel (or equivalent depending on OS and language).		# Because of name and path changes, the automatic upgrade with ClickOnce will not work, and '''you must uninstall previous versions av all programs'''. You do this through Add/Remove programs in the Controlpanel (or equivalent depending on OS and language).
	# Upgrade existing databases in two steps:		# Upgrade existing databases in two steps:

Peder: /* Installation */

2010-02-15T12:18:50Z

Installation

← Older revision		Revision as of 13:18, 15 February 2010
Line 39:		Line 39:

	==Installation ==		==Installation ==
	# ~~Becasue~~ of name and path changes, the automatic upgrade with ClickOnce will not work, and '''you must uninstall previous versions av all programs'''. You do this through Add/Remove programs in the Controlpanel (or equivalent depending on OS and language).		# Because of name and path changes, the automatic upgrade with ClickOnce will not work, and '''you must uninstall previous versions av all programs'''. You do this through Add/Remove programs in the Controlpanel (or equivalent depending on OS and language).
	# Upgrade existing databases in two steps:		# Upgrade existing databases in two steps:
	#* First to version 1.0.2.0: [[Heureka_database_upgrade_script_1.0.2.0]].		#* First to version 1.0.2.0: [[Heureka_database_upgrade_script_1.0.2.0]].
Line 48:		Line 48:
	#* Rename the folder RegVis to RegWise		#* Rename the folder RegVis to RegWise
	#* Rename the folder PlanBeslut to PlanEval		#* Rename the folder PlanBeslut to PlanEval
			#After the upgrade from BeståndsVis to StandWise, your chart templates do not appear in the list of available charts. Would you like to have access to the old templates you should rename the folder "My Documents \ Heureka \ Common \ StandVis Diagrams", to "My Documents \ Heureka \ Common \ StandWise Graphs"

	==Next release==		==Next release==
	The next version is planned to be released in only two weeks, that is February 26. It will include functionality for		The next version is planned to be released in only two weeks, that is February 26. It will include functionality for
	auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.		auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.

Peder: /* Installation */

2010-02-15T12:17:23Z

Installation

← Older revision		Revision as of 13:17, 15 February 2010
Line 44:		Line 44:
	#* Then to version 1.0.2.1: [[Heureka_database_upgrade_script_1.0.2.1]]		#* Then to version 1.0.2.1: [[Heureka_database_upgrade_script_1.0.2.1]]
	# If you've used previous Heureka versions and want to find project files easily you should rename the '''project folders'''. These can be found under My Documents> Heureka> Projects (called a bit different depending on the operating system and language):		# If you've used previous Heureka versions and want to find project files easily you should rename the '''project folders'''. These can be found under My Documents> Heureka> Projects (called a bit different depending on the operating system and language):
	# * Rename the folder BeståndsVis to StandWise		#* Rename the folder BeståndsVis to StandWise
	# * Rename the folder to PlanVis PlanWise		#* Rename the folder to PlanVis PlanWise
	# * Rename the folder RegVis to RegWise		#* Rename the folder RegVis to RegWise
	# * Rename the folder PlanBeslut to PlanEval		#* Rename the folder PlanBeslut to PlanEval

	==Next release==		==Next release==
	The next version is planned to be released in only two weeks, that is February 26. It will include functionality for		The next version is planned to be released in only two weeks, that is February 26. It will include functionality for
	auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.		auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.

Peder: /* Installation */

2010-02-15T12:17:10Z

Installation

← Older revision		Revision as of 13:17, 15 February 2010
Line 39:		Line 39:

	==Installation ==		==Installation ==
	*Becasue of name and path changes, the automatic upgrade with ClickOnce will not work, and '''you must uninstall previous versions av all programs'''. You do this through Add/Remove programs in the Controlpanel (or equivalent depending on OS and language).		# Becasue of name and path changes, the automatic upgrade with ClickOnce will not work, and '''you must uninstall previous versions av all programs'''. You do this through Add/Remove programs in the Controlpanel (or equivalent depending on OS and language).
	*Upgrade existing databases in two steps:		# Upgrade existing databases in two steps:
	# First to version 1.0.2.0: [[Heureka_database_upgrade_script_1.0.2.0]].		#* First to version 1.0.2.0: [[Heureka_database_upgrade_script_1.0.2.0]].
	# Then to version 1.0.2.1: [[Heureka_database_upgrade_script_1.0.2.1]]		#* Then to version 1.0.2.1: [[Heureka_database_upgrade_script_1.0.2.1]]
			# If you've used previous Heureka versions and want to find project files easily you should rename the '''project folders'''. These can be found under My Documents> Heureka> Projects (called a bit different depending on the operating system and language):
			# * Rename the folder BeståndsVis to StandWise
			# * Rename the folder to PlanVis PlanWise
			# * Rename the folder RegVis to RegWise
			# * Rename the folder PlanBeslut to PlanEval

	==Next release==		==Next release==
	The next version is planned to be released in only two weeks, that is February 26. It will include functionality for		The next version is planned to be released in only two weeks, that is February 26. It will include functionality for
	auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.		auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.

Peder: /* PlanStart */

2010-02-15T11:32:28Z

PlanStart

← Older revision		Revision as of 12:32, 15 February 2010
Line 8:		Line 8:
	==== PlanStart ====		==== PlanStart ====
	* Function for importing [[Ivent]]-data now works as expected		* Function for importing [[Ivent]]-data now works as expected
	* The fields MapId and SubStandId in the [[Import_of_stand_register#File_specification \| stand register import template]] are now obsolete. The field StandId alone is used as treatment unit id.		* The fields <code>MapId</code> and <code>SubStandId</code> in the [[Import_of_stand_register#File_specification \| stand register import template]] are now obsolete. The field <code>StandId</code> alone is used as treatment unit id.

	==== Common for PlanWise, RegWise, and StandWise ====		==== Common for PlanWise, RegWise, and StandWise ====

Peder: /* PlanStart */

2010-02-15T11:27:02Z

PlanStart

← Older revision		Revision as of 12:27, 15 February 2010
Line 8:		Line 8:
	==== PlanStart ====		==== PlanStart ====
	* Function for importing [[Ivent]]-data now works as expected		* Function for importing [[Ivent]]-data now works as expected
	* The fields MapId and SubStandId in the [[Import_of_stand_register#File_specification stand register import template]] are now obsolete. The field StandId alone is used as treatment unit id.		* The fields MapId and SubStandId in the [[Import_of_stand_register#File_specification \| stand register import template]] are now obsolete. The field StandId alone is used as treatment unit id.

	==== Common for PlanWise, RegWise, and StandWise ====		==== Common for PlanWise, RegWise, and StandWise ====

Peder: /* PlanStart */

2010-02-15T11:26:47Z

PlanStart

← Older revision		Revision as of 12:26, 15 February 2010
Line 8:		Line 8:
	==== PlanStart ====		==== PlanStart ====
	* Function for importing [[Ivent]]-data now works as expected		* Function for importing [[Ivent]]-data now works as expected
			* The fields MapId and SubStandId in the [[Import_of_stand_register#File_specification stand register import template]] are now obsolete. The field StandId alone is used as treatment unit id.

	==== Common for PlanWise, RegWise, and StandWise ====		==== Common for PlanWise, RegWise, and StandWise ====

Peder: /* Next release */

2010-02-15T11:22:55Z

Next release

← Older revision		Revision as of 12:22, 15 February 2010
Line 44:		Line 44:

	==Next release==		==Next release==
	The next version is planned to be released in only two weeks, that is February 26. It will ~~contain functions~~ for		The next version is planned to be released in only two weeks, that is February 26. It will include functionality for
	auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.		auomatically creating a forest database, so that users will not have to download a backup-file and restore it in PlanStart etc. Also, database upgrading will be automatic, making the manual upgrading process obsolete.