XML: Bubble Sort utilizing XMLVARs - Revision history

Rpmc at 01:43, 12 May 2015

2015-05-12T01:43:00Z

← Older revision		Revision as of 20:43, 11 May 2015
Line 92:		Line 92:
	'''FINALLY''' - Note that I placed a '''space after the ampersand &''' in 4 places above (one in the Code and three in the Notes) so that it would display properly in the wiki. Please remove that space in your XML		'''FINALLY''' - Note that I placed a '''space after the ampersand &''' in 4 places above (one in the Code and three in the Notes) so that it would display properly in the wiki. Please remove that space in your XML

	Bob		[[Bob]]

	[[Category:Aircraft Design]]		[[Category:Aircraft Design]]
	[[Category:Panel and Gauge Design]]		[[Category:Panel and Gauge Design]]

Rpmc: Rpmc moved page XML Bubble Sort utilizing XMLVARs to XML: Bubble Sort utilizing XMLVARs

2014-08-25T07:44:41Z

Rpmc moved page XML Bubble Sort utilizing XMLVARs to XML: Bubble Sort utilizing XMLVARs

← Older revision	Revision as of 02:44, 25 August 2014
(No difference)

Rpmc at 15:25, 6 July 2014

2014-07-06T15:25:13Z

← Older revision		Revision as of 10:25, 6 July 2014
Line 5:		Line 5:
	\| FSXA = true		\| FSXA = true
	\| FSX = true		\| FSX = true
	\| FS2004 = ~~false~~		\| FS2004 = true
	\| FS2002 = false		\| FS2002 = false
	\| FS2000 = unknown		\| FS2000 = unknown

BASys: Infobox-Applicable-FSVersion added.

2014-06-02T16:02:59Z

Infobox-Applicable-FSVersion added.

← Older revision		Revision as of 11:02, 2 June 2014
Line 1:		Line 1:
	~~[[Category:Aircraft Design]]~~		{{Infobox-Applicable-FSVersion
	~~[[Category:Panel and Gauge Design]]~~		\| P3D2 = true
			\| P3D = true
			\| FSXI = false
			\| FSXA = true
			\| FSX = true
			\| FS2004 = false
			\| FS2002 = false
			\| FS2000 = unknown
			\| FS98 = unknown
			\| XP10 = false
			\| XP9 = false
			}}

	Recently, a question about sorting came up. The context was an ICAO Search of Facility types which returns ICAO strings in alphabetical order. However, each ICAO represents a Facility that is a certain distance from the user's aircraft, and proper display of the Facility information required a sort according to distance from the aircraft, not alphabetical order of the ICAO string.		Recently, a question about sorting came up.
			The context was an ICAO Search of Facility types which returns ICAO strings in alphabetical order.
			However, each ICAO represents a Facility that is a certain distance from the user's aircraft, and proper display of the Facility information required a sort according to distance from the aircraft, not alphabetical order of the ICAO string.

	Acknowledgements are owed to Robbie McElrath who provided the Bubble Sort XML (thank you, Robbie) and Tom Aguilo, for providing XMLVARs. The sort script that follows makes use of the array-forming capabilities of XMLVARS. Thanks, Tom.		Acknowledgements are owed to Robbie McElrath who provided the Bubble Sort XML (thank you, Robbie) and Tom Aguilo, for providing XMLVARs.
			The sort script that follows makes use of the array-forming capabilities of XMLVARS. Thanks, Tom.

	'''MACROS:'''		'''MACROS:'''
Line 79:		Line 93:

	Bob		Bob

			[[Category:Aircraft Design]]
			[[Category:Panel and Gauge Design]]

Rpmc at 04:25, 2 June 2014

2014-06-02T04:25:32Z

← Older revision		Revision as of 23:25, 1 June 2014
Line 66:		Line 66:
	- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information, for example, would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.		- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information, for example, would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.

	- The bottom 6 lines in the Update section simply read the XMLVARs and store ~~then~~ into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied). Again, for testing purposes.		- The bottom 6 lines in the Update section simply read the XMLVARs and store them into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied). Again, for testing purposes.

	- A Mouse Area 'click area' is used to execute the sort macro, @sort('sort_test', 6). The number 6 is the array length to be sorted. In the real example I postulated, it would be written @sort('sort_test',C:fs9gps:IcaoSearchMatchedIcaosNumber).		- A Mouse Area 'click area' is used to execute the sort macro, @sort('sort_test', 6). The number 6 is the array length to be sorted. In the real example I postulated, it would be written @sort('sort_test',C:fs9gps:IcaoSearchMatchedIcaosNumber).

Rpmc at 14:32, 18 February 2014

2014-02-18T14:32:38Z

← Older revision		Revision as of 09:32, 18 February 2014
Line 66:		Line 66:
	- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information, for example, would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.		- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information, for example, would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.

	- The bottom 6 lines in the Update section simply read the XMLVARs and store then into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied)		- The bottom 6 lines in the Update section simply read the XMLVARs and store then into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied). Again, for testing purposes.

	- A Mouse Area 'click area' is used to execute the sort macro, @sort('sort_test', 6). The number 6 is the array length to be sorted. In the real example I postulated, it would be written @sort('sort_test',C:fs9gps:IcaoSearchMatchedIcaosNumber).		- A Mouse Area 'click area' is used to execute the sort macro, @sort('sort_test', 6). The number 6 is the array length to be sorted. In the real example I postulated, it would be written @sort('sort_test',C:fs9gps:IcaoSearchMatchedIcaosNumber).

