",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "display::text",
+ "wordwrap": True
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 1,
+ "name": "noteLabel",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Note:",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "label",
+ "word_wrap": False
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 1,
+ "name": "noteInput",
+ "password": False,
+ "read_only": False,
+ "rows": 1,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "input::string",
+ "value": ""
+ }
+ ]
+ ],
+ "control": {
+ "id": "Wizard"
+ },
+ "embedding": "always_toplevel",
+ "position": "automatic",
+ "size": {
+ "height": 530,
+ "width": 1191
+ },
+ "sizemode": "fixed",
+ "style": "",
+ "title": {
+ "id": "",
+ "text": "Construct Fitting Cylinder (Step 4)",
+ "translatable": True
+ }
+})
+
+
+
+
+current_step = -1
+new_step = 0
+steps = [DIALOG, STEP_2, STEP_3, STEP_4]
+inputStrings = ['', '', '', '']
+def handler_func (widget):
+ global current_step, new_step
+ global current_dialog
+
+ if widget == current_dialog.control.next:
+ if current_step + 1 < len (steps):
+ new_step = current_step + 1
+ gom.script.sys.close_user_defined_dialog (dialog=current_dialog)
+ elif widget == current_dialog.control.prev:
+ if current_step > 0:
+ new_step = current_step - 1
+ gom.script.sys.close_user_defined_dialog (dialog=current_dialog)
+
+
+ current_dialog.control.prev.enabled = current_step > 0
+ current_dialog.control.next.enabled = current_step + 1 < len (steps)
+ current_dialog.control.close.enabled = current_step + 1 >= len (steps)
+
+while current_step != new_step :
+ current_step = new_step
+ current_dialog = steps[current_step]
+ current_dialog.handler = handler_func
+ RESULT=gom.script.sys.show_user_defined_dialog (dialog=current_dialog)
+ inputStrings[current_step] = RESULT.noteInput
+
+
+# Print out the acquired input:
+print(inputStrings[0])
+print(inputStrings[1])
+print(inputStrings[2])
+print(inputStrings[3])
diff --git a/2022-new-headings-intros/_downloads/cbebcc2e1c7dcf042fbff10ce916f294/timer.py b/2022-new-headings-intros/_downloads/cbebcc2e1c7dcf042fbff10ce916f294/timer.py
new file mode 100644
index 0000000..abca1ba
--- /dev/null
+++ b/2022-new-headings-intros/_downloads/cbebcc2e1c7dcf042fbff10ce916f294/timer.py
@@ -0,0 +1,303 @@
+# -*- coding: utf-8 -*-
+
+import gom
+
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ "columns": 2,
+ "name": "separator",
+ "rows": 1,
+ "title": {
+ "id": "",
+ "text": "Control",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "separator"
+ },
+ {
+ }
+ ],
+ [
+ {
+ "button_type": "push",
+ "columns": 2,
+ "icon": "AAAAAA==",
+ "icon_file_name": "",
+ "icon_size": {
+ "value": "icon"
+ },
+ "icon_system_size": {
+ "value": "default"
+ },
+ "icon_system_type": {
+ "value": "ok"
+ },
+ "icon_type": {
+ "value": "none"
+ },
+ "name": "start",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Start",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "button::pushbutton"
+ },
+ {
+ }
+ ],
+ [
+ {
+ "button_type": "push",
+ "columns": 2,
+ "icon": "AAAAAA==",
+ "icon_file_name": "",
+ "icon_size": {
+ "value": "icon"
+ },
+ "icon_system_size": {
+ "value": "default"
+ },
+ "icon_system_type": {
+ "value": "ok"
+ },
+ "icon_type": {
+ "value": "none"
+ },
+ "name": "stop",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Stop",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "button::pushbutton"
+ },
+ {
+ }
+ ],
+ [
+ {
+ "columns": 2,
+ "name": "separator_1",
+ "rows": 1,
+ "title": {
+ "id": "",
+ "text": "Parameters",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "separator"
+ },
+ {
+ }
+ ],
+ [
+ {
+ "columns": 1,
+ "name": "interval_label",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Interval",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "label",
+ "word_wrap": False
+ },
+ {
+ "background_style": "",
+ "columns": 1,
+ "maximum": 10,
+ "minimum": 0.01,
+ "name": "interval",
+ "precision": 2,
+ "rows": 1,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "input::number",
+ "unit": "SHUTTER",
+ "value": 1
+ }
+ ],
+ [
+ {
+ "columns": 2,
+ "name": "separator_2",
+ "rows": 1,
+ "title": {
+ "id": "",
+ "text": "State",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "separator"
+ },
+ {
+ }
+ ],
+ [
+ {
+ "columns": 2,
+ "data": "AAAAAA==",
+ "file_name": "",
+ "height": 0,
+ "keep_aspect": True,
+ "keep_original_size": True,
+ "name": "image",
+ "rows": 1,
+ "system_image": "system_message_warning",
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "image",
+ "use_system_image": True,
+ "width": 0
+ },
+ {
+ }
+ ],
+ [
+ {
+ "columns": 2,
+ "maximum_size": -1,
+ "minimum_size": 0,
+ "name": "spacer",
+ "rows": 1,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "spacer::vertical"
+ },
+ {
+ }
+ ],
+ [
+ {
+ "button_type": "push",
+ "columns": 2,
+ "icon": "AAAAAA==",
+ "icon_file_name": "",
+ "icon_size": {
+ "value": "icon"
+ },
+ "icon_system_size": {
+ "value": "default"
+ },
+ "icon_system_type": {
+ "value": "ok"
+ },
+ "icon_type": {
+ "value": "none"
+ },
+ "name": "exit",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Exit",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "button::pushbutton"
+ },
+ {
+ }
+ ]
+ ],
+ "control": {
+ "id": "Empty"
+ },
+ "embedding": "always_toplevel",
+ "position": "automatic",
+ "size": {
+ "height": 368,
+ "width": 188
+ },
+ "sizemode": "fixed",
+ "style": "Standard",
+ "title": {
+ "id": "",
+ "text": "Test Timer",
+ "translatable": True
+ }
+})
+
+#
+# Event handler function called if anything happens inside of the dialog
+#
+state = False
+def dialog_event_handler (widget):
+ global state
+
+ if widget == DIALOG.start:
+ DIALOG.timer.interval = DIALOG.interval.value * 1000
+ DIALOG.timer.enabled = True
+ DIALOG.start.enabled = False
+ DIALOG.stop.enabled = True
+ elif widget == DIALOG.stop:
+ DIALOG.timer.enabled = False
+ DIALOG.start.enabled = True
+ DIALOG.stop.enabled = False
+ elif widget == DIALOG.interval:
+ DIALOG.timer.interval = DIALOG.interval.value * 1000
+ elif widget == DIALOG.exit:
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+ elif hasattr(widget, '__str__') and str(widget) == 'system':
+ print("Its a system event.")
+ elif hasattr(widget, '__str__') and str(widget) == 'timer':
+ print("Its a timer event. Let´s swap the image.")
+ state = not state
+
+ if state:
+ DIALOG.image.system_image = 'system_message_warning'
+ else:
+ DIALOG.image.system_image = 'system_message_question'
+
+
+
+DIALOG.handler = dialog_event_handler
+DIALOG.stop.enabled = False
+
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
diff --git a/2022-new-headings-intros/_downloads/df5001d15c7f4e6de709b26bc23e46df/scriptingEditorExampleDialog.py b/2022-new-headings-intros/_downloads/df5001d15c7f4e6de709b26bc23e46df/scriptingEditorExampleDialog.py
new file mode 100644
index 0000000..d465bcc
--- /dev/null
+++ b/2022-new-headings-intros/_downloads/df5001d15c7f4e6de709b26bc23e46df/scriptingEditorExampleDialog.py
@@ -0,0 +1,248 @@
+# -*- coding: utf-8 -*-
+
+import gom
+
+
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ "columns": 1,
+ "data": "AAAAAYlQTkcNChoKAAAADUlIRFIAAACMAAAAuQgCAAAAdRVAdwAAAAlwSFlzAAAOwwAADsMBx2+oZAAADmVJREFUeJxivHTpEsMoGMSAgYEBAAAA//9iGo2fQQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//xqNpMEOGBgYAAAAAP//Go0kKgM9MKCioQwMDAAAAAD//xqNJKoBSPQIXy6mrrEMDAwAAAAA//9iGTA/DSMAyTq0iB4GBgYGBgYAAAAA//8ajSRKAY1yDxwwMDAAAAAA//8ajSTyAa0zEAQwMDAAAAAA//8ajSTyAWSFtp4ubaOKgYEBAAAA//8abThQCmi9mJ6BgQEAAAD//xrNSZQCeJ30VreXFuYzMDAAAAAA//8azUnUBJfAgLpmMjAwAAAAAP//Gt36QhFAzkY0CkkGBgYAAAAA//8azUnkAzo0vhkYGBgYGAAAAAD//xqNJCoAmmYjBgYGAAAAAP//Go0kMgHdshEDAwMAAAD//xqNJEoBrbMRAwMDAAAA//8ajSRyAD2zEQMDAwAAAP//Go0kigAdshEDAwMAAAD//xqNJJIBnbMRAwMDAAAA//8ajSTyAX2yEQMDAwAAAP//Go0k0gB9eq/IgIGBAQAAAP//Go2kwQ4YGBgAAAAA//8ajSQSwIBkIwYGBgAAAAD//xqNJGIB/dsLEMDAwAAAAAD//xqNJJIBnbMRAwMDAAAA//8ajSSiwABmIwYGBgAAAAD//xqNJNIA/bMRAwMDAAAA//8ajSTCYGCzEQMDAwAAAP//Go0kEsCAZCMGBgYAAAAA//8ajSQCYMCzEQMDAwAAAP//Go0kYsFAZSMGBgYAAAAA//8ajSR8YDBkIwYGBgAAAAD//xqNJKLAAGYjBgYGAAAAAP//Go0knGCgBoHQAAMDAwAAAP//Go0k7GCQFHQMDAwMDAwAAAAA//8ajSQCYMCzEQMDAwAAAP//Go0kLGBQZSMGBgYAAAAA//8ajSR8YDBkIwYGBgAAAAD//xqNJHQw2LIRAwMDAAAA//8ajSScYJBkIwYGBgAAAAD//xqNJBQwCLMRAwMDAAAA//8ajSTsYPBkIwYGBgAAAAD//xqNJAQYnNmIgYEBAAAA//8ajSQsYFBlIwYGBgAAAAD//xqNJCgYPINAaICBgQEAAAD//xqNJBAYtAUdAwMDAwMDAAAA//8ajSQUMAizEQMDAwAAAP//Go2kwZ6NGBgYAAAAAP//Go0kBBic2YiBgQEAAAD//8J+jsO7d+/o7hIqAyEhIWIMHPzZiIGBAQAAAP//wnnYhr29PfGmHDx4kCT1tAYHDx4k1YZBm40YGBgAAAAA//+itLi7e/culVwyAGBIZCMGBgYAAAAA//+iKJLu3r3r1mU0pOMJAgZzNmJgYAAAAAD//yI/kiAxhEuWEQyIESQbUGjaUMlGDAwMAAAAAP//IjOS4DG0q+ycsrIykbr+gwF5NqIBKkb2IM9GDAwMAAAAAP//IueULvJiCB6ykHhCC2XkyEOWwhWp////p0o2GvwxxMDAAAAAAP//IjknkR1DWAE8b8FDHB6RWOOSKmAIFXQMDAwMDAwAAAAA//8iLSdRN4bwAFrEDSYYEtmIgYEBAAAA//8iIZLoFkN4SjnKwZDLRgwMDAAAAAD//yK2uKNnDCED2mWpoZKNGBgYAAAAAP//IionUdhSgAAiMwekRQDXiEsXch1GfLYbitmIgYEBAAAA//8iobgjtbWNXxAXm8jopLA8HELZiIGBAQAAAP//Iqq4U1ZWpnMpRwswRLMRAwMDAAAA//8itk4a6jGEDIZWNmJgYAAAAAD//8JZ3JE6kEzGwDM9wdDNRgwMDAAAAAD//8IeSUROxtAIHDx4sKGhIS0tLTIykuo2DLlsxMDAAAAAAP//GqRHTj99+rS4uFhOTq6hoYGLi4tC04bWIBAaYGBgAAAAAP//GqTT59LS0osWLeLh4YmKiqJwKmRIF3QMDAwMDAwAAAAA//8avGsc2NjY6urqksFg+/btlBs4RLMRAwMDAAAA//8a7HdV+Pr6amhoFBUVnT9/vrS0lJWVlSTtwyAbMTAwAAAAAP//GgKrhVRVVZcvX/7mzZv4+Pjnz5+TZ8jQzUYMDAwAAAAA//8aGku6eHh4+vr6PD09o6Ojjx49SqSu4ZGNGBgYAAAAAP//GkpX88TGxuro6JSXlwcEBGRkZDAxEZvChnQ2YmBgAAAAAP//GmKLIw0NDVesWHH+/PnMzMz379/jUTlsshEDAwMAAAD//xp6K1iFhIRmzpypo6MTERFx8eJFguqHejZiYGAAAAAA//8aksuMmZiYcnNzq6urCwsLly5diqlgOGUjBgYGAAAAAP//GsLXxdnZ2S1ZsqS4uPjChQsNDQ3c3Nxv377dvXv3q1evQHMZX38xcrMNg2zEwMAAAAAA//8a8jeR/fr1q6ur6/Tp0yEhIQsWLLC3t1+zZg27l+bvC0//Pfs0DGKIgYEBAAAA//8aJtfFzZo1a8aMGRs2bPDx8YEUdH8uPf8YvezAgQMDO1hMOWBgYAAAAAD//xomW1/u3LlTU1MjJycHF/kYvSw+Pn716tUD6i4qAAYGBgAAAAD//xomkXTjxg0DAwO09oK+vv7169cH1F1UAAwMDAAAAAD//xomkcTLy/vp0yc4F9Je+PDhAx8f34C6iwqAgYEBAAAA//8aJpHk6uoaFxeHnI3+/v27bt06Nze3AXUXFQADAwMAAAD//xomkRQVFcXAwPC1de+/l5/f6vZu2LChoKBAWVnZ2tp6ELiOIsDAwAAAAAD//xomrTs9PT2h03nfZ5z4uf7Kv3ffpKWlo6Ojo6KiiB/fG7SAgYEBAAAA//8aPnefM3KwchXYfp976ty5cywsw8dfDAwMAAAAAP//Gg4JDa1RN8xiiIGBAQAAAP//GlZHBAyPQSA0wMDAAAAAAP//GvKRNNRXAhEEDAwMAAAAAP//GtqRNMxGu7ECBgYGAAAAAP//GibF3TDORgwMDAAAAAD//xrCkTRCshEDAwMAAAD//xoOOWl4ZyMGBgYAAAAA//8aqpE0crIRAwMDAAAA//8a8jlp2GcjBgYGAAAAAP//GpKRNKKyEQMDAwAAAP//Gto5aSRkIwYGBgAAAAD//xp6kTTSshEDAwMAAAD//xrCOWmEZCMGBgYAAAAA//8aYpE0EgaB0AADAwMAAAD//xpKkTQCCzoGBgYGBgYAAAAA//8aksXdiMpGDAwMAAAAAP//GjKRNGKzEQMDAwAAAP//Gno5aaRlIwYGBgAAAAD//xoakTSSsxEDAwMAAAD//xpiOWkEZiMGBgYAAAAA//8aApE0wrMRAwMDAAAA//8aSjlpZGYjBgYGAAAAAP//GuyRNOKzEQMDAwMAAAD//xoyOWnEZiMGBgYAAAAA//8a1JE0MgeB0AADAwMAAAD//xq8kTRa0EEAAwMDAAAA//8aAsXdCM9GDAwMAAAAAP//GqSRNJqN4ICBgQEAAAD//xrsOWnEZyMGBgYGAAAAAP//GoyRNJqNkAEDAwMAAAD//xrUOWk0GzEwMDAwMAAAAAD//xp0kTSajdAAAwMDAAAA//8avDlpNBtBAAMDAwAAAP//GlyRNJqNMAEDAwMAAAD//xqkOWk0G8EBAwMDAAAA//8aRJE0OgiEFTAwMAAAAAD//xoskTRa0OECDAwMAAAAAP//GnTF3Wg2QgMMDAwAAAAA//8aFJE0mo3wAAYGBgAAAAD//xpcOWk0G2ECBgYGAAAAAP//GvhIGs1G+AEDAwMAAAD//xpEOWk0G2EFDAwMAAAAAP//GuBIGs1GBAEDAwMAAAD//xosOWk0G+ECDAwMAAAAAP//GshIGs1GxAAGBgYAAAAA//8aFDlpNBvhAQwMDAAAAAD//xqwSBodBCISMDAwAAAAAP//GphIGi3oiAcMDAwAAAAA//8a4OJuNBsRBAwMDAAAAAD//xqASBrNRiQBBgYGAAAAAP//GsicNJqNiAEMDAwAAAAA//+idySNZiNSAQMDAwAAAP//GrCcNJqNiAQMDAwAAAAA//+iaySNZiMyAAMDAwAAAP//GpicNJqNiAcMDAwAAAAA//+iXySNZiPyAAMDAwAAAP//GoCcNJqNSAIMDAwAAAAA//+iUySNDgKRDRgYGAAAAAD//6JHJI0WdJQABgYGAAAAAP//omtxN5qNyAAMDAwAAAAA//+ieSSNZiMKAQMDAwAAAP//ol9OGs1G5AEGBgYAAAAA//+ibSSNZiPKAQMDAwAAAP//olNOGs1GZAMGBgYAAAAA//+iYSSNZiOqAAYGBgAAAAD//6JHThrNRpQABgYGAAAAAP//olUkjWYjagEGBgYAAAAA//+ieU4azUYUAgYGBgAAAAD//6JJJI0OAlERMDAwAAAAAP//on4kjRZ01AUMDAwAAAAA//+iYXE3mo2oAhgYGAAAAAD//6JyJI1mI6oDBgYGAAAAAP//on5OeqvbO5qNqAgYGBgAAAAA//+i8r25kIjR09UbWF8NJ8DAwAAAAAD//xomd58PY8DAwAAAAAD//xpWNzYPS8DAwAAAAAD//xqNpMEOGBgYAAAAAP//Go2kwQ4YGBgAAAAA//8ajaTBDhgYGAAAAAD//wMASJJB4JtH7IUAAAAASUVORK5CYII=",
+ "file_name": "Y:/gomServiceArea/DokumentationDerDialoge/widgetDescription/LineForDialogImage.png",
+ "height": 140,
+ "keep_aspect": True,
+ "keep_original_size": True,
+ "name": "image",
+ "rows": 6,
+ "system_image": "system_message_warning",
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "image",
+ "use_system_image": False,
+ "width": 140
+ },
+ {
+ "columns": 2,
+ "name": "parametersSeparator",
+ "rows": 1,
+ "title": {
+ "id": "",
+ "text": "Parameters",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "separator"
+ },
+ {
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 1,
+ "name": "nameLabel",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Name:",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "label",
+ "word_wrap": False
+ },
+ {
+ "columns": 1,
+ "name": "name",
+ "password": False,
+ "read_only": False,
+ "rows": 1,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "input::string",
+ "value": ""
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 2,
+ "name": "pointsSeparator",
+ "rows": 1,
+ "title": {
+ "id": "",
+ "text": "Points",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "separator"
+ },
+ {
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 1,
+ "name": "point1Label",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Point 1",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "label",
+ "word_wrap": False
+ },
+ {
+ "columns": 1,
+ "fast_filter": False,
+ "name": "point1",
+ "rows": 1,
+ "supplier": "any",
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "input::point3d"
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 1,
+ "name": "point2Label",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Point 2",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "label",
+ "word_wrap": False
+ },
+ {
+ "columns": 1,
+ "fast_filter": False,
+ "name": "point2",
+ "rows": 1,
+ "supplier": "any",
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "input::point3d"
+ }
+ ],
+ [
+ {
+ },
+ {
+ "columns": 2,
+ "maximum_size": -1,
+ "minimum_size": 0,
+ "name": "spacer",
+ "rows": 1,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "spacer::vertical"
+ },
+ {
+ }
+ ]
+ ],
+ "control": {
+ "id": "OkCancel"
+ },
+ "embedding": "always_toplevel",
+ "position": "automatic",
+ "size": {
+ "height": 291,
+ "width": 434
+ },
+ "sizemode": "automatic",
+ "style": "Standard",
+ "title": {
+ "id": "",
+ "text": "Line from two points",
+ "translatable": True
+ }
+})
+
+# Handler function registered to the dialog
+def handler_function (widget):
+ # Print information about the modified widget
+ print ("Modified:", str (widget))
+ # If the 'name' widget is empty, the 'ok' button is disabled.
+ if DIALOG.name.value == "":
+ DIALOG.control.ok.enabled = False
+ else :
+ DIALOG.control.ok.enabled = True
+
+ if str(widget) == 'system':
+ print("It is a global event.")
+ elif str(widget) == 'initialize':
+ print("Dialog is displayed for the first time.")
+
+# Register dialog handler
+DIALOG.handler = handler_function
+# Execute dialog
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+
+# Print content of the 'name' widget
+print( RESULT.name )
+# output: Line 1
+
+# Print content of the widget named 'point1'. This can again be an element reference.
+print( RESULT.point1 )
+# output: gom.app.project.actual_elements['Point 5']
+
+# Print content of the widget named 'point2'.
+print( RESULT.point2 )
+# output: gom.app.project.actual_elements['Point 6']
+
+# construct a line with the user input. Therefore our dialog works similar to the 2-point Line
+# construction dialog
+MCAD_ELEMENT=gom.script.primitive.create_line_by_2_points (
+ name= RESULT.name,
+ point1 = RESULT.point1,
+ point2 = RESULT.point2
+)
diff --git a/2022-new-headings-intros/_images/after_installation.png b/2022-new-headings-intros/_images/after_installation.png
new file mode 100644
index 0000000..8e2a439
Binary files /dev/null and b/2022-new-headings-intros/_images/after_installation.png differ
diff --git a/2022-new-headings-intros/_images/built-in_progressbar.png b/2022-new-headings-intros/_images/built-in_progressbar.png
new file mode 100644
index 0000000..88793cf
Binary files /dev/null and b/2022-new-headings-intros/_images/built-in_progressbar.png differ
diff --git a/2022-new-headings-intros/_images/check_results_data_array.jpg b/2022-new-headings-intros/_images/check_results_data_array.jpg
new file mode 100644
index 0000000..40fd8af
Binary files /dev/null and b/2022-new-headings-intros/_images/check_results_data_array.jpg differ
diff --git a/2022-new-headings-intros/_images/configuring_widgets.png b/2022-new-headings-intros/_images/configuring_widgets.png
new file mode 100644
index 0000000..7166e0c
Binary files /dev/null and b/2022-new-headings-intros/_images/configuring_widgets.png differ
diff --git a/2022-new-headings-intros/_images/connecting1.png b/2022-new-headings-intros/_images/connecting1.png
new file mode 100644
index 0000000..47dde58
Binary files /dev/null and b/2022-new-headings-intros/_images/connecting1.png differ
diff --git a/2022-new-headings-intros/_images/connecting2.png b/2022-new-headings-intros/_images/connecting2.png
new file mode 100644
index 0000000..8c6bca7
Binary files /dev/null and b/2022-new-headings-intros/_images/connecting2.png differ
diff --git a/2022-new-headings-intros/_images/control_widget_status_label.png b/2022-new-headings-intros/_images/control_widget_status_label.png
new file mode 100644
index 0000000..d4dfaaf
Binary files /dev/null and b/2022-new-headings-intros/_images/control_widget_status_label.png differ
diff --git a/2022-new-headings-intros/_images/convert_base64_dialog.png b/2022-new-headings-intros/_images/convert_base64_dialog.png
new file mode 100644
index 0000000..5c566b5
Binary files /dev/null and b/2022-new-headings-intros/_images/convert_base64_dialog.png differ
diff --git a/2022-new-headings-intros/_images/create_package.png b/2022-new-headings-intros/_images/create_package.png
new file mode 100644
index 0000000..6f4cdae
Binary files /dev/null and b/2022-new-headings-intros/_images/create_package.png differ
diff --git a/2022-new-headings-intros/_images/creating_an_environment.gif b/2022-new-headings-intros/_images/creating_an_environment.gif
new file mode 100644
index 0000000..8cc6a55
Binary files /dev/null and b/2022-new-headings-intros/_images/creating_an_environment.gif differ
diff --git a/2022-new-headings-intros/_images/debugging1.png b/2022-new-headings-intros/_images/debugging1.png
new file mode 100644
index 0000000..b76b11e
Binary files /dev/null and b/2022-new-headings-intros/_images/debugging1.png differ
diff --git a/2022-new-headings-intros/_images/debugging2.png b/2022-new-headings-intros/_images/debugging2.png
new file mode 100644
index 0000000..fd07cb3
Binary files /dev/null and b/2022-new-headings-intros/_images/debugging2.png differ
diff --git a/2022-new-headings-intros/_images/debugging3.png b/2022-new-headings-intros/_images/debugging3.png
new file mode 100644
index 0000000..61980ad
Binary files /dev/null and b/2022-new-headings-intros/_images/debugging3.png differ
diff --git a/2022-new-headings-intros/_images/dialog1.png b/2022-new-headings-intros/_images/dialog1.png
new file mode 100644
index 0000000..7d7d18b
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog1.png differ
diff --git a/2022-new-headings-intros/_images/dialog1_break.png b/2022-new-headings-intros/_images/dialog1_break.png
new file mode 100644
index 0000000..fc4872f
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog1_break.png differ
diff --git a/2022-new-headings-intros/_images/dialog2_extendable_break.png b/2022-new-headings-intros/_images/dialog2_extendable_break.png
new file mode 100644
index 0000000..c48ce44
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog2_extendable_break.png differ
diff --git a/2022-new-headings-intros/_images/dialog3_info.png b/2022-new-headings-intros/_images/dialog3_info.png
new file mode 100644
index 0000000..4b16d49
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog3_info.png differ
diff --git a/2022-new-headings-intros/_images/dialog_editing_1.png b/2022-new-headings-intros/_images/dialog_editing_1.png
new file mode 100644
index 0000000..136259a
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog_editing_1.png differ
diff --git a/2022-new-headings-intros/_images/dialog_editing_2.png b/2022-new-headings-intros/_images/dialog_editing_2.png
new file mode 100644
index 0000000..c0e2577
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog_editing_2.png differ
diff --git a/2022-new-headings-intros/_images/dialog_editor.png b/2022-new-headings-intros/_images/dialog_editor.png
new file mode 100644
index 0000000..0069514
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog_editor.png differ
diff --git a/2022-new-headings-intros/_images/dialog_reopen_example.jpg b/2022-new-headings-intros/_images/dialog_reopen_example.jpg
new file mode 100644
index 0000000..cc0d76f
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog_reopen_example.jpg differ
diff --git a/2022-new-headings-intros/_images/dialog_template.png b/2022-new-headings-intros/_images/dialog_template.png
new file mode 100644
index 0000000..b7de698
Binary files /dev/null and b/2022-new-headings-intros/_images/dialog_template.png differ
diff --git a/2022-new-headings-intros/_images/dropdown_widget.jpg b/2022-new-headings-intros/_images/dropdown_widget.jpg
new file mode 100644
index 0000000..af5f740
Binary files /dev/null and b/2022-new-headings-intros/_images/dropdown_widget.jpg differ
diff --git a/2022-new-headings-intros/_images/edit_mode.png b/2022-new-headings-intros/_images/edit_mode.png
new file mode 100644
index 0000000..098ecaa
Binary files /dev/null and b/2022-new-headings-intros/_images/edit_mode.png differ
diff --git a/2022-new-headings-intros/_images/edit_package.gif b/2022-new-headings-intros/_images/edit_package.gif
new file mode 100644
index 0000000..3fb0fc3
Binary files /dev/null and b/2022-new-headings-intros/_images/edit_package.gif differ
diff --git a/2022-new-headings-intros/_images/edit_package.png b/2022-new-headings-intros/_images/edit_package.png
new file mode 100644
index 0000000..093be45
Binary files /dev/null and b/2022-new-headings-intros/_images/edit_package.png differ
diff --git a/2022-new-headings-intros/_images/edit_text.png b/2022-new-headings-intros/_images/edit_text.png
new file mode 100644
index 0000000..31e1563
Binary files /dev/null and b/2022-new-headings-intros/_images/edit_text.png differ
diff --git a/2022-new-headings-intros/_images/editing1.png b/2022-new-headings-intros/_images/editing1.png
new file mode 100644
index 0000000..2539084
Binary files /dev/null and b/2022-new-headings-intros/_images/editing1.png differ
diff --git a/2022-new-headings-intros/_images/editing2.png b/2022-new-headings-intros/_images/editing2.png
new file mode 100644
index 0000000..1b423f2
Binary files /dev/null and b/2022-new-headings-intros/_images/editing2.png differ
diff --git a/2022-new-headings-intros/_images/event_handler_script_launcher.png b/2022-new-headings-intros/_images/event_handler_script_launcher.png
new file mode 100644
index 0000000..d02b08a
Binary files /dev/null and b/2022-new-headings-intros/_images/event_handler_script_launcher.png differ
diff --git a/2022-new-headings-intros/_images/event_handler_timer_edit.png b/2022-new-headings-intros/_images/event_handler_timer_edit.png
new file mode 100644
index 0000000..764f0dc
Binary files /dev/null and b/2022-new-headings-intros/_images/event_handler_timer_edit.png differ
diff --git a/2022-new-headings-intros/_images/explorer.png b/2022-new-headings-intros/_images/explorer.png
new file mode 100644
index 0000000..91e767f
Binary files /dev/null and b/2022-new-headings-intros/_images/explorer.png differ
diff --git a/2022-new-headings-intros/_images/explorer_selected_elements_in_dialog.jpg b/2022-new-headings-intros/_images/explorer_selected_elements_in_dialog.jpg
new file mode 100644
index 0000000..d82af34
Binary files /dev/null and b/2022-new-headings-intros/_images/explorer_selected_elements_in_dialog.jpg differ
diff --git a/2022-new-headings-intros/_images/explorer_selected_elements_script_explorer.jpg b/2022-new-headings-intros/_images/explorer_selected_elements_script_explorer.jpg
new file mode 100644
index 0000000..a8bb47a
Binary files /dev/null and b/2022-new-headings-intros/_images/explorer_selected_elements_script_explorer.jpg differ
diff --git a/2022-new-headings-intros/_images/extension.png b/2022-new-headings-intros/_images/extension.png
new file mode 100644
index 0000000..8382c83
Binary files /dev/null and b/2022-new-headings-intros/_images/extension.png differ
diff --git a/2022-new-headings-intros/_images/file_structure.jpg b/2022-new-headings-intros/_images/file_structure.jpg
new file mode 100644
index 0000000..015e1d4
Binary files /dev/null and b/2022-new-headings-intros/_images/file_structure.jpg differ
diff --git a/2022-new-headings-intros/_images/go_to_create_package.png b/2022-new-headings-intros/_images/go_to_create_package.png
new file mode 100644
index 0000000..14af68a
Binary files /dev/null and b/2022-new-headings-intros/_images/go_to_create_package.png differ
diff --git a/2022-new-headings-intros/_images/icon_guideline.png b/2022-new-headings-intros/_images/icon_guideline.png
new file mode 100644
index 0000000..a03a45c
Binary files /dev/null and b/2022-new-headings-intros/_images/icon_guideline.png differ
diff --git a/2022-new-headings-intros/_images/import_script_resource.jpg b/2022-new-headings-intros/_images/import_script_resource.jpg
new file mode 100644
index 0000000..7cf39fd
Binary files /dev/null and b/2022-new-headings-intros/_images/import_script_resource.jpg differ
diff --git a/2022-new-headings-intros/_images/in_package_manager.png b/2022-new-headings-intros/_images/in_package_manager.png
new file mode 100644
index 0000000..3b2c54b
Binary files /dev/null and b/2022-new-headings-intros/_images/in_package_manager.png differ
diff --git a/2022-new-headings-intros/_images/insert_dialog.png b/2022-new-headings-intros/_images/insert_dialog.png
new file mode 100644
index 0000000..0d9f5ca
Binary files /dev/null and b/2022-new-headings-intros/_images/insert_dialog.png differ
diff --git a/2022-new-headings-intros/_images/inserting_elements.png b/2022-new-headings-intros/_images/inserting_elements.png
new file mode 100644
index 0000000..77aa68e
Binary files /dev/null and b/2022-new-headings-intros/_images/inserting_elements.png differ
diff --git a/2022-new-headings-intros/_images/inserting_keywords.png b/2022-new-headings-intros/_images/inserting_keywords.png
new file mode 100644
index 0000000..856f8ef
Binary files /dev/null and b/2022-new-headings-intros/_images/inserting_keywords.png differ
diff --git a/2022-new-headings-intros/_images/install_python_package_from_local.png b/2022-new-headings-intros/_images/install_python_package_from_local.png
new file mode 100644
index 0000000..bacf80f
Binary files /dev/null and b/2022-new-headings-intros/_images/install_python_package_from_local.png differ
diff --git a/2022-new-headings-intros/_images/install_python_package_from_network.png b/2022-new-headings-intros/_images/install_python_package_from_network.png
new file mode 100644
index 0000000..0e860c7
Binary files /dev/null and b/2022-new-headings-intros/_images/install_python_package_from_network.png differ
diff --git a/2022-new-headings-intros/_images/keyword_list_1.png b/2022-new-headings-intros/_images/keyword_list_1.png
new file mode 100644
index 0000000..dcee829
Binary files /dev/null and b/2022-new-headings-intros/_images/keyword_list_1.png differ
diff --git a/2022-new-headings-intros/_images/keyword_list_2.png b/2022-new-headings-intros/_images/keyword_list_2.png
new file mode 100644
index 0000000..d1bab9b
Binary files /dev/null and b/2022-new-headings-intros/_images/keyword_list_2.png differ
diff --git a/2022-new-headings-intros/_images/language_preferences.png b/2022-new-headings-intros/_images/language_preferences.png
new file mode 100644
index 0000000..1038f3f
Binary files /dev/null and b/2022-new-headings-intros/_images/language_preferences.png differ
diff --git a/2022-new-headings-intros/_images/menu_icon_darkbg.jpg b/2022-new-headings-intros/_images/menu_icon_darkbg.jpg
new file mode 100644
index 0000000..bbb2e38
Binary files /dev/null and b/2022-new-headings-intros/_images/menu_icon_darkbg.jpg differ
diff --git a/2022-new-headings-intros/_images/menu_icon_lightbg.jpg b/2022-new-headings-intros/_images/menu_icon_lightbg.jpg
new file mode 100644
index 0000000..c6c225b
Binary files /dev/null and b/2022-new-headings-intros/_images/menu_icon_lightbg.jpg differ
diff --git a/2022-new-headings-intros/_images/merge_cells.png b/2022-new-headings-intros/_images/merge_cells.png
new file mode 100644
index 0000000..3965907
Binary files /dev/null and b/2022-new-headings-intros/_images/merge_cells.png differ
diff --git a/2022-new-headings-intros/_images/modules_json_file.png b/2022-new-headings-intros/_images/modules_json_file.png
new file mode 100644
index 0000000..741887d
Binary files /dev/null and b/2022-new-headings-intros/_images/modules_json_file.png differ
diff --git a/2022-new-headings-intros/_images/offset_point_creation_type.jpg b/2022-new-headings-intros/_images/offset_point_creation_type.jpg
new file mode 100644
index 0000000..3be2adb
Binary files /dev/null and b/2022-new-headings-intros/_images/offset_point_creation_type.jpg differ
diff --git a/2022-new-headings-intros/_images/offset_point_dialog.jpg b/2022-new-headings-intros/_images/offset_point_dialog.jpg
new file mode 100644
index 0000000..58bf51e
Binary files /dev/null and b/2022-new-headings-intros/_images/offset_point_dialog.jpg differ
diff --git a/2022-new-headings-intros/_images/offset_point_user_dialog.jpg b/2022-new-headings-intros/_images/offset_point_user_dialog.jpg
new file mode 100644
index 0000000..42647fa
Binary files /dev/null and b/2022-new-headings-intros/_images/offset_point_user_dialog.jpg differ
diff --git a/2022-new-headings-intros/_images/offset_point_v2.jpg b/2022-new-headings-intros/_images/offset_point_v2.jpg
new file mode 100644
index 0000000..0441259
Binary files /dev/null and b/2022-new-headings-intros/_images/offset_point_v2.jpg differ
diff --git a/2022-new-headings-intros/_images/package_dialog.png b/2022-new-headings-intros/_images/package_dialog.png
new file mode 100644
index 0000000..08bf01e
Binary files /dev/null and b/2022-new-headings-intros/_images/package_dialog.png differ
diff --git a/2022-new-headings-intros/_images/recording1.png b/2022-new-headings-intros/_images/recording1.png
new file mode 100644
index 0000000..c9cc96e
Binary files /dev/null and b/2022-new-headings-intros/_images/recording1.png differ
diff --git a/2022-new-headings-intros/_images/result1.png b/2022-new-headings-intros/_images/result1.png
new file mode 100644
index 0000000..490d1b3
Binary files /dev/null and b/2022-new-headings-intros/_images/result1.png differ
diff --git a/2022-new-headings-intros/_images/result2.png b/2022-new-headings-intros/_images/result2.png
new file mode 100644
index 0000000..d90dbd7
Binary files /dev/null and b/2022-new-headings-intros/_images/result2.png differ
diff --git a/2022-new-headings-intros/_images/script_editing_1.png b/2022-new-headings-intros/_images/script_editing_1.png
new file mode 100644
index 0000000..e088a53
Binary files /dev/null and b/2022-new-headings-intros/_images/script_editing_1.png differ
diff --git a/2022-new-headings-intros/_images/script_editor.png b/2022-new-headings-intros/_images/script_editor.png
new file mode 100644
index 0000000..b650398
Binary files /dev/null and b/2022-new-headings-intros/_images/script_editor.png differ
diff --git a/2022-new-headings-intros/_images/script_icon_from_file.jpg b/2022-new-headings-intros/_images/script_icon_from_file.jpg
new file mode 100644
index 0000000..30c0010
Binary files /dev/null and b/2022-new-headings-intros/_images/script_icon_from_file.jpg differ
diff --git a/2022-new-headings-intros/_images/script_object_explorer.jpg b/2022-new-headings-intros/_images/script_object_explorer.jpg
new file mode 100644
index 0000000..9131563
Binary files /dev/null and b/2022-new-headings-intros/_images/script_object_explorer.jpg differ
diff --git a/2022-new-headings-intros/_images/script_properties_dialog.png b/2022-new-headings-intros/_images/script_properties_dialog.png
new file mode 100644
index 0000000..4ef3d14
Binary files /dev/null and b/2022-new-headings-intros/_images/script_properties_dialog.png differ
diff --git a/2022-new-headings-intros/_images/script_resources.jpg b/2022-new-headings-intros/_images/script_resources.jpg
new file mode 100644
index 0000000..ef4dcfc
Binary files /dev/null and b/2022-new-headings-intros/_images/script_resources.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_actual_explorer.jpg b/2022-new-headings-intros/_images/scripted_actual_explorer.jpg
new file mode 100644
index 0000000..8d95cff
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_actual_explorer.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_check_widgets.jpg b/2022-new-headings-intros/_images/scripted_check_widgets.jpg
new file mode 100644
index 0000000..ba03409
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_check_widgets.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_curve_check.jpg b/2022-new-headings-intros/_images/scripted_curve_check.jpg
new file mode 100644
index 0000000..8c29309
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_curve_check.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_curve_check_cs.jpg b/2022-new-headings-intros/_images/scripted_curve_check_cs.jpg
new file mode 100644
index 0000000..14a129d
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_curve_check_cs.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_element_progress_computation.jpg b/2022-new-headings-intros/_images/scripted_element_progress_computation.jpg
new file mode 100644
index 0000000..9a0df20
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_element_progress_computation.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_element_progress_preview.jpg b/2022-new-headings-intros/_images/scripted_element_progress_preview.jpg
new file mode 100644
index 0000000..ebbb816
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_element_progress_preview.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_scalar_check.jpg b/2022-new-headings-intros/_images/scripted_scalar_check.jpg
new file mode 100644
index 0000000..218d66d
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_scalar_check.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_surface_check.jpg b/2022-new-headings-intros/_images/scripted_surface_check.jpg
new file mode 100644
index 0000000..b858d32
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_surface_check.jpg differ
diff --git a/2022-new-headings-intros/_images/scripted_surface_check_cs.jpg b/2022-new-headings-intros/_images/scripted_surface_check_cs.jpg
new file mode 100644
index 0000000..a2e4134
Binary files /dev/null and b/2022-new-headings-intros/_images/scripted_surface_check_cs.jpg differ
diff --git a/2022-new-headings-intros/_images/selected_cell.png b/2022-new-headings-intros/_images/selected_cell.png
new file mode 100644
index 0000000..8c62179
Binary files /dev/null and b/2022-new-headings-intros/_images/selected_cell.png differ
diff --git a/2022-new-headings-intros/_images/separator_line.png b/2022-new-headings-intros/_images/separator_line.png
new file mode 100644
index 0000000..a8883b6
Binary files /dev/null and b/2022-new-headings-intros/_images/separator_line.png differ
diff --git a/2022-new-headings-intros/_images/setup2.png b/2022-new-headings-intros/_images/setup2.png
new file mode 100644
index 0000000..9e24fd6
Binary files /dev/null and b/2022-new-headings-intros/_images/setup2.png differ
diff --git a/2022-new-headings-intros/_images/setup4.png b/2022-new-headings-intros/_images/setup4.png
new file mode 100644
index 0000000..444094c
Binary files /dev/null and b/2022-new-headings-intros/_images/setup4.png differ
diff --git a/2022-new-headings-intros/_images/spacer.png b/2022-new-headings-intros/_images/spacer.png
new file mode 100644
index 0000000..f368c36
Binary files /dev/null and b/2022-new-headings-intros/_images/spacer.png differ
diff --git a/2022-new-headings-intros/_images/split_cells_horizontally.png b/2022-new-headings-intros/_images/split_cells_horizontally.png
new file mode 100644
index 0000000..2b17ea5
Binary files /dev/null and b/2022-new-headings-intros/_images/split_cells_horizontally.png differ
diff --git a/2022-new-headings-intros/_images/split_cells_vertically.png b/2022-new-headings-intros/_images/split_cells_vertically.png
new file mode 100644
index 0000000..9861d4f
Binary files /dev/null and b/2022-new-headings-intros/_images/split_cells_vertically.png differ
diff --git a/2022-new-headings-intros/_images/start_from_menu.png b/2022-new-headings-intros/_images/start_from_menu.png
new file mode 100644
index 0000000..b23619d
Binary files /dev/null and b/2022-new-headings-intros/_images/start_from_menu.png differ
diff --git a/2022-new-headings-intros/_images/text_field.png b/2022-new-headings-intros/_images/text_field.png
new file mode 100644
index 0000000..2c22c65
Binary files /dev/null and b/2022-new-headings-intros/_images/text_field.png differ
diff --git a/2022-new-headings-intros/_images/toggle_recording_1.png b/2022-new-headings-intros/_images/toggle_recording_1.png
new file mode 100644
index 0000000..84177c4
Binary files /dev/null and b/2022-new-headings-intros/_images/toggle_recording_1.png differ
diff --git a/2022-new-headings-intros/_images/toggle_recording_2.png b/2022-new-headings-intros/_images/toggle_recording_2.png
new file mode 100644
index 0000000..6b48e63
Binary files /dev/null and b/2022-new-headings-intros/_images/toggle_recording_2.png differ
diff --git a/2022-new-headings-intros/_images/toggle_recording_3.png b/2022-new-headings-intros/_images/toggle_recording_3.png
new file mode 100644
index 0000000..2f0b4a8
Binary files /dev/null and b/2022-new-headings-intros/_images/toggle_recording_3.png differ
diff --git a/2022-new-headings-intros/_images/trimesh_deform_mesh.jpg b/2022-new-headings-intros/_images/trimesh_deform_mesh.jpg
new file mode 100644
index 0000000..c846a5f
Binary files /dev/null and b/2022-new-headings-intros/_images/trimesh_deform_mesh.jpg differ
diff --git a/2022-new-headings-intros/_images/trimesh_deform_mesh_dialog.jpg b/2022-new-headings-intros/_images/trimesh_deform_mesh_dialog.jpg
new file mode 100644
index 0000000..b517b34
Binary files /dev/null and b/2022-new-headings-intros/_images/trimesh_deform_mesh_dialog.jpg differ
diff --git a/2022-new-headings-intros/_images/uninstallation.gif b/2022-new-headings-intros/_images/uninstallation.gif
new file mode 100644
index 0000000..7c74d76
Binary files /dev/null and b/2022-new-headings-intros/_images/uninstallation.gif differ
diff --git a/2022-new-headings-intros/_images/unit_dialog_event_handler.jpg b/2022-new-headings-intros/_images/unit_dialog_event_handler.jpg
new file mode 100644
index 0000000..dff17ff
Binary files /dev/null and b/2022-new-headings-intros/_images/unit_dialog_event_handler.jpg differ
diff --git a/2022-new-headings-intros/_images/update_xliff.png b/2022-new-headings-intros/_images/update_xliff.png
new file mode 100644
index 0000000..c5be5ce
Binary files /dev/null and b/2022-new-headings-intros/_images/update_xliff.png differ
diff --git a/2022-new-headings-intros/_images/user_defined_tokens-1.png b/2022-new-headings-intros/_images/user_defined_tokens-1.png
new file mode 100644
index 0000000..d4a19ec
Binary files /dev/null and b/2022-new-headings-intros/_images/user_defined_tokens-1.png differ
diff --git a/2022-new-headings-intros/_images/user_defined_tokens-2.png b/2022-new-headings-intros/_images/user_defined_tokens-2.png
new file mode 100644
index 0000000..8ea94da
Binary files /dev/null and b/2022-new-headings-intros/_images/user_defined_tokens-2.png differ
diff --git a/2022-new-headings-intros/_images/userdialog1.png b/2022-new-headings-intros/_images/userdialog1.png
new file mode 100644
index 0000000..63a3121
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog1.png differ
diff --git a/2022-new-headings-intros/_images/userdialog2.png b/2022-new-headings-intros/_images/userdialog2.png
new file mode 100644
index 0000000..8dc980d
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog2.png differ
diff --git a/2022-new-headings-intros/_images/userdialog3.png b/2022-new-headings-intros/_images/userdialog3.png
new file mode 100644
index 0000000..c61ea83
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog3.png differ
diff --git a/2022-new-headings-intros/_images/userdialog4.png b/2022-new-headings-intros/_images/userdialog4.png
new file mode 100644
index 0000000..e3636fb
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog4.png differ
diff --git a/2022-new-headings-intros/_images/userdialog5.png b/2022-new-headings-intros/_images/userdialog5.png
new file mode 100644
index 0000000..88e01f4
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog5.png differ
diff --git a/2022-new-headings-intros/_images/userdialog6.png b/2022-new-headings-intros/_images/userdialog6.png
new file mode 100644
index 0000000..eef3327
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog6.png differ
diff --git a/2022-new-headings-intros/_images/userdialog7.png b/2022-new-headings-intros/_images/userdialog7.png
new file mode 100644
index 0000000..d043032
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog7.png differ
diff --git a/2022-new-headings-intros/_images/userdialog8.png b/2022-new-headings-intros/_images/userdialog8.png
new file mode 100644
index 0000000..cbe77dd
Binary files /dev/null and b/2022-new-headings-intros/_images/userdialog8.png differ
diff --git a/2022-new-headings-intros/_images/volume_section_image.jpg b/2022-new-headings-intros/_images/volume_section_image.jpg
new file mode 100644
index 0000000..fb0c4f9
Binary files /dev/null and b/2022-new-headings-intros/_images/volume_section_image.jpg differ
diff --git a/2022-new-headings-intros/_images/widget_abort_disabled.png b/2022-new-headings-intros/_images/widget_abort_disabled.png
new file mode 100644
index 0000000..f3e9ab6
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_abort_disabled.png differ
diff --git a/2022-new-headings-intros/_images/widget_button_off.png b/2022-new-headings-intros/_images/widget_button_off.png
new file mode 100644
index 0000000..ee9e559
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_button_off.png differ
diff --git a/2022-new-headings-intros/_images/widget_button_on.png b/2022-new-headings-intros/_images/widget_button_on.png
new file mode 100644
index 0000000..8fa8fff
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_button_on.png differ
diff --git a/2022-new-headings-intros/_images/widget_checkbox.png b/2022-new-headings-intros/_images/widget_checkbox.png
new file mode 100644
index 0000000..a3d46a7
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_checkbox.png differ
diff --git a/2022-new-headings-intros/_images/widget_color.png b/2022-new-headings-intros/_images/widget_color.png
new file mode 100644
index 0000000..9c892b5
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_color.png differ
diff --git a/2022-new-headings-intros/_images/widget_date.png b/2022-new-headings-intros/_images/widget_date.png
new file mode 100644
index 0000000..e94bde0
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_date.png differ
diff --git a/2022-new-headings-intros/_images/widget_decimal.png b/2022-new-headings-intros/_images/widget_decimal.png
new file mode 100644
index 0000000..3dd3012
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_decimal.png differ
diff --git a/2022-new-headings-intros/_images/widget_element_name.png b/2022-new-headings-intros/_images/widget_element_name.png
new file mode 100644
index 0000000..0da6c5e
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_element_name.png differ
diff --git a/2022-new-headings-intros/_images/widget_file.png b/2022-new-headings-intros/_images/widget_file.png
new file mode 100644
index 0000000..413f674
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_file.png differ
diff --git a/2022-new-headings-intros/_images/widget_fsbrowser.png b/2022-new-headings-intros/_images/widget_fsbrowser.png
new file mode 100644
index 0000000..9fe2c6b
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_fsbrowser.png differ
diff --git a/2022-new-headings-intros/_images/widget_image.png b/2022-new-headings-intros/_images/widget_image.png
new file mode 100644
index 0000000..b97a9d4
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_image.png differ
diff --git a/2022-new-headings-intros/_images/widget_integer.png b/2022-new-headings-intros/_images/widget_integer.png
new file mode 100644
index 0000000..0f95644
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_integer.png differ
diff --git a/2022-new-headings-intros/_images/widget_label.png b/2022-new-headings-intros/_images/widget_label.png
new file mode 100644
index 0000000..e55943c
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_label.png differ
diff --git a/2022-new-headings-intros/_images/widget_list_selection.png b/2022-new-headings-intros/_images/widget_list_selection.png
new file mode 100644
index 0000000..2df11a2
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_list_selection.png differ
diff --git a/2022-new-headings-intros/_images/widget_log.png b/2022-new-headings-intros/_images/widget_log.png
new file mode 100644
index 0000000..87aa326
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_log.png differ
diff --git a/2022-new-headings-intros/_images/widget_progressbar.png b/2022-new-headings-intros/_images/widget_progressbar.png
new file mode 100644
index 0000000..c6d2b62
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_progressbar.png differ
diff --git a/2022-new-headings-intros/_images/widget_radiobutton.png b/2022-new-headings-intros/_images/widget_radiobutton.png
new file mode 100644
index 0000000..e8773e5
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_radiobutton.png differ
diff --git a/2022-new-headings-intros/_images/widget_selection_element.png b/2022-new-headings-intros/_images/widget_selection_element.png
new file mode 100644
index 0000000..7dc98c4
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_selection_element.png differ
diff --git a/2022-new-headings-intros/_images/widget_slider.png b/2022-new-headings-intros/_images/widget_slider.png
new file mode 100644
index 0000000..07ea9dc
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_slider.png differ
diff --git a/2022-new-headings-intros/_images/widget_text.png b/2022-new-headings-intros/_images/widget_text.png
new file mode 100644
index 0000000..4a1c85a
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text.png differ
diff --git a/2022-new-headings-intros/_images/widget_text_entry.png b/2022-new-headings-intros/_images/widget_text_entry.png
new file mode 100644
index 0000000..69fb2b0
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text_entry.png differ
diff --git a/2022-new-headings-intros/_images/widget_text_insert_expression1.png b/2022-new-headings-intros/_images/widget_text_insert_expression1.png
new file mode 100644
index 0000000..6392d80
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text_insert_expression1.png differ
diff --git a/2022-new-headings-intros/_images/widget_text_insert_expression2.png b/2022-new-headings-intros/_images/widget_text_insert_expression2.png
new file mode 100644
index 0000000..65b2169
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text_insert_expression2.png differ
diff --git a/2022-new-headings-intros/_images/widget_text_insert_expression3.png b/2022-new-headings-intros/_images/widget_text_insert_expression3.png
new file mode 100644
index 0000000..d07a82a
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text_insert_expression3.png differ
diff --git a/2022-new-headings-intros/_images/widget_text_insert_expression4.png b/2022-new-headings-intros/_images/widget_text_insert_expression4.png
new file mode 100644
index 0000000..6cf9a14
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text_insert_expression4.png differ
diff --git a/2022-new-headings-intros/_images/widget_text_insert_expression6.png b/2022-new-headings-intros/_images/widget_text_insert_expression6.png
new file mode 100644
index 0000000..088778e
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_text_insert_expression6.png differ
diff --git a/2022-new-headings-intros/_images/widget_tolerances.png b/2022-new-headings-intros/_images/widget_tolerances.png
new file mode 100644
index 0000000..139a497
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_tolerances.png differ
diff --git a/2022-new-headings-intros/_images/widget_unit.png b/2022-new-headings-intros/_images/widget_unit.png
new file mode 100644
index 0000000..0f472e0
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_unit.png differ
diff --git a/2022-new-headings-intros/_images/widget_visibility_off.jpg b/2022-new-headings-intros/_images/widget_visibility_off.jpg
new file mode 100644
index 0000000..52a2f67
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_visibility_off.jpg differ
diff --git a/2022-new-headings-intros/_images/widget_visibility_on.jpg b/2022-new-headings-intros/_images/widget_visibility_on.jpg
new file mode 100644
index 0000000..eb405e4
Binary files /dev/null and b/2022-new-headings-intros/_images/widget_visibility_on.jpg differ
diff --git a/2022-new-headings-intros/_images/wizard.png b/2022-new-headings-intros/_images/wizard.png
new file mode 100644
index 0000000..7a7d70e
Binary files /dev/null and b/2022-new-headings-intros/_images/wizard.png differ
diff --git a/2022-new-headings-intros/_images/wizard_dialog_step_1.png b/2022-new-headings-intros/_images/wizard_dialog_step_1.png
new file mode 100644
index 0000000..908fe3e
Binary files /dev/null and b/2022-new-headings-intros/_images/wizard_dialog_step_1.png differ
diff --git a/2022-new-headings-intros/_images/wizard_dialog_step_2.png b/2022-new-headings-intros/_images/wizard_dialog_step_2.png
new file mode 100644
index 0000000..f0c4130
Binary files /dev/null and b/2022-new-headings-intros/_images/wizard_dialog_step_2.png differ
diff --git a/2022-new-headings-intros/_images/wizard_dialog_step_3.png b/2022-new-headings-intros/_images/wizard_dialog_step_3.png
new file mode 100644
index 0000000..1ae628a
Binary files /dev/null and b/2022-new-headings-intros/_images/wizard_dialog_step_3.png differ
diff --git a/2022-new-headings-intros/_images/wizard_dialog_step_4.png b/2022-new-headings-intros/_images/wizard_dialog_step_4.png
new file mode 100644
index 0000000..0a47d56
Binary files /dev/null and b/2022-new-headings-intros/_images/wizard_dialog_step_4.png differ
diff --git a/2022-new-headings-intros/_images/workspace1.png b/2022-new-headings-intros/_images/workspace1.png
new file mode 100644
index 0000000..20e1d1c
Binary files /dev/null and b/2022-new-headings-intros/_images/workspace1.png differ
diff --git a/2022-new-headings-intros/_images/workspace2.png b/2022-new-headings-intros/_images/workspace2.png
new file mode 100644
index 0000000..1985a6f
Binary files /dev/null and b/2022-new-headings-intros/_images/workspace2.png differ
diff --git a/2022-new-headings-intros/_images/workspace5.png b/2022-new-headings-intros/_images/workspace5.png
new file mode 100644
index 0000000..d6defcb
Binary files /dev/null and b/2022-new-headings-intros/_images/workspace5.png differ
diff --git a/2022-new-headings-intros/_images/workspace6.png b/2022-new-headings-intros/_images/workspace6.png
new file mode 100644
index 0000000..107cc4a
Binary files /dev/null and b/2022-new-headings-intros/_images/workspace6.png differ
diff --git a/2022-new-headings-intros/_images/workspace7.png b/2022-new-headings-intros/_images/workspace7.png
new file mode 100644
index 0000000..9255202
Binary files /dev/null and b/2022-new-headings-intros/_images/workspace7.png differ
diff --git a/2022-new-headings-intros/_images/xliff_files.png b/2022-new-headings-intros/_images/xliff_files.png
new file mode 100644
index 0000000..a6badd2
Binary files /dev/null and b/2022-new-headings-intros/_images/xliff_files.png differ
diff --git a/2022-new-headings-intros/_sources/howtos/adding_workspaces_to_packages/adding_workspaces_to_packages.md.txt b/2022-new-headings-intros/_sources/howtos/adding_workspaces_to_packages/adding_workspaces_to_packages.md.txt
new file mode 100644
index 0000000..f60f763
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/adding_workspaces_to_packages/adding_workspaces_to_packages.md.txt
@@ -0,0 +1,245 @@
+# Adding workspaces to add-ons
+
+> Abstract: An add-on can include a definition for a new workspace. 'Inspection' and 'Reporting' are examples for these workspaces. Although there is not UI based workspace editor yet, it is possible to create one nevertheless with some manual work.
+
+## Workspaces
+
+
+
+* Each GOM application does have a list of available workspace on the left side (1).
+* Which workspaces are available depends on the available licenses and the installed add-ons.
+* A workspace bundles commands etc. thematically. If, for example, the 'inspection' workspace is selected, the toolbar (2) and the view menu (3) above will show everything the user needs to inspect parts, while the 'report' workspace provides tool for report page creation.
+* An add-on can add its own workspace. The 'Blade CMM' add-on, for example will provide tools for 'Airfoil CMM data preparation' - a feature, which is packaged and not provided by default because it is rather special.
+
+## Adding workspaces to add-ons
+
+> There is no UI based workspace editor yet, but workspace definitions can be added manually.
+
+* An add-on is just a ZIP file with a different extension (.package) containing JSON based object definitions.
+* It can be unpacked, edited and packaged again with a new workspace definition.
+
+### Step 1: Unpack the add-on
+
+* Use the tool of your choice to unpack the add-on file.
+* We recommend 7-zip for that task, but every other zip tool will do the job, too.
+* If you want to perform these tasks often, you can register your ZIP tool in the Windows "Choose default apps by file type" settings. Then, instead of unpacking and packing the add-on again for each edit, you can fiddle with the add-on content directly from the ZIP tool:
+
+ 
+
+### Step 2: Edit the main package content file
+
+> The file package.json contains a listing of the add-on content
+
+* When editing the package.json file in an add-on, you will notice that all general add-on information is handled there.
+* Among data like name and description, the package.json file contains a list of "content objects".
+* Every content object in the package.json file
+ * is associated with an object_xxx.json file containing the content data and
+ * is tagged with a provider_id entry defining the content type.
+* In the example, the "Blade CMM" add-on adds a workspace
+ * named "Airfoil CMM Data Preparation"
+ * which exact definition is provided in the add-on file object_0.json
+ * among other content like 'import_templates' and 'scripts'.
+
+Example: package.json
+
+~~~
+{
+ "author": "Carl Zeiss GOM Metrology GmbH",
+ "description": "System package 'Airfoil CMM Data Preparation'",
+ "uuid": "cab03223-c3ca-4001-af23-23f6d07471cb",
+ ...
+ "content": [
+ {
+ "displayname": "Airfoil CMM Data Preparation",
+ "object": "object_0.json",
+ "provider_id": "workspace",
+ "resources": [],
+ "content_id": "711632f6-7444-4e66-bf21-00cdd153d535"
+ },
+ {
+ "displayname": "import_cmm_xml.py",
+ "object": "object_1.json",
+ "provider_id": "import_templates",
+ "resources": []
+ },
+ {
+ "displayname": "Blade CMM",
+ "object": "object_2.json",
+ "provider_id": "scripts",
+ "resources": [],
+ "content_id": ":cab03223-c3ca-4001-af23-23f6d07471cb.Blade_CMM"
+ }
+ ],
+...
+}
+~~~
+
+* So to add a workspace to your own add-on, add a new content entry to the add-ons package.json file like above.
+
+### Step 3: Add a workspace definition file
+
+> The object_xxx.json file contains the complete workspace definition
+
+* Add an appropriately named object definition file (object_0.json in the example above) containing the workspace definition
+
+**Example:** 'object_0.json' from the 'Blade CMM' add-on defining a workspace for airfoil CMM data preparation:
+
+~~~
+{
+ "name": "Airfoil CMM Data Preparation",
+ "uuid": "711632f6-7444-4e66-bf21-00cdd153d535",
+ "content": {
+ "color": [
+ 170,
+ 93,
+ 30
+ ],
+ "recalc_section": true,
+ "alignment_section": true,
+ "sort_index": "19",
+ "icon": "cmd_mode_eval_blade_cmm",
+ "workflow_commands": [
+ "sys.import_file",
+ "[separator]",
+ "userscript.Blade_CMM__ProjectSetup__Project_Setup",
+ "inspect.tb_create_blade_stylus_correction_cmd_group",
+ "primitive.create_fitting_plane_mp_none_draft",
+ "inspect.tb_create_profile_section_by_projection_cmd_group",
+ "[separator]",
+ "userscript.Blade_CMM__AutoPilot__AutoPilot"
+ ],
+ "default_visible_tabs": [
+ "diagram",
+ "section_view",
+ "table",
+ "pip"
+ ]
+ }
+}
+~~~
+
+#### "name"
+
+Workspace name as displayed in the workspaces tooltip.
+
+#### "uuid"
+
+A unique id which matches the "content id" field in the packages.json file.
+
+> Please do not define the UUID manually, but use a UUID generator like Online UUID Generator to generate a fresh, truly unique one !
+
+#### "color"
+
+RGB color of the workspace toolbar background. This default may be overwritten by themes, so e.g. in dark theme the toolbar will be colored in rgb(51,51,51) always.
+
+#### "recalc_section"
+
+True, if the toolbar should contain a section for recalculation commands
+
+#### "alignment_section"
+
+True, if the toolbar should contain a section for alignment commands.
+
+#### "sort_index"
+
+Position of that workspace in the list of workspace. The default (no value given) will add the workspace to the end of the workspace list, which is often fine.
+
+#### "icon"
+
+The internal name of the icon file.
+
+> It is currently possible only to select icons which are part of the GOM software distribution and which are not listed anywhere for the outside world. So this important field is of limited use now. But we will add a method to add custom icons just into that particular content definition file in the near future !
+
+In SW2022-0 and later only:
+
+* Choose an icon file in one of the widely supported formats (png, jpg, ...). We are using the Qt library functions to read image data, so you can have a look at the related Qt documentation to see the list of supported image formats.
+* Install add-on Workspace editor tools and use the script in Scripting / Tools / Workspace editor to create a base64 encoded file of this icons data:
+
+ 
+
+* Insert the resulting file content as a text item into the icon property:
+
+~~~
+{
+ "name": "Airfoil CMM Data Preparation",
+ "uuid": "711632f6-7444-4e66-bf21-00cdd153d535",
+ "content": {
+ ...
+ # The icon definition contains the content of the created encoding as string enclosed in '"'
+ "icon": "x8Royf4mIiJq8v3YBiIj6IRvW1yr6DhnwUw45R0RErxcr+kREALZDBZvXLgYREdGZHBx1h4iIiIiI...",
+ ...
+}
+~~~
+
+Some icon guidelines
+
+* Use only black/white icons to match with the overall application style
+ * Black color: HEX (#333333), RGB (51,51,51)
+ * White color: HEX (#FFFFFF), RGB (255,255,255)
+* Use image formats that support transparency (e.g. '.png')
+* Image size:
+ * preferably from 24x24 px (minimum, for script icons) to 64x64 px (recommended for workspace icons)
+ * Try NOT to use any form of compression
+* Set the workspace (and scripts) icons to look good on a bright background
+ * Normally, this means just a black icon with transparent background
+ * To look good on darker background you have two options:
+ 1. You put a bright (white) padding around the icon, so it is still visible on dark backgrounds
+ 2. You let the software automatically invert the icon to white color. The icons will get autobrightened, if the icon contains ONLY the standard black color (see above), and no bright colors (Lightness > 127)
+* Example
+
+ 
+
+ * (1) = Icon with padding, stays the same in all modes
+ * (2) = Icon in pure #333333 black, gets auto-brightened in dark modes
+
+#### "workflow_commands"
+
+Commands on the left side of the workspace toolbar. These command can either be
+* the name of a "hardcoded" GOM command,
+* the name of a script command (a command starting a python script)
+* a special tag like '[separator]' for a separator in the command toolbar.
+
+The command here will become entries in the toolbar from the left to the right. To get the name of the command, you can record it in the script editor and skip the 'gom.script' prefix:
+
+
+
+This works for scripts, too, if a script is executed from the 'Scripts' menu while the script editor is in recording mode.
+
+#### "sensor_commands"
+
+Commands on the right side of the workspace toolbar. Same principle as above.
+
+#### "default_visible_views"
+
+Views that are visible per default, e.g. adding "right_docking_area" shows the properties/toolbox window(star) on right side, which is collapsed by default. ( (star) as long as the default_view_layout_right_ isn't changed). To investigate the name of the view to enter here, start script recording again and switch to that view in the applications UI. This will record a command containing that name:
+
+
+
+#### "default_visible_tabs"
+
+Views that are visible as tabs per default → these are still initially collapsed until adding them to "default_visible_views".
+
+### Step 4: Test your workspace
+
+* Save that new content in the add-on.
+* Install the add-on.
+* Look for a new workspace in the workspace toolbar on the left side of the application.
+
+## Guidelines
+
+### Icon guidelines
+* SVG Format, with a page size of 16x16. E.g. Inkscape page template "Icon 16x16"
+* Only use two colors:
+ * white (#ffffff) background
+ * black (#333333) foreground
+* For proper appearance in dark themes:
+ * Only use "black" color, so the icon will get inverted automatically in dark mode
+ * Use a white padding of 0.5px on each side
+
+## FAQ
+
+### How can I add icons to the workspace toolbar ?
+
+You can only add commands to the toolbar. The commands will bring their own icons. For scripts, which can be added like commands, a custom script icon can be set in the script editor via the 'edit properties' feature in the right mouse menu of the script:
+
+
diff --git a/2022-new-headings-intros/_sources/howtos/environments_for_python_scripts/environments_for_python_scripts.md.txt b/2022-new-headings-intros/_sources/howtos/environments_for_python_scripts/environments_for_python_scripts.md.txt
new file mode 100644
index 0000000..1a9ab62
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/environments_for_python_scripts/environments_for_python_scripts.md.txt
@@ -0,0 +1,105 @@
+# Environments for python scripts
+
+```{note}
+Script environments is available since software version 2022, revision 147326.
+```
+
+```{important}
+New package with only scripts, which are not in environment, can not be created any more. Previous packages without environment can still be installed and executed, but can not be edited. If you want to export only scripts, please use "Export Script" (RMB on the script to export) or create a script environment and add the script in it.
+```
+
+## Creating an environment in the script editor
+
+* RMB (or Ctrl+E) on the Public/User-defined scripts > New Environment
+* Each created environment contains a "modules" folder and a "modules.json" file in the "modules" folder.
+
+ 
+
+## Install / uninstall python packages
+
+### Installation
+
+* To install python packages to the created environment path: RMB on ①the environment folder or ②modules folder or ③modules.json file > Install Python Package
+
+ 
+
+* To install python packages to the public/user local path: RMB on Public/User-defined scripts > Install Python Package or old version is also valid (old version) Menu > Scripting > Script Choice > Tools > Install Python Package
+
+* The Installation can be done in two ways: network or local.
+ * Network
+ * The package list from network must be separated with a comma.
+ * To install the packages of the specific version, write the version after "==". ex) numpy==1.22.0
+
+ 
+
+ * Local
+ * Python wheel files (*.whl) can be added or removed.
+
+ 
+
+
+* The explorer of the script editor and "modules.json" file are updated after installation.
+
+ 
+
+
+### Uninstallation
+
+* RMB on a python package that should be removed > Uninstall Python Package
+* The explorer of the script editor and "modules.json" file are updated after uninstallation.
+
+ 
+
+## Writing and running a script in the environment
+
+* To create a script in the created environment: RMB (or Ctrl+N) on the environment folder > New Script
+* Scripts in a script environments can import only
+ * installed python packages in that script environment, which are displayed in modules.json file
+ * other scripts in that script environment
+
+## Editing "modules.json" file
+
+* "modules.json" file can be edited in the script editor.
+* "wheelsfrom": "local": When creating a package that contains this environment, all wheel files of the required python packages for this environment are packaged together. When this environment being imported, required python packages are installed from the contained wheel files. Importing of this environment can be done offline.
+* "wheelsfrom": "network": When creating a package that contains this environment, wheel files of the required python packages for this environment are NOT packaged together. When this environment being imported, required python packages are installed from network. Importing of this environment must be done online.
+
+ 
+
+## Creating a package that contains environments
+
+* Go to "Create Package" dialog.
+
+ 
+
+* When creating package, now only environments can be added instead of scripts and python modules.
+* More than one environment with a unique name can be packaged into a package.
+
+ 
+
+## Editing the package that contains only script environments
+
+* When editing package in the script editor, python packages can be installed and uninstalled in the environment.
+
+ 
+
+* If editing is completed, the package can be saved in package manager.
+
+ 
+
+ 
+
+## Editing the package that contains contents not in a script environment
+
+* Packages that contain contents not in a script environment are called old-school packages.
+* Old-school packages still exist and should be able to execute.
+* Old-school packages should be updated when the script contents are modified.
+* When editing old-school package in the script editor, all contents not in a script environment would be migrated automatically after a warning message.
+* The python packages contained in the old-school package would be installed in the script environment automatically, too.
+
+### Script editor
+
+
+
+### Package manager
+
+
diff --git a/2022-new-headings-intros/_sources/howtos/localization/localization.md.txt b/2022-new-headings-intros/_sources/howtos/localization/localization.md.txt
new file mode 100644
index 0000000..2c14d3b
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/localization/localization.md.txt
@@ -0,0 +1,145 @@
+# Localization of packages
+
+## Writing translatable scripts
+
+### User-defined script dialogs
+
+When adding a user defined script dialog to a script, since software version 2022 the resulting code is in JSON compatible format and will contain translation entries for all translatable texts automatically. The user does not have to care for these entries manually. They are kept consistently when the dialog is edited again and will lead to translation file entries (see below).
+
+``` Python
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ "columns": 1,
+ "monospace": False,
+ "name": "log",
+ "rows": 1,
+ "save_dialog_title": {
+ "id": "",
+ "text": "Save Log File",
+ "translatable": True
+ },
+ "scroll_automatically": True,
+ "show_save": False,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ ...
+ )
+```
+
+### Text in scripts
+
+Texts in script have to be tagged as translatable via using the `tr ()` function. During translation file generation, these texts will be processed and later replaced at runtime with the available translations.
+
+ print (tr ('This text will be translated'))
+
+
+## Translating scripts
+
+### Generating translatable XLIFF files
+
+💡 Scripts are using standard XLIFF files to access translations in different languages.
+
+#### Install package 'Internationalization'
+
+* Install the package 'Internationalization'.
+* Possible via package Manager or via downloading it from the connect directly plus drag/drop onto the application.
+
+#### Switch package into 'Edit' mode
+
+* Select the package the translations should be added to.
+* Switch it into 'Edit' mode:
+
+ 
+
+#### Execute script 'Update XLIFF files'
+
+
+
+* Execute script 'Update XLIFF files' from package 'Internationalization'.
+* Select the package with the translations which shall be generated or updated (1)
+* Set the comma separated list of language identifiers for which translation files will be generated (2)
+* Check the displayed number of translated texts for plausibility (3)
+* Press 'Update' (4) to generate translatable XLIFF files (4)
+
+ 
+
+* Afterwards, the package's XLIFF translatable files will be present in the package's languages folder:
+
+ 
+
+#### Translate XLIFF files
+
+* Export the XLIFF files via 'Export Resource...' on the right mouse menu.
+* Translate the XLIFF files. This can be done either manually or by importing them into a translation software, possibly via a translation service provider.
+* Import the XLIFF files back into the package via 'Import Resource...' on the right mouse menu.
+
+``` XML
+
+
+
+
+ Save Log File
+ Protokolldatei speichern
+
+
+ Curve inspection
+ Kurveninspektion
+
+
+ Processing...
+ In Bearbeitung...
+
+
+
+
+```
+
+## Switching package languages
+
+### Enable language
+
+💡 The package language is the same as the globally set application language.
+
+#### Selecting an package/application language
+
+* Select the appropriate language the the applications preferences dialog.
+
+ 
+
+* If a matching XLIFF file is present in an package, the translations from this file are used automatically.
+* This might require an application restart due to caching issues.
+
+## FAQ
+
+### Is there a shortcut for exporting/importing the XLIFF files ?
+
+* If there are quite many of these files and the process has to be done regularly, the resource files can be accessed right on file system.
+* Each package in 'Edit' mode mirrors its content into `%APPDATA%/gom//gom_package_scripts/`.
+* The XLIFF files can be edited right there of copies/pasted from there as long as the package remains in 'Edit' mode.
+
+### Are the translation entries persistent when updated via the 'Update XLIFF files' script ?
+
+* As long as the original texts (the texts in the 'id' attribute of the 'trans-unit' tag of the XLIFF files) are not changing, already translated entries are left untouched and will persist.
+* This is the case when the original text in the script does not change, like the text in a dialog button or the original text in a scripts 'tr ()' function.
+* Can this scheme be automated, for example in a build queue ?
+* The 'Update XLIFF files' script itself is designed to be interactive.
+* But: The source is available and the logic within can be used as a base to implement a customized XLIFF files updater to automatic execution.
+* The goal of the scheme is to have translated XLIFF files with a name scheme as shown above in the package's 'language' directory.
+
+### After the application language is set, the package is not displaying the translations for that language ?
+
+* You might have to restart the application after switching the application language in the preferences.
+* Please double check, too, if the package supports that specific language at all.
+
+
diff --git a/2022-new-headings-intros/_sources/howtos/python_api_introduction/creating_wizard_dialogs.md.txt b/2022-new-headings-intros/_sources/howtos/python_api_introduction/creating_wizard_dialogs.md.txt
new file mode 100644
index 0000000..04eb17f
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/python_api_introduction/creating_wizard_dialogs.md.txt
@@ -0,0 +1,309 @@
+# Creating wizard dialogs
+
+- [What is a wizard dialog](#what-is-a-wizard-dialog)
+- [Creating a simple wizard dialogs](#creating-a-simple-wizard-dialog)
+- [Changing the button text](#changing-the-button-text)
+- [Creating wizards with different layouts per step](#creating-wizards-with-different-layouts-per-step)
+- [Final scripts](#final-scripts)
+
+## What is a wizard dialog
+
+A wizard dialog is a sequence of steps, which guides the user through a process flow. The wizard dialog has a back button to go to the previous step, a next button to proceed with the next step and a Close button to complete the wizard dialog. The wizards layout is created through the scripting dialog editor like any other dialog and its transition logic for going through the steps is specified by a handler function.
+
+💡 Note that it is only possible to change the content of the wizards' widgets in the handler function. This means particularly, that it is not possible to remove or add widgets after the definition of the wizards' layout.
+
+## Creating a simple wizard dialog
+
+The screenshots below show a wizard with three steps, which will be created in this tutorial.
+
+ 
+
+ 
+
+The wizard has to following properties:
+
+* The wizard's layout consists of an image widget, a text widget, an input widget and the default wizard control elements (**Next**, **Back** , **Close**).
+* On script startup the dialog already contains the text and image for the first instruction set.
+* If the **Next** or **Back** button is pressed, the corresponding instruction text and image must be displayed.
+* To avoid loading the following images from an external source (which would have to be distributed together with the script), the images are encoded in dummy dialogs and read from these sources.
+* The dummy dialogs are organized in an array.
+
+Firstly, the wizard dialog and a dummy dialog for each wizard step is created. A dummy dialog holds the content of the wizards widgets for its respective step. The screenshots above show these dummy dialogs.
+
+```Python
+#
+# create main wizard dialog:
+#
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={'...'})
+
+#
+# Dummy dialogs containing the images of the corresponding steps encoded in JSON
+#
+STEP_1=gom.script.sys.create_user_defined_dialog (dialog={'...'})
+
+STEP_2=gom.script.sys.create_user_defined_dialog (dialog={'...'})
+
+STEP_3=gom.script.sys.create_user_defined_dialog (dialog={'...'})
+
+STEP_4=gom.script.sys.create_user_defined_dialog (dialog={'...'})
+
+#
+# The dummy dialogs are organized in an array for a simple step transition logic
+#
+steps = [STEP_1, STEP_2, STEP_3, STEP_4]
+```
+
+Note that the wizard dialog and the dummy dialogs have to be non-blocking dialogs. Note also, that the content of STEP_1 and DIALOG are identically. This is necessary, since the content of DIALOG will be overridden in the handler function. Let us create the handler function for managing the step transition:
+
+```Python
+count = 0
+
+#
+# handler function for step transition
+#
+def handler_func (widget):
+ global count
+
+ # save input to dummy dialog:
+ steps[count].noteInput.value = DIALOG.noteInput.value
+
+ #
+ # 'next' button has been pressed
+ #
+ if widget == DIALOG.control.next:
+ if count + 1 < len (steps):
+ count += 1
+ DIALOG.noteInput.value = steps[count].noteInput.value
+ DIALOG.text.text = steps[count].text.text
+ DIALOG.image.data = steps[count].image.data
+
+ #
+ # 'prev' button has been pressed
+ #
+ elif widget == DIALOG.control.prev:
+ if count > 0:
+ count -= 1
+ DIALOG.noteInput.value = steps[count].noteInput.value
+ DIALOG.text.text = steps[count].text.text
+ DIALOG.image.data = steps[count].image.data
+
+ #
+ # Update enabled state of the dialog control elements
+ #
+ DIALOG.control.prev.enabled = count > 0
+ DIALOG.control.next.enabled = count + 1 < len (steps)
+ DIALOG.control.close.enabled = count + 1 >= len (steps)
+```
+
+Note that `noteInput` is the object name of the text entry field assigned within the scripting dialog editor.
+Finally we register the handler function to the dialog and display the wizard dialog:
+
+```Python
+DIALOG.handler = handler_func
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+```
+
+## Changing the button text
+
+You can easily change the text of the **Next** and **Back** buttons:
+
+```Python
+DIALOG.control.next.text = "randomButtonText"
+DIALOG.control.prev.text = "anotherRandomButtonText"
+```
+
+## Creating wizards with different layouts per step
+
+Despite the limitations mentioned above, you may use a different layout for each step in the wizard by using a more sophisticated step transition logic. Instead of changing the content of the displayed wizard dialog, you may display another wizard at each step. Let us go through the code necessary for doing that.
+First of all we have to define appropriate dialogs:
+
+```Python
+
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+STEP_2=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+STEP_3=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+STEP_4=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+```
+
+This time, STEP_2, STEP_3 and STEP_4 won´t be simple dummy dialogs used as containers, they have to be wizard dialogs instead. Now let us define the handler function:
+
+```Python
+steps = [DIALOG, STEP_2, STEP_3, STEP_4]
+inputStrings = ['', '', '', '']
+current_step = -1
+new_step = 0
+
+def handler_func (widget):
+ global current_step, new_step
+ global current_dialog
+
+ if widget == current_dialog.control.next:
+ if current_step + 1 < len (steps):
+ new_step = current_step + 1
+ gom.script.sys.close_user_defined_dialog (dialog=current_dialog)
+ elif widget == current_dialog.control.prev:
+ if current_step > 0:
+ new_step = current_step - 1
+ gom.script.sys.close_user_defined_dialog (dialog=current_dialog)
+
+
+ current_dialog.control.prev.enabled = current_step > 0
+ current_dialog.control.next.enabled = current_step + 1 < len (steps)
+ current_dialog.control.close.enabled = current_step + 1 >= len (steps)
+
+```
+
+The basic idea is to close the current dialog if the user hits the **Next** button to proceed to the next dialog step or the **Back** button to return to the previous one. The next code snippet will make it clear:
+
+```Python
+while current_step != new_step :
+ current_step = new_step
+ current_dialog = steps[current_step]
+ current_dialog.handler = handler_func
+ RESULT=gom.script.sys.show_user_defined_dialog (dialog=current_dialog)
+ inputStrings[current_step] = RESULT.noteInput
+```
+
+The program will enter the while loop, if the the wizard step changed (or due to initialization) and launch a new dialog. As long as the user clicks **Next** or **Back** in the current dialog, the while loop won't be left and "the" wizard will be displayed. If the user leaves the dialog through **Close**, the while loop will be left and "the" wizard terminates. `noteInput` is the object name of the text entry field within the scripting dialog editor as before. Please note that the `.value` suffix has to be omitted here.
+
+## Final scripts
+
+The following scripts combine the code snippets above. The first one is the single layout wizard, the second one the multi layout wizard.
+
+### Single Layout Wizard
+
+[SingleLayoutWizard.py](assets/SingleLayoutWizard.py)
+
+```Python
+# -*- coding: utf-8 -*-
+
+# Script: SingleLayoutWizard.py
+
+import gom
+
+#
+# create main wizard dialog:
+#
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+#
+# Dummy dialogs containing the images of the corresponding steps encoded in JSON
+#
+STEP_1=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+STEP_2=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+STEP_3=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+STEP_4=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+#
+# The dummy dialogs are organized in an array for a simple step transition logic
+#
+steps = [STEP_1, STEP_2, STEP_3, STEP_4]
+
+count = 0
+
+#
+# Registered handler function
+#
+def handler_func (widget):
+ global count
+
+ # save input to dummy dialog:
+ steps[count].noteInput.value = DIALOG.noteInput.value
+
+ #
+ # 'next' button has been pressed
+ #
+ if widget == DIALOG.control.next:
+ if count + 1 < len (steps):
+ count += 1
+ DIALOG.noteInput.value = steps[count].noteInput.value
+ DIALOG.text.text = steps[count].text.text
+ DIALOG.image.data = steps[count].image.data
+ #
+ # 'prev' button has been pressed
+ #
+ elif widget == DIALOG.control.prev:
+ if count > 0:
+ count -= 1
+ DIALOG.noteInput.value = steps[count].noteInput.value
+ DIALOG.text.text = steps[count].text.text
+ DIALOG.image.data = steps[count].image.data
+
+ #
+ # Update enabled state of the dialog control elements
+ #
+ DIALOG.control.prev.enabled = count > 0
+ DIALOG.control.next.enabled = count + 1 < len (steps)
+ DIALOG.control.close.enabled = count + 1 >= len (steps)
+
+DIALOG.handler = handler_func
+
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+
+# Access dialog input strings:
+print( steps[0].noteInput.value )
+print( steps[1].noteInput.value )
+print( steps[2].noteInput.value )
+print( steps[3].noteInput.value )
+```
+
+### Multi Layout Wizard
+
+[MultiLayoutWizard.py](assets/MultiLayoutWizard.py)
+
+```Python
+# -*- coding: utf-8 -*-
+
+# Script: MultiLayoutWizard
+
+import gom
+
+DIALOG=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+STEP_2=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+STEP_3=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+STEP_4=gom.script.sys.create_user_defined_dialog (dialog={...Boring dialog definition...})
+
+current_step = -1
+new_step = 0
+steps = [DIALOG, STEP_2, STEP_3, STEP_4]
+inputStrings = ['', '', '', '']
+
+def handler_func (widget):
+ global current_step, new_step
+ global current_dialog
+
+ if widget == current_dialog.control.next:
+ if current_step + 1 < len (steps):
+ new_step = current_step + 1
+ gom.script.sys.close_user_defined_dialog (dialog=current_dialog)
+ elif widget == current_dialog.control.prev:
+ if current_step > 0:
+ new_step = current_step - 1
+ gom.script.sys.close_user_defined_dialog (dialog=current_dialog)
+
+
+ current_dialog.control.prev.enabled = current_step > 0
+ current_dialog.control.next.enabled = current_step + 1 < len (steps)
+ current_dialog.control.close.enabled = current_step + 1 >= len (steps)
+
+while current_step != new_step :
+ current_step = new_step
+ current_dialog = steps[current_step]
+ current_dialog.handler = handler_func
+ RESULT=gom.script.sys.show_user_defined_dialog (dialog=current_dialog)
+ print(RESULT.noteInput)
+ inputStrings[current_step] = RESULT.noteInput
+
+
+# Print out the acquired input:
+print(inputStrings[0])
+print(inputStrings[1])
+print(inputStrings[2])
+print(inputStrings[3])
+```
diff --git a/2022-new-headings-intros/_sources/howtos/python_api_introduction/python_api_introduction.md.txt b/2022-new-headings-intros/_sources/howtos/python_api_introduction/python_api_introduction.md.txt
new file mode 100644
index 0000000..9994929
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/python_api_introduction/python_api_introduction.md.txt
@@ -0,0 +1,414 @@
+---
+myst:
+ html_meta:
+ "description": "Introduction to the Python API for extending GOM Inspect 2022 with Packages/Add-ons"
+ "keywords": "Metrology, GOM Inspect, Python API, GOM API, Scripting, Packages, Add-ons, How-tos"
+---
+# GOM Inspect Python API introduction
+
+Welcome to the GOM Inspect Python API introduction. This is your starting point into Add-on development for GOM Inspect. Here you find out what you can do with Add-ons, how they work and how you create them.
+
+See [Introduction to Python Scripting](https://techguide.gom.com/en/gom-software-2022/article/introduction_to_python_scripting.html) if you are new to Python or the GOM Software Python interface.
+
+## Creating projects
+
+You can create a new, empty project as follows:
+
+``` Python
+# Create a new project
+gom.script.sys.create_project ()
+```
+
+```{note}
+💡 This way, a project in the default workflow (part-based) is created. For the legacy workflow (part-less), please refer to [Legacy projects \(part-less\)](#legacy-projects-part-less)
+```
+
+## Creating parts
+
+The evaluation elements are usually placed under a "part". Accordingly, an empty part can be created as follows:
+
+``` Python
+# Creates a new part in your project with the name 'Part 1'
+PART_OBJECT = gom.script.part.create_new_part (name='Part 1')
+```
+
+An existing part can be accessed via name or index in the new category:
+
+``` Python
+# Access the part object via name
+PART_OBJECT = gom.app.project.parts['Part 1']
+
+# or via index
+PART_OBJECT = gom.app.project.parts[0]
+
+# you can access all parts via iterating over the parts attribute
+for p in gom.app.project.parts:
+ print (p)
+```
+
+## Adding elements to a part
+
+If an actual mesh or CAD or elements are imported into a part project, different options are available. For scripting, the import is always separated into two different steps.
+
+1. Importing the elements into the *Elements in clipboard*
+2. Add the imported elements to a created part
+
+Example:
+
+``` Python
+gom.script.part.create_new_part (name='Part 1')
+
+# import element into 'Element in clipboard'
+gom.script.sys.import_g3d (
+ files=['D:/gom_part.g3d'],
+ import_mode='clipboard'
+)
+
+# Move it to a created part
+gom.script.part.add_elements_to_part (
+ delete_invisible_elements=True,
+ elements=[gom.app.project.clipboard.actual_elements['gom_part']],
+ import_mode='new_elements',
+ part=gom.app.project.parts['Part 1'])
+
+```
+
+In the same way, a CAD can be imported into a part project.
+
+Constructing new elements based on elements which already belong to a part are automatically added to that part.
+
+## Accessing CAD and actual mesh
+
+A **mesh element** of a part can be accessed in the following ways:
+
+``` Python
+# This is usually the most elegant way and is recommended.
+# Replacing your mesh will keep the correct parametric if you use
+# the actual values reference (like formerly the 'Actual master' in the part-less workflow).
+PART_OBJECT = gom.app.project.parts['Part 1']
+MESH_PROXY = gom.ActualReference (PART_OBJECT)
+
+# If you really like to access the representing CAD Element (which is not always existing, e.g. for planning)
+# you can access this element via
+MESH_ELEMENT = gom.ActualReference(PART_OBJECT).actual
+
+```
+
+The **CAD** of a part can be addressed in the following ways:
+
+``` Python
+# This is usually the most elegant way and is recommended.
+# Replacing your CAD will keep the correct parametric if you use
+# the nominal values reference (like formerly the 'All CAD Group proxy' in the part-less workflow)
+PART_OBJECT = gom.app.project.parts['Part 1']
+CAD_PROXY = gom.NominalReference (PART_OBJECT)
+
+# If you really like to access the representing CAD Element (which is not always existing, e.g. for planning)
+# you can access this element via
+CAD_ELEMENT = gom.NominalReference(PART_OBJECT).nominal
+```
+
+## Accessing an object's part
+
+This information can be retrieved via an attribute of the object. Here is an example:
+
+``` Python
+PART_OBJECT = gom.app.project.inspection['Point 1'].part
+```
+
+## Accessing all elements and alignments of a part
+
+One possibility is to iterate over all elements in the different categories (nominal, actual, inspection, alignments) and to check the part attribute. Usually, for most applications this can be achieved easier using an `ElementSelection` (some elements are hidden and not listed, but usually you do not need access to these elements). Here is an example:
+
+``` Python
+for x in gom.ElementSelection ({'category': ['key', 'elements', 'part', gom.app.project.parts['Part']]}):
+ print (x)
+```
+
+## Accessing elements and alignments of *Element in clipboard*
+
+Also, these elements can be easily accessed via an `ElementSelection`:
+
+``` Python
+for x in gom.ElementSelection ({'category': ['key', 'elements', 'is_element_in_clipboard', 'True']}):
+ print (x)
+```
+
+## Alignments
+
+Alignments are still accessible via `gom.app.project.alignments` (like in the legacy workflow). The same is valid for `gom.app.project.nominal_elements`, `gom.app.project.actual_elements` and `gom.app.project.inspection`. You have to keep in mind that you will get all elements or alignments of all parts. You can use the `part` token to establish to which part an alignment belongs to or you use an `ElementSelection` (see examples above):
+
+``` Python
+for x in gom.ElementSelection ({'category': ['key', 'elements', 'part', gom.app.project.parts['Part'], 'explorer_category', 'alignment']}):
+ print (x)
+```
+
+There is one special handling for multiple parts and scripting with the *Original alignment*. To distinguish these alignments for different parts, the scripting name contains the part name and is modified into:
+
+``` Python
+gom.app.project.alignments['::Original alignment']
+```
+
+## Legacy projects (part-less)
+
+```{note}
+⚠️ You can skip this section unless you are dealing with legacy projects!
+```
+
+As shown above, the following code creates a project in the part-based workflow, which allows to analyze multiple parts:
+
+``` Python
+# Create a project (default; part-based workflow)
+gom.script.sys.create_project ()
+
+# For compatibility, the kind of project can be stated explicitely:
+# Create a project (part-based workflow)
+gom.script.sys.create_project (type=2018)
+```
+
+You can still create a project in the legacy workflow, which is restricted to a single part:
+
+``` Python
+# Create a project (part-less workflow)
+# Note: This allows to analyze a single part only!
+gom.script.sys.create_project (type=2016)
+```
+
+Use the following code to determine the type of an existing project:
+
+``` Python
+if gom.app.project.is_part_project:
+ print ('Is part project: True')
+else:
+ print ('Is part project: False')
+```
+
+In former projects, the CAD or the actual mesh have been accessed via their proxies:
+
+*All CADGroup proxy*
+
+*Actual Master*
+
+### Measurement series and Measuring environment
+
+The access and information about the VMR, measuring setups and measurement series are much more separated in the part-based workflow as compared to the part-less workflow. New categories and `ElementSelection` categories were introduced. If you have further questions regarding scripting purposes, please contact the ZEISS support.
+
+Here just the most important information follows. The measurements have their own category in the part-based workflow. A measurement can be accessed via the attribute `measurement_series` and no longer via `actual_elements`.
+
+``` Python
+MEASUREMENT = gom.app.project.measurement_series['Scan 1']
+
+MEASUREMENTS = gom.ElementSelection ({'category': ['key', 'elements', 'explorer_category', 'measurements', 'object_family', 'measurement_series']})
+```
+
+### Reports
+
+Reports did not change so much in the part-based workflow. Reports are not assigned to a part, they show the situation of measurement series, VMR or multiple parts at the same time. Some slight changes must be taken into account: The keyword `alignment` could now return names of more than one alignment (comma separated, i.e. a Python list) due to the fact that multiple parts (if visible in the report page) with their own alignment must be respected.
+
+### CAD structure and contents
+
+For scripting with CADs in part-based projects, some additional information are necessary. Most importantly:
+
+Only one CAD Group per part is supported.
+
+
+The *CAD Group* (in a part-based workflow) supports now the access via an internal file structure to represent structures stored in CAD files like *CATProduct*. These entities are imported in the part-less workflow as separated *CAD Groups*.
+
+The following simple code examples show how to access bodies or files of a CAD Group.
+
+⚠️ **Keep in mind:** This access gives you information about the bodies or files. You can use this also for the deletion of bodies. Visibility operations are suppressed by intention. Usage for construction purposes is not recommended due to the fact that exchanging CAD structures would **not** work as expected.
+
+``` Python
+# this example code list all bodies of all CADs for all parts
+cad = filter (lambda c: c.type == "cad", gom.app.project.nominal_elements)
+for c in cad:
+ print (c.name, c.type)
+ for b in c.bodies:
+ print (b.name)
+```
+
+This is an example to list files by `cat_part`:
+
+``` Python
+cad = filter (lambda c: c.type == "cad", gom.app.project.nominal_elements)
+
+# for all cads in all parts list the file structure of each CAD of one part and furthermore all bodies of each file
+for c in cad:
+ print (c.name)
+ print ('Number of files: ' + str (len (c.file)))
+ for file in c.file:
+ print (file)
+ for b in file.bodies:
+ print (' {}'.format (b.name))
+```
+
+### CAD assembly structure in the *Elements in clipboard*
+
+These information are usually not necessary for scripting. The most important fact is that the assembly structure does not represent our CAD structure. The assembly structure shows much more internal details.
+
+### Script compatibility
+
+#### Actual master and All CAD Group proxy
+For the single part workflow old scripts using *Actual Master* and the *All CAD Group proxy* in creation commands should usually work.
+
+⚠️ **Keep in mind:** The functionality of these proxies is no longer present in the part-based workflow. Therefore functionalities like *Define Actual Master* will not work anymore. If the scripting tries to resolve the elements for the *Actual Master* a mapping takes place and the *ActualValues-Reference* of the unique part is returned. The same happens for the *All CAD Group proxy* and the *NominalValues-Reference*.
+
+#### Measurement series
+The script compatibility for the current measurement list is given in most cases. Normal information is usually accessible via the same attributes as before.
+
+#### Tesselate Geometrical Element
+The obsolete command `gom.script.mesh.tesselate_geometrical_element` creates an element of type mesh.
+
+In the part-based workflow this command has been replaced with the command `gom.script.primitive.tesselate_geometrical_element`, which creates elements of type surface.
+
+## Access element properties
+
+The "elements" of the GOM Software, i.e. what you see in the element explorer of your project, hold several properties and data which you can access using the Python API.
+
+First of all, you need a reference to an element, which you can get either by [using a script dialog](script_dialogs_introduction.md) or simply by referencing it by name.
+
+If you have installed the `Python API Examples` add-on from the store and loaded the `gom_part_test_project` (see the [Python API Examples Documentation](../../python_examples/index.md)), you can reference the mesh like this:
+
+```python
+mesh_element = gom.app.project.parts['Part'].actual
+```
+
+### Explore available properties
+
+Once you have a reference to the element, you can access its properties using several keywords in the form `element.`.
+
+One way to inspect the available keys is by using the 'Script Object' explorer, which is available from the context menu `-> Insert -> Element Value` or by shortcut `F2`.
+
+
+```{image} assets/script_object_explorer.jpg
+:alt: Script Object Explorer
+:width: 350px
+```
+
+You will find several keywords there, with a preview of the current value.
+If you click `OK`, the complete call, including element reference by name, will be copied to your current script. If you already have a name reference, you can of course use this reference.
+
+```python
+mesh_element = gom.app.project.parts['Part'].actual
+print (mesh_element.area)
+```
+Output:
+```
+>>> 207422.1875
+```
+
+### Element properties in VSCode
+
+Using Visual Studio Code, you can get auto-completion for the usable keywords directly in a pop-up.
+
+
+
+See [Using VSCode Editor](../using_vscode_editor/using_vscode_editor.md) for details.
+
+
+### Properties of different stages
+
+If you are using a multi-stage project, the approach as described above will always give you the element properties in the current stage. If you need access to properties in a different stage, you can use the `in_stage[s]` modifier:
+
+```python
+mesh_element = gom.app.project.parts['Part'].actual
+print (mesh_element.in_stage[0].area)
+```
+Output:
+```
+>>> 207422.1875
+```
+
+```{note}
+Stage indices start with index `0`.
+```
+
+In this way, you can get simple properties of a different stage. If you need access to data of all stages at once, especially for larger data (like arrays of vertices), use "Data interfaces" as described below.
+
+
+## Element data interfaces
+
+In a script, each element present in the application (project, inspection elements, reports, ...) can be referenced by a named identifier. Each identifier consists of a type and some index, which can be a name or an integer number.
+
+### Concept
+This is already the case for access via the data interface instead of the token interface: The returned value has the format `(stages, )`.
+
+```{code-block} python
+:caption: Example 1 - Mesh
+
+# Mesh in 8 stage trend project with 238654 points, each with one (x, y, z) triple
+> print (gom.app.project.parts['Part'].actual.data.coordinate.shape)
+(8, 238654, 3)
+```
+
+```{code-block} python
+:caption: Example 2 - Scalar value
+
+# Single scalar value in a 8 stages trend project
+> print (gom.app.project.inspection['My Check'].data.result_dimension.deviation.shape)
+(8, 1)
+```
+
+```{code-block} python
+:caption: Example 3 - Image
+
+# Image in 8 stage trend project with 4000x3000 pixels, each with one (r, g, b, a) tuple
+> print (gom.app.project.measurement_list['Scan'].measurement['M1'].images['Left camera'].data.rgb.shape)
+(8, 3000, 4000, 4)
+```
+
+⚠️ When accessing the image, the complete data set is *not* transferred immediately from C++ to Python! Instead this happens just in the moment when it is converted into a numpy array!
+
+```{code-block} python
+:caption: Example 4 - Transferring image data
+
+# Fetch gom.Array with image data in all stages (not transferred !)
+> image = gom.app.project.measurement_list['Scan'].measurement['M1'].images['Left camera'].data.rgb
+> print (image.shape, type (image))
+(8, 3000, 4000, 4), gom.Array ()
+# 45 MB Image data if on stage, transferred in < 100 ms
+> data = np.array (image[0])
+> print (data.shape)
+(3000, 4000, 4)
+```
+
+
diff --git a/2022-new-headings-intros/_sources/howtos/python_api_introduction/script_dialogs_introduction.md.txt b/2022-new-headings-intros/_sources/howtos/python_api_introduction/script_dialogs_introduction.md.txt
new file mode 100644
index 0000000..f4239c3
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/python_api_introduction/script_dialogs_introduction.md.txt
@@ -0,0 +1,1569 @@
+# Using script dialogs
+
+- [Creating dialogs](#creating-dialogs)
+- [Dialog widgets](#dialog-widgets)
+- [Executing dialogs](#executing-dialogs)
+- [Wizards](#wizards)
+
+## Creating dialogs
+
+- [Dialog designer](#dialog-designer)
+- [Dialog layout](#dialog-layout)
+ - [Editing the grid](#editing-the-grid)
+ - [Spacers](#spacers)
+- [Widgets](#widgets)
+ - [Inserting and removing widgets](#inserting-and-removing-widgets)
+ - [Configuring widgets](#configuring-widgets)
+- [Editing already created dialogs](#editing-already-created-dialogs)
+
+### Dialog designer
+
+* User defined **Dialogs** can be inserted into the script using _right mouse button_->"Insert / Dialog...".
+
+ 
+
+* When a new dialog is inserted, a dialog **Template**, the **target location** of the dialog configuration and the dialog **Type** can be selected.
+
+ 
+
+* Some dialog **Templates** are provided by the system. Additional templates can be created by the user.
+
+* The options for placing a dialog configuration (see section **Create as** in the window above) are
+ * **Separate dialog file** - default
+ * **Embedded into script**
+
+ The base filename of a dialog file is `dialog.gdlg`, it can be renamed later. A dialog is stored as a JSON document internally.
+
+
+
+ ```{code-block} python
+ :caption: Example: Script with separate dialog file
+
+ RESULT=gom.script.sys.execute_user_defined_dialog (file=':dialog.gdlg')
+ ```
+
+ ```{code-block} python
+ :caption: Example: Script with embedded dialog
+
+ RESULT=gom.script.sys.execute_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ ...
+ }
+ ]
+ ],
+ "control": {
+ "id": "OkCancel"
+ },
+ "embedding": "always_toplevel",
+ "position": "automatic",
+ "size": {
+ "height": 155,
+ "width": 198
+ },
+ "sizemode": "automatic",
+ "style": "",
+ "title": {
+ "id": "",
+ "text": "Message",
+ "translatable": True
+ }
+ })
+ ```
+
+* The options for the dialog **Type** are
+ * **Break dialog (script is blocked)** - default
+ * **Extendable break dialog (script is blocked)**
+ * **Info dialog (script continues)**
+
+ The dialog type is explained in section [Executing dialogs](#executing-dialogs)
+
+
+* Dialogs are designed using a GUI based **Dialog Editor**.
+
+ 
+
+### Dialog layout
+
+* The **Dialog Editor** is using a grid based layout.
+* Elements can be inserted into the grid via drag and drop.
+
+#### Editing the grid
+
+💡 Editing the layout means changing the underlying grid.
+
+* Because the underlying layout is a grid, the following actions are possible:
+ * Adding and removing rows and columns.
+ * Merging and splitting rows and columns.
+
+ | Tool button | Function |
+ | ---------------------------------------- | --------------------------------- |
+ |  | Split selected cells vertically |
+ |  | Split selected cells horizontally |
+ |  | Merge selected cells |
+
+* Selected cells are marked with a red overlay.
+
+ 
+
+#### Spacers
+
+💡 **Spacers** are empty spaces extending in either horizontal or vertical direction.
+
+* If a spacer is inserted into a cell, the cell claims the maximum available space in spacer direction.
+* All other cells share the remaining space.
+
+
+
+### Widgets
+
+#### Inserting and removing widgets
+
+* The list of available widgets resides at the left of the Dialog Editor in the section **Dialog Elements**.
+* **Widgets** are inserted via drag and drop.
+* Newly dropped widgets overwrite existing widgets at the drop target cells.
+* A unique **object name** is assigned during insertion of a widget. This name is used to access the widget in the Python script.
+* Because each cell has to be filled with a widget, widgets can not be removed from the grid. To get rid of a widget
+ * Another widget can be dragged and dropped onto the existing widget or
+ * The widget cell can be merged with another cell.
+
+💡 Removing widgets from the grid is not possible. Instead, they can be overwritten by other widgets.
+
+
+
+#### Configuring widgets
+
+* The properties of selected widgets can be edited in the **Property Editor** at the right side of the Dialog Editor.
+* Every widget has at least a unique **Object name**.
+* Additionally, various parameters depending on the widget type can be edited.
+
+
+
+The definition of the dialog can be found in [scriptingEditorExampleDialog.py](assets/scriptingEditorExampleDialog.py)
+
+### Editing already created dialogs
+
+* Creating a dialog leads to a script command with a dialog representation as JSON code, which can either be embedded or stored in an external dialog file (`*.gdlg`).
+* Double clicking onto the embedded dialog or the dialog file opens the Dialog Editor again.
+
+## Dialog widgets
+
+- [Use of the \_\_doc\_\_ string](#use-of-the-__doc__-string)
+- [Control widget](#control-widget)
+ - [Control widget elements](#control-widget-elements)
+ - [Control button properties](#control-button-properties)
+ - [Status label](#status-label)
+- [Specific widgets](#specific-widgets)
+ - [Description field (label) widget](#description-field-label-widget)
+ - [Continuous text widget](#continuous-text-widget)
+ - [Image widget](#image-widget)
+ - [Log widget](#log-widget)
+ - [Progress-bar widget](#progress-bar-widget)
+ - [Element name widget](#element-name-widget)
+ - [Integer widget](#integer-widget)
+ - [Decimal widget](#decimal-widget)
+ - [Text entry field](#text-entry-field)
+ - [Slider widget](#slider-widget)
+ - [Checkbox widget](#checkbox-widget)
+ - [File widget](#file-widget)
+ - [Date widget](#date-widget)
+ - [Color widget](#color-widget)
+ - [Unit widget](#unit-widget)
+ - [Selection element widget](#selection-element-widget)
+ - [Selection list widget](#selection-list-widget)
+ - [Button widget](#button-widget)
+ - [Radio button widget](#radio-button-widget)
+ - [Abort button widget](#abort-button-widget)
+ - [Tolerances widget](#tolerances-widget)
+ - [File system browser widget](#file-system-browser-widget)
+
+This section gives an overview of the available widgets. If the code examples given in this section are not intuitive to you, you might want to take a look
+into [Executing dialogs](#executing-dialogs).
+
+### Use of the \_\_doc\_\_ string
+
+Information about the widgets can be obtained by accessing their doc string. Let `objName` be the object name of a widget and `DIALOG` the dialog handle
+(see [Executing dialogs](#executing-dialogs) if this is unclear to you), the `__doc__` string can be obtained as follows:
+
+```python
+print( DIALOG.objName.__doc__ )
+```
+
+### Control widget
+
+💡 The **Control** widget contains the **ok** / **cancel** or similar buttons of the dialog.
+
+* The control elements of a dialog cannot be configured like other dialog widgets.
+* Therefore, their name is fixed and they are grouped together inside of the control widget named **control**.
+* The control elements consist of the dialogs lower buttons plus a configurable dialog status label.
+
+| Handle | Property | Example |
+| ------------------------- | ----------------------------------------- | --------------------------------------------------- |
+| DIALOG.control | Control widget | - |
+| DIALOG.control.status | Status icon of the control widget |
DIALOG.control.status = 'Point 1 missing'
|
+| DIALOG.control.\ | Handle for a button of the control widget |
DIALOG.control.ok.enabled = False
|
+
+#### Control widget elements
+
+💡 The names of the **Control** widget elements are fixed
+
+* Usually, the names are corresponding with the elements' semantics. For example, the name of the **ok** button is 'ok'. The names can also be obtained from the `__doc__` string as shown in the code example below.
+* The control elements are accessed like all other widget attributes.
+
+```{code-block} python
+:caption: Accessing the control widget
+
+# Print control widget properties print (DIALOG.control.__doc__)
+ControlGroup
+
+Attributes:
+
+status (string) - Status tool tip icon
+ok (unspecified/various) - Control widget
+cancel (unspecified/various) - Control widget
+```
+
+#### Control button properties
+
+Control buttons only have the following two properties which can be set programmatically:
+
+| Property | Type | Example |
+| -------- | ---- | ------------------------------------------------ |
+| text | str |
DIALOG.control.prev.text = 'Previous'
|
+| enabled | bool |
DIALOG.control.ok.enabled = False
|
+
+#### Status label
+
+⚠️ The **Status label** of the control widget is invisible until a status text is set.
+
+* If a status text is set, a small warning icon appears, like in regular applications' dialogs.
+* The status label can be configured using its properties like all other widgets.
+
+
+
+```{code-block} python
+:caption: Using the Status label
+
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+
+# Set status label text
+DIALOG.control.status = 'No point selected.'
+
+# Set 'ok' button to disabled DIALOG.control.ok.enabled = False
+gom.script.sys.show_user_defined_dialog(dialog = DIALOG)
+
+```
+
+You can reset the status icon and clear the error message by assigning an empty string (`DIALOG.control.status = ''`).
+
+### Specific widgets
+
+#### Description field (label) widget
+
+
+
+Description field (label) widget
+: The Description field (label) widget allows to display static text. It is typically used for labelling a section or an individual element of a dialog.
+
+| Property | Type | Example |
+| --------- | ----- | ------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.label.tooltip = 'This is just a label!'
|
+| enabled | bool |
DIALOG.label.enabled = False
|
+| focus | bool |
DIALOG.label.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.label.visible = False
|
+| text | str |
DIALOG.label.text = 'New label:'
|
+| word_wrap | bool |
DIALOG.label.word_wrap = True
|
+
+
+#### Continuous text widget
+
+
+
+Continuous text widget
+: The Continuous text widget allows to display static text and keywords. A double click onto a text field widget opens the content editor. Some formatting can be applied.
+
+| Editor | Dialog |
+| -------------------------- | --------------------------- |
+|  |  |
+
+
+%* The keywords displayed in text field widgets can originate from different source:
+%
+% * Global application keywords
+%
+% * project related keywords
+%
+% * local script variables.
+%
+%⚠️ Local script variables can be displayed in text fields by inserting them via the 'insert expression' dialog.
+%
+% * Local script variables are invalid until the variable assignment is reached. They cannot be displayed statically in the text
+% field editor prior to script execution, so an invalid value will most certainly be displayed instead.
+%
+% To Do: Check how to insert local variables
+
+| Property | Type | Example |
+| ------------------- | ---- | ---------------------------------------------------------- |
+| enabled | bool |
|
+
+##### Displaying keywords in a continuous text widget
+
+A keyword can be inserted into the text with the following procedure:
+
+1. RMB -> 'Insert Expression...'
+
+ 
+
+2. Select 'Insert Keyword' button
+
+ 
+
+3. Select the desired keyword from the tree
+
+ 
+
+4. The keyword and its actual value are shown
+
+ 
+
+5. The final rendering of the text widget
+
+ 
+
+##### Internal representation of a dialog with text widget
+
+The dialog is stored as a JSON document internally.
+
+
+
+```{code-block} python
+:caption: Internal representation of a dialog
+
+gom.script.sys.execute_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ ...
+ },
+ {
+ "columns": 1,
+ "default_font_family": "",
+ "default_font_size": 0,
+ "name": "text",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "\\
# This is the actual image data # Copy image from one dialog to another: my_dialog.my_image.data = image_container_dialog.image_1.data
|
+| width | int |
print('image width ' + str(DIALOG.image.width))
|
+| height | int |
print('image height ' + str(DIALOG.image.height))
|
+| visible | bool |
DIALOG.image.visible = False
|
+
+Note that you can switch from a system image to a user image using the property `use_system_image`. But this user image must have been selected beforehand in the designer. You cannot read a new image file by setting the `filename` property. Also, all of the image formatting properties (`keep_original_size`, `keep_aspect`, `width`, `height`) only work in the designer. From the script you can only read these values. Although you cannot read images using the `filename` property you can copy images from one dialog to another using the `data` property. So you are able to prepare (create) a dialog as an image container holding several images. You can then use this image container dialog to copy the image you need to an actually displayed dialog.
+
+##### Internal representation of a dialog with image widget
+
+The dialog is stored as a JSON document internally. The 'data' element contains the image data.
+
+```{code-block} python
+:caption: Internal representation of an image
+
+# The 'data' element contains the image data (shortened version here)
+RESULT=gom.script.sys.execute_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ "columns": 1,
+ "data": "AAAAAYlQTkcNChoKAAAADUlIRFIAAAQAAAACQAgCAAAAnPeDgptZSsdt...",
+ "file_name": "C:/Users/IQMPRINK/Downloads/zeiss-inspect_python.jpg",
+ "height": 144,
+ "keep_aspect": True,
+ "keep_original_size": False,
+ "name": "image",
+ "rows": 1,
+ "system_image": "system_message_information",
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "image",
+ "use_system_image": False,
+ "width": 256
+ }
+ ]
+ ],
+ "control": {
+ "id": "Close"
+ },
+ "embedding": "always_toplevel",
+ "position": "automatic",
+ "size": {
+ "height": 233,
+ "width": 292
+ },
+ "sizemode": "automatic",
+ "style": "",
+ "title": {
+ "id": "",
+ "text": "Dialog with image",
+ "translatable": True
+ }
+})
+```
+
+#### Log widget
+
+
+
+Log widget
+: The Log widget can display multiple lines of unformatted text, which can be easily saved to a text file by clicking the save button.
+
+
+| Property | Type | Example |
+| -------------------- | --------- | -------------------------------------------------------------- |
+| enabled | bool |
|
+
+#### Progress bar widget
+
+
+
+Progress bar widget
+: The Progress bar widget can be used in the two modes _system_ and _manual_.
+
+Manual mode
+: In this mode, the user may set the progress bar through its `value` variable.
+
+ ```{code-block} python
+ import gom, time
+ DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+ DIALOG.progress.minimum = 0
+ DIALOG.progress.maximum = 100
+ gom.script.sys.open_user_defined_dialog( dialog = DIALOG )
+ DIALOG.progress.value = 0
+ time.sleep(1)
+ DIALOG.progress.value = 33
+ time.sleep(1)
+ DIALOG.progress.value = 66
+ time.sleep(1)
+ DIALOG.progress.value = 100
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+ ```
+
+Automatic mode
+: In this mode, the progress bar displays the same progress informations as the progress bar in the lower right corner of the software.
+
+ ```{code-block} python
+ import gom
+ DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+ gom.script.sys.open_user_defined_dialog (dialog=DIALOG)
+ gom.script.sys.create_project ()
+ gom.script.sys.import_project (file='some project')
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+ ```
+
+You can switch between automatic and manual mode from within the script by setting the mode variable as shown below:
+
+```python
+# manual mode:
+DIALOG.progress.mode = "manual"
+
+# automatic mode:
+DIALOG.progress.mode = "system"
+```
+
+Partially controlled system progress bar
+: The range of a system progress bar can be divided into parts, sequentially controlled by an executed command.
+ * The progress bar range can be split into multiple parts.
+ * Each part controls an equally sized progress bar interval. If, for example, there are 3 parts, the first part ranges from 0 to 33, the second from 33 to 66 and the third from 66 to 100.
+ * When a command is executed, the command controls just the one active part of the progress bar widget.
+
+
+
+ ``` python
+ # -*- coding: utf-8 -*-
+
+ import gom
+
+ # Create a user defined dialog with a progress bar, mode 'system'
+ DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+ gom.script.sys.open_user_defined_dialog( dialog = DIALOG )
+
+ # Split progress bar into 3 parts
+ DIALOG.progress.parts = 3
+
+ # Current part is the first interval (part '0', because we are counting from '0')
+ DIALOG.progress.step = 0
+
+ # Execute load command. The command will control the first progress bar range from 0% to 33%.
+ # That means when the command has been finished, the progress bar will display '33%'.
+ gom.script.sys.load_project (file='some project')
+
+ # Current part is the second interval. The progress bar runs from 33% to 66%
+ DIALOG.progress.step = 1
+
+ gom.script.sys.switch_to_report_workspace ()
+ gom.script.report.update_report_page (
+ pages=gom.app.project.reports,
+ switch_alignment=True,
+ switch_stage=False)
+
+ # Current part is the third interval. The progress bar runs from 66% to 100%
+ DIALOG.progress.step = 2
+
+ gom.script.sys.switch_to_inspection_workspace ()
+ gom.script.sys.recalculate_all_elements ()
+ ```
+
+💡 It is possible to switch between automatic and manual mode for each part.
+
+| Property | Type | Example |
+| -------- | ----- | --------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.progressbar.tooltip = 'Work in progress!'
|
+| enabled | bool |
DIALOG.progressbar.enabled = False
|
+| value | int |
if DIALOG.progressbar.value < 50:
|
+| focus | bool |
DIALOG.progressbar.focus = True
⚠️ Only works if dialog is open |
+| minimum | int |
DIALOG.progressbar.minimum = 20
|
+| maximum | int |
DIALOG.progressbar.maximum = 50
|
+| visible | bool |
DIALOG.progressbar.visible = False
|
+| parts | int |
# Set number of progress bar parts DIALOG.progressbar.parts = 3
|
+| step | int |
# Set current step DIALOG.progressbar.step = 0
|
+| text | str |
# Set text mode (none, percentage, step) DIALOG.progressbar.text = 'step'
|
+| mode | str |
# Set mode (system, manual) DIALOG.progressbar.mode = 'manual'
|
+
+#### Element name widget
+
+
+
+Element name widget
+: The Element name widget is used to request an element name from the user. It is possible to select the default name (according to naming scheme, e.g. 'Point 2' if 'Point 1' already exists), or to enter an arbitrary name. `elementnameWidget` is the object name of the element name widget in the example below.
+
+```python
+# Let the user define 3 new points (the coordinates are created automatically in this example)
+for i in range(3):
+ DIALOG=gom.script.sys.create_user_defined_dialog (dialog='dialog definition')
+
+ #
+ # Event handler function called if anything happens inside of the dialog
+ #
+ def dialog_event_handler (widget):
+ pass
+
+ DIALOG.handler = dialog_event_handler
+
+ RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+
+ print (RESULT.elementnameWidget)
+
+ MCAD_ELEMENT=gom.script.primitive.create_point (
+ name=RESULT.elementnameWidget,
+ point={'point': gom.Vec3d (i+10.0, 0.0, 0.0)}
+ )
+```
+
+| Property | Type | Example |
+| -------- | ----- | ------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.inputEleName.tooltip = 'Enter the number of points!'
|
+| enabled | bool |
DIALOG.inputEleName.enabled = False
|
+| value | int |
DIALOG.inputEleName.value = 'Blob'
|
+| focus | bool |
DIALOG.inputEleName.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputEleName.visible = False
|
+| basename | str |
DIALOG.inputEleName.basename = 'Point'
|
+| mode | str |
# Mode to get the name suggestion from. ('manually', 'from_element_type', 'check_like') DIALOG.inputEleName.mode = 'from_element_type'
|
+| read_only | bool |
# Keep user from changing the default DIALOG.inputEleName.read_only = true
|
+
+#### Integer widget
+
+
+
+Integer widget
+: The Integer widget is used to request an integer value from the user. `integerWidget` is the object name of the integer widget in the example below.
+
+``` python
+RESULT=gom.script.sys.execute_user_defined_dialog (content='dialog definition')
+userInput = RESULT.integerWidget
+```
+
+| Property | Type | Example |
+| -------- | ------ | ---------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.inputInt.tooltip = 'Enter the number of points!'
|
+| enabled | bool |
DIALOG.inputInt.enabled = False
|
+| value | int |
if DIALOG.inputInt.value < 15:
|
+| focus | bool |
DIALOG.inputInt.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputInt.visible = False
|
+| minimum | double |
DIALOG.inputInt.minimum = 20
|
+| maximum | double |
DIALOG.inputInt.maximum = 50
|
+
+#### Decimal widget
+
+
+
+Decimal widget
+: The Decimal widget is used to request a floating point value from the user. It is possible to choose the number of digits and a unit. The selectable units are the ones from the user preferences (Edit \> Application \> Settings \> Preferences) in the _Default units_ tab. `decimalWidget` is the object name of the decimal widget in the example below.
+
+``` python
+RESULT=gom.script.sys.execute_user_defined_dialog (content='dialog definition')
+userInput = RESULT.decimalWidget
+```
+
+| Property | Type | Example |
+| --------- | ------ | ------------------------------------------------------------------------ |
+| tooltip | str |
DIALOG.input.tooltip = 'Enter distance between points!'
|
+| enabled | bool |
DIALOG.input.enabled = False
|
+| value | int |
if DIALOG.input.value < 15:
|
+| focus | bool |
DIALOG.input.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.input.visible = False
|
+| minimum | double |
DIALOG.input.minimum = 20
|
+| maximum | double |
DIALOG.input.maximum = 50
|
+| precision | double |
# Set precision to 2 decimals DIALOG.input.precision = 2
|
+| unit | str |
# Set unit ID DIALOG.input.unit = 'LENGTH'
|
+
+% No visible effect:
+% background_style - str - Set style sheet based background color - red, green, blue
+
+#### Text entry field
+
+
+Text entry field
+: The Text entry field widget can be used to get string input from the user. A simple use case is given by the next code block. `textEntryWidget` is the object name of the widget in the example below.
+
+``` python
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+DIALOG.textEntryWidget = "some default text"
+RESULT = gom.script.sys.show_user_defined_dialog(dialog = DIALOG)
+print( RESULT.textEntryWidget ) # the user input string
+```
+
+| Property | Type | Example |
+| --------- | ----- | -------------------------------------------------------------------------- |
+| tooltip | str |
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputString.visible = False
|
+| read_only | bool |
if DIALOG.inputString.read_only:
|
+| password | bool |
# Hide user input by replacing each character by a dot DIALOG.inputString.password = True
|
+
+#### Slider widget
+
+
+
+Slider widget
+: The Slider widget can be used to get a float value from a certain interval from the user. `sliderWidget` is the object name of the slider widget in the example below.
+
+``` python
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+
+RESULT = gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+print( RESULT.sliderWidget ) # some text
+```
+
+| Property | Type | Example |
+| ------------- | ------ | -------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.input.tooltip = 'Drag slider to change rotation'
|
+| enabled | bool |
DIALOG.input.enabled = True
|
+| value | str |
print('Angle:', str(DIALOG.input.value))
|
+| focus | bool |
DIALOG.input.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.input.visible = False
|
+| minimum | double |
DIALOG.input.minimum = -90
|
+| maximum | double |
DIALOG.input.maximum = 90
|
+| precision | double |
# Set precision to 1 decimal DIALOG.input.precision = 1
|
+| step | double |
# Set step size to 15 DIALOG.input.step = 15
|
+| orientation | str |
print(DIALOG.input.orientation)
⚠️ read-only |
+
+% ticks are not drawn:
+% tick_interval - double - Interval of ticks drawn
+
+
+#### Checkbox widget
+
+
+
+Checkbox widget
+: The Checkbox widget can be used to get boolean input from the user. `checkboxWidget` is the object name of the checkbox widget in the example below.
+
+``` python
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+print (RESULT.checkboxWidget)
+```
+
+| Property | Type | Example |
+| --------- | ----- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.inputCheckbox.tooltip = 'Check this option to clear the results after evaluation.'
|
+
+#### File widget
+
+
+
+File widget
+: By clicking the File widget, a file selection dialog is opened. This allows to select a file from the file system.
+
+
+| Property | Type | Example |
+| --------- | ----- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.inputFile.tooltip = 'Select a file for the protocol'
|
+| enabled | bool |
DIALOG.inputFile.enabled = False
|
+| value | str |
if DIALOG.inputFile.value != '':
|
+| focus | bool |
DIALOG.inputFile.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputFile.title = 'Select the location for the protocol files'
|
+| default | str |
DIALOG.inputFile.default = 'D:/data/default.txt'
|
+| file | str |
print(DIALOG.inputFile.file)
|
+| file_types | list |
# Show only specified file types; each list item must consist of \[\, \\] DIALOG.inputFile.file_types = \[\['*.g3d', 'Mesh data'\], \['*.stp', 'CAD data'\]\]
⚠️ ``limited`` must be set to ``True`` in order to apply the filter! |
+| limited | bool |
# Limit file selection to 'file_types' DIALOG.inputFile.limited = True
|
+
+% Clarify this:
+% selection_type - str - File selector type; any, directory, executable, file, multi_file
+
+#### Date widget
+
+
+
+Date widget
+: The Date widget requests a date from the user. `dateWidget` is the object name of the date widget in the example below.
+
+``` python
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+dateObject = DIALOG.dateWidget.value # date object
+print( DIALOG.dateWidget.year ) # integer
+print( DIALOG.dateWidget.month ) # integer
+print( DIALOG.dateWidget.day ) # integer
+```
+
+| Property | Type | Example |
+| ----------------- | --------- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputDate.visible = False
|
+| use_current_date | bool |
DIALOG.inputDate.use_current_date = True
💡 if set, use current date to initialize widget. |
+| year | int |
DIALOG.inputDate.year = 2014
|
+| month | int |
DIALOG.inputDate.month = 12
|
+| day | int |
DIALOG.inputDate.day = 24
|
+| show_today_button | bool |
DIALOG.inputDate.show_today_button = True
|
+
+
+#### Color widget
+
+
+
+Color widget
+: The Color widget allows to select a color. `colorWidget` is the object name of the color widget in the example below. `gomColor` behaves in the same way as `gom.Color( ... )`.
+
+``` python
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+
+#
+# Event handler function called if anything happens inside of the dialog
+#
+def dialog_event_handler (widget):
+ if widget == DIALOG.colorWidget:
+ gomColor = DIALOG.colorWidget.color
+ print( gomColor) # output: gom.Color (#ffffffff)
+
+DIALOG.handler = dialog_event_handler
+
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+print('Selection:', RESULT.colorWidget) # example output (white): 0xffffffff
+```
+
+| Property | Type | Example |
+| -------------------- | --------- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.inputColor.tooltip = 'Select a color for the marks.'
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputColor.visible = False
|
+| transparency_allowed | bool |
DIALOG.inputColor.transparency_allowed = True
|
+
+#### Unit widget
+
+
+
+Unit widget
+: The Unit widget allows to select a unit. `unitWidget` is the object name of the color widget in the example below.
+
+``` python
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+
+#
+# Event handler function called if anything happens inside of the dialog
+#
+def dialog_event_handler (widget):
+ if widget == DIALOG.unitWidget:
+ unit = DIALOG.unitWidget.value
+ print( unit) # ANGLE
+
+DIALOG.handler = dialog_event_handler
+
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+```
+
+| Property | Type | Example |
+| -------------------- | --------- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.inputUnit.tooltip = 'Select a unit.'
|
+| enabled | bool |
DIALOG.inputUnit.enabled = True
|
+| value | (special) |
print('Unit ID:', DIALOG.inputUnit.value)
|
+| focus | bool |
DIALOG.inputUnit.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.inputUnit.visible = False
|
+
+#### Selection element widget
+
+
+
+Selection element widget
+: The Selection element widget can be used to select the elements from the element explorer. The following element types can be chosen:
+ * Any Point
+ * Point element
+ * Line element
+ * Plane element
+ * Direction
+ * User-defined
+ `elementSelectionWidget` is the object name of the element selection widget in the example below.
+
+``` python
+DIALOG=gom.script.sys.execute_user_defined_dialog (content='dialog definition')
+
+selectedElement = DIALOG.elementSelectionWidget
+print(selectedElement.value ) # output: gom.app.project.inspection['Equidistant Surface Points 1']
+```
+
+| Property | Type | Example |
+| -------- | --------- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.selectElement.tooltip = 'Select a line for rotation'
|
+| enabled | bool |
DIALOG.selectElement.enabled = False
|
+| value |(special) |
if DIALOG.selectElement.value != None:
|
+| focus | bool |
DIALOG.selectElement.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
|
+| filter | function | Element filter function for the 'custom' supplier. See example below. |
+
+The following script shows how to use a custom filter for element selection. The example filter allows the user to select a system plane:
+
+``` python
+DIALOG4=gom.script.sys.create_user_defined_dialog (content='...')
+
+
+def dialog_event_handler (widget):
+ pass
+
+# filter system planes
+def element_filter( element ):
+ try:
+ if element.type == 'plane':
+ return True
+ except Exception as e:
+ pass
+ return False
+
+DIALOG4.handler = dialog_event_handler
+DIALOG4.input_new.filter = element_filter
+
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG4)
+
+print("Chosen system plane:", RESULT.input_new.name)
+```
+
+The complete code of the example is attached to this document.
+
+% To Do: attach example
+
+#### Selection list widget
+
+
+
+Selection list widget
+: The Selection list widget allows to make a selection from a predefined set of options. The selected item can be accessed from a script through its object name (e.g. `selectionListWidget`) as follows.
+
+``` python
+selectedValue = DIALOG.selectionListWidget.value
+print( selectedValue ) # output: entry2
+```
+
+| Property | Type | Example |
+| -------- | ----------- | ---------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.selectEntry.tooltip = 'Select one of the operating modes'
|
+| enabled | bool |
DIALOG.selectEntry.enabled = False
|
+| value | str |
DIALOG.selectEntry.value = 'Debug'
|
+| focus | bool |
DIALOG.selectEntry.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
|
+
+
+#### Button widget
+
+
+
+
+
+Button widget
+: The Button widget allows to trigger an event or to return a boolean value, respectively. There are two types of buttons: push buttons and toggle buttons. The push button is a regular button and needs an event handler to manage its action. The toggle button has two states - active and inactive - and the user can toggle between them by clicking the button. The button is highlighted in active state as shown in the screenshot. The state of the toggle button can be accessed as follows.
+
+``` python
+toggleButtonState = DIALOG.toggleButtonWidget.value
+print(toggleButtonState) # output: True
+```
+
+The buttons size and icon can be changed in the Dialog Editor.
+
+| Property | Type | Example |
+| ---------------- | ---- | --------------------------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.button.tooltip = 'Click to start evaluation'
|
+| enabled | bool |
DIALOG.button.enabled = False |
+| value | bool |
if DIALOG.button.value:
💡 Only for toggle button! |
+| text | str |
DIALOG.button.text = 'Click here!' |
+| type | str |
# Possible values: 'default', 'large', 'extra_large' DIALOG.button.icon_system_size = 'extra_large'
|
+| visible | bool |
DIALOG.button.visible = False
+
+💡 There are also values for file icons. These only work straightforward using the dialog designer but not from a script. You can only change between no icon and system icons in a straightforward way.
+
+#### Radio button widget
+
+
+
+Radio button widget
+: The Radio button widget enables the user to choose an option from a predefined set. Each option has a label and a unique ID, which both can be set in the scripting dialog editor by double clicking the widget. The IDs are 'ONE', 'TWO' and 'THREE' in the example below.
+
+``` python
+selectedChoice = DIALOG.radiobuttonsWidget.value
+print( selectedChoice ) # output: ONE
+
+if selectedChoice == 'ONE':
+ print("IDs are strings.") # output: IDs are strings.
+```
+
+| Property | Type | Example |
+| -------- | -------------- | --------------------------------------------------------------------------------------------------------------------- |
+| tooltip | str |
DIALOG.radiobuttons.tooltip = 'Choose one alternative!'
|
+| enabled | bool |
DIALOG.radiobuttons.enabled = False
|
+| value | str |
DIALOG.radiobuttons.value = 'Value3'
|
+| visible | bool |
DIALOG.radiobuttons.visible = False
|
+| items | (special list) |
# Possible values is a list of lists of two strings. # Each first string is the returned value # Each second string is the entries' title DIALOG.radiobuttons.items = [['Value1', 'Title1'], ['Value2', 'Title2'], ['Value3', 'Title3']] DIALOG.radiobuttons.default = 'Value2'
|
+| default | str |
DIALOG.radiobuttons.default = 'Value1'
|
+
+
+#### Abort button widget
+
+
+
+Abort button widget
+: The Abort button widget aborts the current action. It is disabled if no action is currently executed. It behaves in the same manner as the abort button in the lower right corner of the ZEISS Inspect software.
+
+
+
+% To Do: Add enabled abort button. Check if the button still exists in ZEISS Inspect.
+
+#### Tolerances widget
+
+
+
+Tolerances widget
+: The Tolerances widget is a group of input widgets which allows to configure all parameters related to tolerances.
+
+| Property | Type | Example |
+| ---------------- | --------------------- | ---------------------------------------------------------------------------------------- |
+| tooltip | str |
|
+| value | (unspecified/various) | The current value of the widget. Type depends on the widget type and can be 'none' for empty widgets. |
+| focus | bool |
DIALOG.tolerancesWidget.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.tolerancesWidget.visible = False
|
+| expanded | bool |
# Check if widged is expanded if DIALOG.tolerancesWidget.expanded == True:
# Set unit ID DIALOG.tolerancesWidget.unit = 'LENGTH' |
+
+#### File system browser widget
+
+
+
+File system browser widget
+: The File system browser widget allows to view the file system and to select a file or a set of files, respectively. A filter can be set to show only files with certain filename extensions.
+
+| Property | Type | Example |
+| ------------------ | --------------------- | -------------------------------------------------------------------------------------- |
+| tooltip | str |
|
+| value | (unspecified/various) | The current value of the widget. Type depends on the widget type and can be 'none' for empty widgets. |
+| focus | bool |
DIALOG.filesystemWidget.focus = True
⚠️ Only works if dialog is open |
+| visible | bool |
DIALOG.filesystemWidget.visible = False
|
+| root | str |
DIALOG.filesystemWidget.root = 'C:/Users'
|
+| show_date | bool |
DIALOG.filesystemWidget.show_date = True
|
+| show_size | bool |
DIALOG.filesystemWidget.show_size = True
|
+| show_type | bool |
DIALOG.filesystemWidget.show_type = True
|
+| use_multiselection | bool |
# Enable selection of multiple files DIALOG.filesystemWidget.use_multiselection = True
|
+| selected | list |
print(DIALOG.filesystemWidget.selected) # example output: \['C:/temp/Basic_Training_GOM_Inspect_Pro/Training Data/Raw Data/Actual/GOM Training Object Mesh 1.g3d', 'C:/temp/Basic_Training_GOM_Inspect_Pro/Training Data/Raw Data/Actual/GOM Training Object Mesh 2.g3d'\]
|
+| filter | list |
# Apply a filter of filename extensions DIALOG.filesystemWidget.filter = \[ '\*.g3d', '\*.stp' \]
|
+
+## Executing dialogs
+
+- [Dialog commands](#dialog-commands)
+ - [Break dialog (`execute`)](#break-dialog-execute)
+ - [Extendable break dialog (`create` and `show`)](#extendable-break-dialog-create-and-show)
+ - [Info dialog (`create`, `open` and `close`)](#info-dialog-create-open-and-close)
+- [Dialog results](#dialog-results)
+ - [Custom results](#custom-results)
+- [Configuring dialog widgets](#configuring-dialog-widgets)
+- [Event handler functions](#event-handler-functions)
+ - [Registering event handlers](#registering-event-handlers)
+ - [Closing dialogs from within the event handler](#closing-dialogs-from-within-the-event-handler)
+ - [Using a timer to activate the event handler](#using-a-timer-to-activate-the-event-handler)
+- [Determining the existing widget attributes](#determining-the-existing-widget-attributes)
+
+### Dialog commands
+
+#### Break dialog (`execute`)
+
+
+
+* Standard case of a dialog.
+* The dialog is created and executed with a single command.
+* The command blocks the script until the dialog is closed again.
+* The dialog result is returned.
+
+
+
+``` python
+RESULT=gom.script.sys.execute_user_defined_dialog (dialog={
+ "content": [
+ [
+ {
+ "columns": 1,
+ "name": "label",
+ "rows": 1,
+ "text": {
+ "id": "",
+ "text": "Distance",
+ "translatable": True
+ },
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "label",
+ "word_wrap": False
+ },
+ {
+ "background_style": "",
+ "columns": 1,
+ "maximum": 1000,
+ "minimum": 0,
+ "name": "inputDistance",
+ "precision": 2,
+ "rows": 1,
+ "tooltip": {
+ "id": "",
+ "text": "",
+ "translatable": True
+ },
+ "type": "input::number",
+ "unit": "",
+ "value": 0
+ }
+ ]
+ ],
+ "control": {
+ "id": "OkCancel"
+ },
+ "embedding": "always_toplevel",
+ "position": "automatic",
+ "size": {
+ "height": 112,
+ "width": 198
+ },
+ "sizemode": "automatic",
+ "style": "",
+ "title": {
+ "id": "",
+ "text": "Distance",
+ "translatable": True
+ }
+})
+
+```
+
+#### Extendable break dialog (`create` and `show`)
+
+
+
+* A dialog is created and executed by subsequent commands.
+* This way, the created dialog can be modified by the script right before execution.
+
+```{code-block} python
+:caption: Creating and executing a dialog with two separate commands
+
+# Create dialog, but do not execute it yet
+DIALOG = gom.script.sys.create_user_defined_dialog (content='...')
+
+#
+# The dialog has been created. At this point of the script, the dialog handle DIALOG
+# can be used to access and configure dialog parts
+#
+
+# Execute dialog and fetch execution result
+RESULT = gom.script.sys.show_user_defined_dialog( dialog = DIALOG )
+```
+
+#### Info dialog (`create`, `open` and `close`)
+
+
+
+* In this mode, the script execution continues after the dialog has been opened.
+* The sequence of commands is as follows:
+ * the `create` command creates a dialog. The dialog can be configured now. Afterwards
+ * the `open` command is issued to display the dialog. The script executing continues. At last
+ * the `close` command closes the dialog again, if no closed manually by the user yet.
+
+💡 At script termination all open dialogs are closed automatically.
+
+```{code-block} python
+:caption: Non blocking configurable dialogs
+
+# Create dialog but do not execute it yet
+DIALOG = gom.script.sys.create_user_defined_dialog (content='...')
+
+#
+# The dialog has been created. At this point of the script, the dialog handle DIALOG
+# can be used to access and configure dialog parts
+#
+
+# Show dialog. The script execution continues.
+gom.script.sys.open_user_defined_dialog( dialog = DIALOG )
+
+#
+# The dialog content can be modified here, the dialog is still open
+#
+DIALOG.title = 'Stufe 2'
+
+# Close dialog again
+gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+```
+
+### Dialog results
+
+💡 The return value is an object with one property per interactive dialog widget containing its current value.
+
+* The return value is an object containing all current values.
+* Each dialog widget which can be changed by the script user writes its resulting value into this result object.
+* The key for each widget is its object name, which is unique.
+
+
+
+``` python
+#
+# Print whole dialog result. This is a result map with just one entry 'distance', named after
+# the unique name assigned to the spinbox.
+#
+print (RESULT) # Print whole result map
+# output: gom.dialog.DialogResult ('distance': 2.0, 'label': None)
+
+#
+# Print result for the element named 'distance'. This will lead to the spinbox content.
+#
+print (RESULT.distance)
+# output: 2.0
+```
+
+
+
+``` python
+# Print content of the 'name' widget
+print( RESULT.name )
+# output: Line 1
+
+# Print content of the widget named 'point1'. This can again be an element reference.
+print( RESULT.point1 )
+# output: gom.ActualReference (gom.app.project.inspection['Point 5'])
+
+# Print content of the widget named 'point2'.
+print( RESULT.point2 )
+# output: gom.ActualReference (gom.app.project.inspection['Point 6'])
+
+# construct a line with the user input. Therefore our dialog works similar to the 2-point line
+# construction dialog
+MCAD_ELEMENT=gom.script.primitive.create_line_by_2_points (
+ name= RESULT.name,
+ point1 = RESULT.point1,
+ point2 = RESULT.point2)
+```
+
+💡 The type of the result depends on the specific widget.
+
+#### Custom results
+
+You can return custom results from dialogs using an optional parameter to the `close_user_defined_dialog`-function. The following example produces 'Yes'
+and 'No' results for the different buttons and 'Cheater' when the user uses the close button of the dialog.
+
+``` python
+DIALOG = gom.script.sys.create_user_defined_dialog (content='...')
+
+#
+# Event handler function called if anything happens inside of the dialog
+#
+def dialog_event_handler (widget):
+ if widget == DIALOG.button_yes:
+ gom.script.sys.close_user_defined_dialog( dialog = DIALOG, result = 'Yes' )
+ if widget == DIALOG.button_no:
+ gom.script.sys.close_user_defined_dialog( dialog = DIALOG, result = 'No' )
+
+DIALOG.handler = dialog_event_handler
+
+try:
+ RESULT = gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+except gom.BreakError as e:
+ RESULT = 'Cheater'
+
+print('RESULT', RESULT)
+```
+
+Please find the complete example here: [dialog_yes_no.py](assets/dialog_yes_no.py)
+
+### Configuring dialog widgets
+
+* Dialogs created with the `create` and `open` commands can be modified before executed.
+* Each widget in the dialog can be accessed via the dialog handle.
+* The widget is identified by its unique name.
+
+```{code-block} python
+:caption: Configuring dialog widgets
+
+# Create dialog and receive dialog handle
+DIALOG = gom.script.sys.create_user_defined_dialog (content='...')
+
+# The handle for a widget inside of the dialog is addressed by its unique name
+WIDGET = DIALOG.distance
+
+# The widget parameter can be set via widget attributes. 'Value', for instance, relates to the current widget value.
+WIDGET.value = 3.0
+```
+
+* All widgets share some common standard attributes:
+
+| Attribute | Type | Property |
+| --------- | ------------------- | ----------------------------------------- |
+| name | str | Unique name of the widget - do not write! |
+| enabled | bool | Widget is currently active / inactive |
+| value | (depends on widget) | Current value |
+
+For the type of the value property for a specific widget, see section [Specific widgets](#specific-widgets) above. For widgets which are not used to enter some value, `value` is `None` and read-only. In addition, widgets have further attributes depending on their type (see section [Specific widgets](#specific-widgets) above for details).
+
+```{code-block} python
+:caption: Accessing widget attributes
+
+# Create dialog but do not execute it yet
+DIALOG=gom.script.sys.create_dialog (content='...')
+
+# Set name to 'default name' and disable 'ok' button
+DIALOG.name.value = "default name"
+DIALOG.control.ok.enabled = False
+
+# Execute dialog
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+```
+
+### Event handler functions
+
+#### Registering event handlers
+
+* A function can be registered to the dialog called on value changed.
+* Every time the user modified a dialog value, the **handler** function is called.
+* The handler function is also called on application global signals, e.g. when application data has been changed. In these cases is the string `'system'` passed to the handler function. Those global signals are caused by changing the element selection or opening a project for example.
+* The handler function can access dialog widget properties.
+* The handler function is registered using the special attribute `handler`.
+* The **prev** and **next** buttons of a wizard dialog are the only control widgets, which trigger the event handler.
+
+```{code-block} python
+:caption: Dialog handler functions
+
+DIALOG=gom.script.sys.create_user_defined_dialog (content='dialog definition')
+
+# Handler function registered to the dialog
+def handler_function (widget):
+ # Print information about the modified widget
+ print ("Modified:", str (widget))
+ # If the 'name' widget is empty, the 'ok' button is disabled.
+ if DIALOG.name.value == "":
+ DIALOG.control.ok.enabled = False
+ else:
+ DIALOG.control.ok.enabled = True
+
+ if str(widget) == 'system':
+ print("It is a global event.")
+ elif str(widget) == 'initialize':
+ print("Dialog is displayed for the first time.")
+
+# Register dialog handler
+DIALOG.handler = handler_function
+
+# Execute dialog
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+```
+
+A complete example with a handler function can be found in the file [scriptingEditorExampleDialog.py](assets/scriptingEditorExampleDialog.py). The argument passed to the event handler is either the dialog widget (e.g. a button) which triggered the event handler or a string. The following table lists all possible strings:
+
+| Value | Description |
+| ------------ | ---------------------------------------------------------------------------- |
+| 'system' | Passed to the event handler in the case of a global event. |
+| 'timer' | Passed to the event handler in the case of a global event. |
+| 'initialize' | Passed to the event handler when the dialog is displayed for the first time. |
+
+If the widget parameter is not a string, it represents a widget object. Note, that you cannot use the `is` operator on these objects. Always use `==` and similar
+operators to compare the widget parameter:
+
+```{code-block} python
+:caption: Comparing widget parameters
+
+def handler_function (widget):
+ ...
+ # compare widget using "==", using "is" will not work!
+ if widget == DIALOG.textInput:
+ if DIALOG.textInput.value == "":
+ DIALOG.control.ok.enabled = False
+ else:
+ DIALOG.control.ok.enabled = True
+```
+
+#### Closing dialogs from within the event handler
+
+💡 Dialogs can be closed from within event handlers.
+
+
+
+```{code-block} python
+:caption: Button event handler
+
+def dialog_event_handler (widget):
+ if widget == DIALOG.button1:
+ execute_func_1 ()
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+ elif widget == DIALOG.button2:
+ execute_func_2 ()
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+ elif widget == DIALOG.button3:
+ execute_func_3 ()
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+```
+
+⚠️ Right after the dialog has been closed its handle becomes invalid.
+
+This implies, that the event handler function must be written in a way that no dialog dependent code is executed after the dialog has been closed.
+
+#### Using a timer to activate the event handler
+
+Each `DIALOG` has a special property named `DIALOG.timer`. This timer property can be used to trigger the event handler registered to `DIALOG` in
+certain time intervals. When the event handler is triggered by the timer, the string `timer` is passed to it. The `__doc__`-string of the timer gives information
+about its attributes:
+
+``` python
+print(DIALOG.timer.__doc__)
+# output:
+# Timer
+#
+# Attributes:
+# enabled (boolean) - timer enabled
+# interval (integer) - timer interval [ms]
+```
+
+💡 Please note that the timer is disabled by default.
+
+Example:
+
+
+
+```{code-block} python
+:caption: Button/Timer event handler
+
+DIALOG=gom.script.sys.create_user_defined_dialog (content='boring dialog definition')
+
+#
+# Event handler function called if anything happens inside of the dialog
+#
+state = False
+def dialog_event_handler (widget):
+ global state
+ if widget == DIALOG.start:
+ DIALOG.timer.interval = DIALOG.interval.value * 1000
+ DIALOG.timer.enabled = True
+ DIALOG.start.enabled = False
+ DIALOG.stop.enabled = True
+ elif widget == DIALOG.stop:
+ DIALOG.timer.enabled = False
+ DIALOG.start.enabled = True
+ DIALOG.stop.enabled = False
+ elif widget == DIALOG.interval:
+ DIALOG.timer.interval = DIALOG.interval.value * 1000
+ elif widget == DIALOG.exit:
+ gom.script.sys.close_user_defined_dialog (dialog=DIALOG)
+ elif str(widget) == 'system':
+ print("Its a system event.")
+ elif str(widget) == 'timer':
+ print("Its a timer event. Let´s swap the image.")
+ state = not state
+
+ if state:
+ DIALOG.image.system_image = 'system_message_warning'
+ else:
+ DIALOG.image.system_image = 'system_message_question'
+
+DIALOG.handler = dialog_event_handler
+DIALOG.stop.enabled = False
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+```
+
+The complete code of the example can be found here: [timer.py](assets/timer.py).
+
+### Determining the existing widget attributes
+
+* Because Python is a very dynamic language, the type of a variable or attribute can not be determined statically.
+* Instead, it is possible to query the variable dynamically during runtime.
+* The more commonly used widget attributes are documented in the section [Specific widgets](#specific-widgets) above.
+
+💡 Most objects support the attribute `__doc__` which prints the available object documentation to the console.
+
+```{code-block} python
+:caption: Print object documentation
+
+#
+# Query __doc__ attribute of a button widget
+#
+print (DIALOG.my_button.__doc__)
+# output:
+# Handle for a widget called 'my_button' of type 'Button' (button::pushbutton)
+#
+# Attributes:
+# name (string) - Name of the widget. The name can be used to access the widget via a dialog handle.
+# tooltip (string) - Tooltip of the widget. If empty, no tooltip is displayed.
+# enabled (boolean) - Enabled state of the widget. Default is 'enabled', set to false for disabling it.
+# value (unspecified/various) - The current value of the widget. Type depends on the widget type and can be 'none' for empty widgets.
+# attributes (map) - Map of all accessable widget attributes together with their current values.
+# focus (boolean) - Focus state of the widget. Can be used to set an explicit widget focus.
+# text (string) - Text of the button
+# type (string) - Button type ('push', 'toggle')
+# icon (Tom::Parse::Binary) - Icon of the button
+# icon_file_name (string) - Source file name of the icon
+# icon_size (string) - Icon size mode (icon, full)
+# icon_type (string) - Icon type (none, system, file)
+# icon_system_type (string) - System icon type (ok, cancel, arrow_up, arrow_down, arrow_left, arrow_right)
+# icon_system_size (string) - System icon size (default, large, extra_large)
+```
+
+## Wizards
+
+- [Control widgets](#control-widgets)
+
+* **Wizards** are dialogs with **\< Back** and **Next \>** buttons at the lower dialog edge.
+* The script programmer is responsible for adding functionality to this layout.
+* Wizards are not very versatile, but modifying the displayed texts and images is easily possible.
+
+⚠️ It is not possible to exchange widgets from within a dialog after the dialog has been created!
+
+Therefore Wizards only have simple options like exchange of images and texts in those containing elements.
+
+### Control widgets
+
+The operational elements in a control widget from a wizard do act like those in regular dialogs und can be accessed via handles as well:
+
+
+
+```{code-block} python
+:caption: Wizard example
+
+#
+# Create dialog with wizard control panel
+#
+DIALOG=gom.script.sys.create_user_defined_dialog (content='boring dialog definition')
+#
+# Handler function to be registered to the dialog
+#
+def func (widget):
+ #
+ # Handle clicks onto the 'prev' button
+ #
+ if widget == DIALOG.control.prev:
+ # Here you would write code to display the content of the previous wizard 'page'
+
+ #
+ # Handle clicks onto the 'next' button
+ #
+ print("Prev button was clicked.")
+ elif widget == DIALOG.control.next:
+ # Here you would write code to display the content of the next wizard 'page'
+
+ #
+ # Update dialog button enabled state and register handler function
+ #
+ print("Next button was clicked.")
+
+DIALOG.handler = func
+
+#
+# Execute wizard dialog
+#
+RESULT=gom.script.sys.show_user_defined_dialog (dialog=DIALOG)
+```
+
+[Creating wizard dialogs](creating_wizard_dialogs.md) shows some ways to manage wizard dialogs in greater detail.
diff --git a/2022-new-headings-intros/_sources/howtos/python_api_introduction/using_script_resources.md.txt b/2022-new-headings-intros/_sources/howtos/python_api_introduction/using_script_resources.md.txt
new file mode 100644
index 0000000..a54ef22
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/python_api_introduction/using_script_resources.md.txt
@@ -0,0 +1,31 @@
+# Using script resources
+
+The term "resource" is used to describe any files in your scripts directories that are not python scripts (`*.py`). You can use these files to include binary data such as images or other data like config files etc. in your add-ons.
+
+## Importing resources
+
+The resources files in your scripts directory are automatically recognized as such. You can as well add (import) resources using the context menu of the script editor.
+
+
+
+## Usage in scripts
+
+To get access to resource data in a script, the qualified name or relative path to the resource is needed.
+The qualified name starts with a `:` followed by the top-level folder and the path to the resource, e.g. `:PythonApiExamples/examples/script_resources/test_resource.txt`. You can also use a relative path to the currently executed script.
+
+```{hint}
+When using relative paths, the path is resolved to the script *currently executed*. This is not inevitably the script containing the `gom.Resource` call. E.g., when you import a script (A) containing a `gom.Resource` call in another script (B) and then execute the script (B), script (B) will be the *currently executed* one. In this case, usage of qualified names is advised.
+```
+
+Suppose you created a script called `resource_example.py` in a folder next to `test_resource.txt`. In the script, you can read the data in the following way:
+
+```python
+res = gom.Resource ("test_resource.txt")
+if (res.exists()):
+ print (res.open().read())
+```
+
+## See also
+
+* [Examples of category `script_resources`](../../python_examples/script_resources.md)
+* [`gom.Resource` API Definition](../../python_api/resource_api.md)
\ No newline at end of file
diff --git a/2022-new-headings-intros/_sources/howtos/scripted_elements/scripted_actuals.md.txt b/2022-new-headings-intros/_sources/howtos/scripted_elements/scripted_actuals.md.txt
new file mode 100644
index 0000000..36ae266
--- /dev/null
+++ b/2022-new-headings-intros/_sources/howtos/scripted_elements/scripted_actuals.md.txt
@@ -0,0 +1,108 @@
+# Scripted actuals
+
+
+
+Scripted actual elements (short: scripted actuals), are scripted elements that refer to the actual, e.g. measured state of a geometrical object. Therefore, they appear in the "Actual Element" category of the GOM Inspect Element Explorer.
+
+In this how-to, the creation of a very basic point element is presented to show how scripted actuals are developed by example.
+
+## Example: Simple offset point
+
+Assume we want to create a scripted point. A point, whose position is just offsetted by a couple of millimeters from another point. Though the use of such element is clearly limited, it serves as an easy example on the general approach.
+
+As explained in the previous chapter, at first we select the element type in the script properties. For our offset-point, we naturally choose "Actual element" -> "Point".
+
+
+
+Then, we write the code, which needs a `dialog` and a `calculation` function. Let's begin with the `dialog` function.
+
+### `dialog`
+
+```{code-block} python
+---
+linenos:
+---
+def dialog(context, params):
+
+ DIALOG=gom.script.sys.create_user_defined_dialog (dialog={