Projects, Forms, and Controls - Revision history

C185driver: /* Controls */

2015-10-11T00:05:27Z

Controls

← Older revision		Revision as of 00:05, 11 October 2015
Line 6:		Line 6:
	A number of controls are included with App Studio. These include [[CheckBox\|CheckBox]], [[Button\|Button]], [[List\|List]], [[Grid\|Grid]], [[TextBox\|TextBox]], and other common objects.		A number of controls are included with App Studio. These include [[CheckBox\|CheckBox]], [[Button\|Button]], [[List\|List]], [[Grid\|Grid]], [[TextBox\|TextBox]], and other common objects.

	Controls are normally child elements of a specific [[Form\|Form]], and display only on that form. To reuse a control so that it displays ~~across multiple~~ forms, move the control to become a child of the NSBPage object, which contains all of the forms. The appendChild() function accomplishes this.		Controls are normally child elements of a specific [[Form\|Form]], and display only on that form. To reuse a control so that it displays globally on all forms, move the control to become a child of the NSBPage object, which contains all of the forms. The appendChild() function accomplishes this.
	<pre>		<pre>
	Sub Main()		Sub Main()
Line 12:		Line 12:
	End Sub		End Sub
	</pre>		</pre>
			Create the control once on any form at design time. To hide the control, use <code>HeaderBar1.hide()</code> at runtime.

	== Control Events ==		== Control Events ==

2015-10-10T23:47:02Z

Controls

← Older revision		Revision as of 23:47, 10 October 2015
Line 2:		Line 2:
	== Controls ==		== Controls ==

	A control is a visual object used by your program. Controls have Properties which can be queried and set, Methods which can be called as FUNCTION or SUB procedures, and Events which can be triggered by user actions, the operating system, or other programs~~. <br />~~		A control is a visual object used by your program. Controls have Properties which can be queried and set, Methods which can be called as FUNCTION or SUB procedures, and Events which can be triggered by user actions, the operating system, or other programs.
	~~A number of controls are included with App Studio. These include checkbox, commandButton, combobox, grid, textbox and other common objects~~.

			A number of controls are included with App Studio. These include [[CheckBox\|CheckBox]], [[Button\|Button]], [[List\|List]], [[Grid\|Grid]], [[TextBox\|TextBox]], and other common objects.

			Controls are normally child elements of a specific [[Form\|Form]], and display only on that form. To reuse a control so that it displays across multiple forms, move the control to become a child of the NSBPage object, which contains all of the forms. The appendChild() function accomplishes this.
			<pre>
			Sub Main()
			NSBPage.appendChild(HeaderBar1)
			End Sub
			</pre>

	== Control Events ==		== Control Events ==

2014-09-28T13:37:50Z

Program Events

← Older revision		Revision as of 13:37, 28 September 2014
Line 64:		Line 64:
	# Global code in forms, in the order the forms appear in the [[Project Explorer]]. 'firstform' does not affect this.		# Global code in forms, in the order the forms appear in the [[Project Explorer]]. 'firstform' does not affect this.
	# Global code in Project Properties and Global Code.		# Global code in Project Properties and Global Code.
	# Sub Main(), if present.		# Sub Main(), if present. Sub Main() is not called until loading is complete.
	# Form code in the first form's onshow() event. This is also the point where first form appears on the display. If you want to reconfigure some controls when the form first displays, this is the place to do it.		# Form code in the first form's onshow() event. This is also the point where first form appears on the display. If you want to reconfigure some controls when the form first displays, this is the place to do it.

2014-09-22T14:23:26Z

Program Events

← Older revision		Revision as of 14:23, 22 September 2014
Line 75:		Line 75:
	<pre>		<pre>
	'Put this in your global code		'Put this in your global code
	~~MsgBox~~ "This is the global code"		Print "This is the global code"
	Sub Main()		Sub Main()
	~~MsgBox~~ "Main"		Print "Main"
	End Sub		End Sub
	Function window_onunload()		Function window_onunload()
	~~MsgBox~~ "Unloading!"		Print "Unloading!"
	End Function		End Function
	</pre>		</pre>

2014-09-22T13:55:03Z

Program Events

← Older revision		Revision as of 13:55, 22 September 2014
Line 84:		Line 84:
	</pre>		</pre>

			window_onunload does not work on all browsers. In particular, it does not work on Chrome.
	===Browser Warning Message ===		===Browser Warning Message ===

2013-12-30T17:01:44Z

Form Events

← Older revision		Revision as of 17:01, 30 December 2013
Line 44:		Line 44:
	== Form Events ==		== Form Events ==

	Show and Hide events are called when you use ChangeForm() to go to a new form.		Show and Hide events are called when you use [[ChangeForm]]() to go to a new form.

	'''Example'''		'''Example'''

2013-12-30T17:01:28Z

Form Methods

← Older revision		Revision as of 17:01, 30 December 2013
Line 30:		Line 30:

	To go to a new form, <br />		To go to a new form, <br />
	<tt>ChangeForm(Form2)</tt>		<tt>[[ChangeForm]](Form2)</tt>

	To see the name of the current form <br />		To see the name of the current form <br />

2013-11-14T18:53:43Z

Browser Warning Message

← Older revision		Revision as of 18:53, 14 November 2013
Line 87:		Line 87:

	On startup, AppStudio apps call a function to check if the browser being used will work. If it won't, the message in [[Properties Window\|browserwarningmsg]] will be displayed. You can change the message in Project Properties. There are two more things you can do to customize how the warning message appears:		On startup, AppStudio apps call a function to check if the browser being used will work. If it won't, the message in [[Properties Window\|browserwarningmsg]] will be displayed. You can change the message in Project Properties. There are two more things you can do to customize how the warning message appears:

	1. Create your own browserWarningMessage script. This will be called instead of the default script.		1. Create your own browserWarningMessage script. This will be called instead of the default script.
	<pre>		<pre>

2013-11-14T18:53:31Z

Browser Warning Message

← Older revision		Revision as of 18:53, 14 November 2013
Line 87:		Line 87:

	On startup, AppStudio apps call a function to check if the browser being used will work. If it won't, the message in [[Properties Window\|browserwarningmsg]] will be displayed. You can change the message in Project Properties. There are two more things you can do to customize how the warning message appears:		On startup, AppStudio apps call a function to check if the browser being used will work. If it won't, the message in [[Properties Window\|browserwarningmsg]] will be displayed. You can change the message in Project Properties. There are two more things you can do to customize how the warning message appears:
	# Create your own browserWarningMessage script. This will be called instead of the default script.		1. Create your own browserWarningMessage script. This will be called instead of the default script.
	<pre>		<pre>
	Sub browserWarningMessage()		Sub browserWarningMessage()
Line 93:		Line 93:
	End Script		End Script
	</pre>		</pre>
	# You can also create your own browserWarningMessageAfterScript. This will be called only if the default script is used, and the user needs to be warned.		2. You can also create your own browserWarningMessageAfterScript. This will be called only if the default script is used, and the user needs to be warned.
	<pre>		<pre>
	Sub browserWarningMessageAfterScript()		Sub browserWarningMessageAfterScript()

2013-11-14T18:53:12Z

Program Events

@@ Line 82: / Line 82: @@
    MsgBox "Unloading!"
 End Function
 </pre>