Rpmc at 14:31, 18 February 2014

2014-02-18T14:31:39Z

← Older revision		Revision as of 09:31, 18 February 2014
Line 64:		Line 64:
	- (L:sort_len, number) is the array length. For example, IcaoSearchMatchedIcaosNumber		- (L:sort_len, number) is the array length. For example, IcaoSearchMatchedIcaosNumber

	- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.		- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information, for example, would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.

	- The bottom 6 lines in the Update section simply read the XMLVARs and store then into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied)		- The bottom 6 lines in the Update section simply read the XMLVARs and store then into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied)

Rpmc at 14:30, 18 February 2014

2014-02-18T14:30:44Z

← Older revision		Revision as of 09:30, 18 February 2014
Line 33:		Line 33:
	'''UPDATE:'''		'''UPDATE:'''
	<Update Frequency="18" Hidden="No">		<Update Frequency="18" Hidden="No">
	(L:~~SortInit~~, bool) 0 ==		(L:StoreInit, bool) 0 ==
	if{		if{
	2 @store('sort_test', 0)		2 @store('sort_test', 0)
Line 41:		Line 41:
	7 @store('sort_test', 4)		7 @store('sort_test', 4)
	0 @store('sort_test', 5)		0 @store('sort_test', 5)
	1 (>L:~~SortInit~~, bool)		1 (>L:StoreInit, bool)
	}		}

Line 64:		Line 64:
	- (L:sort_len, number) is the array length. For example, IcaoSearchMatchedIcaosNumber		- (L:sort_len, number) is the array length. For example, IcaoSearchMatchedIcaosNumber

	- The ~~SortInit~~ sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information would actually generate the values to be stored in these XMLVARs and a ~~SortInit~~ sequence would probably never be ~~needed~~.		- The StoreInit sequence was used for testing purposes only. It stores 2, 1, 4, 8, 7, and 0 into XMLVARs named 'sort_test0' through 'sort_test5'. In a real application, GeoCalcDistance information would actually generate the values to be stored in these XMLVARs and a StoreInit sequence would probably never be used.

	- The bottom 6 lines in the Update section simply read the XMLVARs and store then into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied)		- The bottom 6 lines in the Update section simply read the XMLVARs and store then into traditional L:Vars so that BlackBox can display them (so you can see what is happening before and after the sort is applied)

Rpmc at 14:29, 18 February 2014

2014-02-18T14:29:15Z

← Older revision		Revision as of 09:29, 18 February 2014
Line 2:		Line 2:
	[[Category:Panel and Gauge Design]]		[[Category:Panel and Gauge Design]]

	Recently, a question about sorting came up. The context was an ICAO Search of Facility types which returns ICAO strings in alphabetical order. However, each ICAO represents a Facility that is a certain distance from the user's aircraft, and proper display of the Facility information required a sort according to distance.		Recently, a question about sorting came up. The context was an ICAO Search of Facility types which returns ICAO strings in alphabetical order. However, each ICAO represents a Facility that is a certain distance from the user's aircraft, and proper display of the Facility information required a sort according to distance from the aircraft, not alphabetical order of the ICAO string.

	Acknowledgements are owed to Robbie McElrath who provided the Bubble Sort XML (thank you, Robbie) and Tom Aguilo, for providing XMLVARs. The sort script that follows makes use of the array-forming capabilities of XMLVARS. Thanks, Tom.		Acknowledgements are owed to Robbie McElrath who provided the Bubble Sort XML (thank you, Robbie) and Tom Aguilo, for providing XMLVARs. The sort script that follows makes use of the array-forming capabilities of XMLVARS. Thanks, Tom.

Rpmc at 14:27, 18 February 2014

2014-02-18T14:27:50Z

← Older revision		Revision as of 09:27, 18 February 2014
Line 2:		Line 2:
	[[Category:Panel and Gauge Design]]		[[Category:Panel and Gauge Design]]

	Recently, a question about sorting ~~has come~~ up. The context was an ICAO Search of Facility types which returns ICAO strings in alphabetical order. However, each ICAO represents a Facility that is a certain distance from the user's aircraft, and proper display of the Facility information required a sort according to distance.		Recently, a question about sorting came up. The context was an ICAO Search of Facility types which returns ICAO strings in alphabetical order. However, each ICAO represents a Facility that is a certain distance from the user's aircraft, and proper display of the Facility information required a sort according to distance.

	Acknowledgements are owed to Robbie McElrath who provided the Bubble Sort XML (thank you, Robbie) and Tom Aguilo, for providing XMLVARs. The sort script that follows makes use of the array-forming capabilities of XMLVARS. Thanks, Tom.		Acknowledgements are owed to Robbie McElrath who provided the Bubble Sort XML (thank you, Robbie) and Tom Aguilo, for providing XMLVARs. The sort script that follows makes use of the array-forming capabilities of XMLVARS. Thanks, Tom.