Exporting a Macro - Revision history

DavidA at 07:56, 2 July 2019

2019-07-02T07:56:46Z

2014-03-07T16:24:48Z

2013-09-05T12:47:23Z

2013-07-24T09:00:47Z

2013-07-22T14:49:57Z

2013-07-22T14:38:32Z

2013-07-18T14:43:51Z

2013-07-18T13:30:21Z

2013-07-09T11:43:50Z

2013-07-09T11:40:58Z

← Older revision		Revision as of 07:56, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:Macros</sidebar>~~
	[[File:Gen_Exporting_a_Macro_01.png\|right]]		[[File:Gen_Exporting_a_Macro_01.png\|right]]

← Older revision		Revision as of 16:24, 7 March 2014
Line 1:		Line 1:
−	<sidebar>Sidebar: ~~What Is a Macro?~~</sidebar>	+	<sidebar>Sidebar: Flowcode Help Overview:Macros</sidebar>
	[[File:Gen_Exporting_a_Macro_01.png\|right]]		[[File:Gen_Exporting_a_Macro_01.png\|right]]

@@ Line 4: / Line 4: @@
 Macros you create can be exported to a file for later use by [[Importing a Macro|importing the macro]] in another project.
-Select the Export option from the Macro menu (Macro > Export...).
+Select the 'Export' option from the 'Macro' menu (Macro > Export...).
 Flowcode will then ask you to select the macro you wish to export and then ask you for a filename to save the file.

← Older revision		Revision as of 09:00, 24 July 2013
Line 14:		Line 14:


−	If the 'Private' option is checked then the macro will be classed as 'hidden' when importing the macro. The macro will not be shown to the ~~rest of~~ the ~~flowchart~~ program ~~and will not be publicly available - these macros are for private and internal use only~~.	+	If the 'Private' option is checked then the macro's code will be classed as 'hidden' when importing the macro. The code inside the macro will not be shown but the macro can still be referenced by the program in the usual way.


	By default all macros are for private use and are 'hidden'. This is to let Flowcode know which ones to expose, the [[Interface Manager]] needs to be used to declare any or all of the macros as public - either simulation only or downloadable 'component macros'.		By default all macros are for private use and are 'hidden'. This is to let Flowcode know which ones to expose, the [[Interface Manager]] needs to be used to declare any or all of the macros as public - either simulation only or downloadable 'component macros'.

← Older revision		Revision as of 14:49, 22 July 2013
Line 11:		Line 11:


−	If the 'Read Only' option is checked then the exported macro will be locked ~~making the macro~~ unable to be edited when importing ~~back~~ into other Flowcode ~~programs~~.	+	If the 'Read Only' option is checked then the exported macro will be locked and unable to be edited when importing into other Flowcode program.


−	If the 'Private' option is checked then the ~~variables used in~~ the macro will be ~~hidden from~~ the rest of the flowchart and will only ~~be usable by that specific macro, this acts similarly to~~ '~~local~~' ~~variables~~, ~~although they can only~~ be used by the ~~macro itself and cannot be used anywhere else~~.	+	If the 'Private' option is checked then the macro will be classed as 'hidden' when importing the macro. The macro will not be shown to the rest of the flowchart program and will not be publicly available - these macros are for private and internal use only.
		+
		+
		+	By default all macros are for private use and are 'hidden'. This is to let Flowcode know which ones to expose, the [[Interface Manager]] needs to be used to declare any or all of the macros as public - either simulation only or downloadable 'component macros'.

← Older revision		Revision as of 14:38, 22 July 2013
Line 14:		Line 14:


−	If the 'Private' option is checked then the variables used in the macro will be hidden from the rest of the flowchart and will only be usable by that specific macro, this acts ~~almost like a~~ 'local' ~~variable~~, although ~~has a bit more flexibility~~.	+	If the 'Private' option is checked then the variables used in the macro will be hidden from the rest of the flowchart and will only be usable by that specific macro, this acts similarly to 'local' variables, although they can only be used by the macro itself and cannot be used anywhere else.

← Older revision		Revision as of 14:43, 18 July 2013
Line 14:		Line 14:


−	If the 'Private' option is checked then the variables used in the macro will be hidden and will only be usable by that specific macro.	+	If the 'Private' option is checked then the variables used in the macro will be hidden from the rest of the flowchart and will only be usable by that specific macro, this acts almost like a 'local' variable, although has a bit more flexibility.

← Older revision		Revision as of 13:30, 18 July 2013
Line 12:		Line 12:

	If the 'Read Only' option is checked then the exported macro will be locked making the macro unable to be edited when importing back into other Flowcode programs.		If the 'Read Only' option is checked then the exported macro will be locked making the macro unable to be edited when importing back into other Flowcode programs.
		+

	If the 'Private' option is checked then the variables used in the macro will be hidden and will only be usable by that specific macro.		If the 'Private' option is checked then the variables used in the macro will be hidden and will only be usable by that specific macro.

← Older revision		Revision as of 11:43, 9 July 2013
Line 11:		Line 11:


−	If the 'Read Only' ~~tick box~~ is ~~ticked~~ then the exported macro will be locked making the macro unable to be edited when importing back into other Flowcode programs.	+	If the 'Read Only' option is checked then the exported macro will be locked making the macro unable to be edited when importing back into other Flowcode programs.

−	If the 'Private' option is ~~ticked~~ then the variables used in the macro will be hidden ~~from the rest of the variables~~ and only usable by ~~the~~ specific macro.	+	If the 'Private' option is checked then the variables used in the macro will be hidden and will only be usable by that specific macro.

← Older revision		Revision as of 11:40, 9 July 2013
Line 11:		Line 11:


−	If the Read Only tick box is ticked then the exported macro will be locked making the macro unable to be edited when importing back into other Flowcode programs.	+	If the 'Read Only' tick box is ticked then the exported macro will be locked making the macro unable to be edited when importing back into other Flowcode programs.
		+
		+	If the 'Private' option is ticked then the variables used in the macro will be hidden from the rest of the variables and only usable by the specific macro.