Appendix 2 Tut3: Difference between revisions

Revision as of 19:12, 6 January 2013

Template:Hauptüberschrift

{{#tree:id=dmxc3|openlevels=1|root=DMXC 3 lessons|

}} Template:NavigationTop-Tut3

Hints for testing and error handling

In this article you will find out what you should do in case of a fault in order to support developers in debugging. You will receive information on how you can check for errors and how and where you can report a bug. But first, you learn something about the targeted search for errors.

An error occurs

You are doing something in DMXControl 3. Then suddenly: Template:Bild mit Unterschrift

The error occurs in the beta is not serious and can happen. Bad it would be if this error is undocumented, because it can not be resolved. Therefore, you should proceed as follows:

Have a look into the Logs panel (Help => Logs). There DMXControl writes information about the latest events. At the bottom now one or more entries as the be seen in Figure 2 are probably present.

Template:Bild mit Unterschrift

Furthermore, these log messages are stored in files. This you should definitely export (Help =>Export log files), because they are needed laterly. Template:Bild mit Unterschrift

If you can reproduce this fault, please report it via bug tracker on DMXControl home page. The bugtracker for DMXControl 3 you can also find directly under http://www.dmxcontrol.de/flyspray/index.php?project=3&do=index&switch=1.

There all errors are collected so that the developers quite easy can see the error and fix it. You can report a fault completely anonymous, but it's better if there are any further questions, to register without any further obligation.

Before you report a bug, please search at first if this bug is already listed in the bug tracker. Is your fault a new one, you can report it via Create new task. Template:Bild mit Unterschrift

Please describe as accurately as possible, as it has come to this error. Please also attach your project and the exported log files to the new task in the bugtracker. Then the developers can fix this soon hopefully. Thanks for your support! Template:NavigationTop-Tut3

Kategorie:DMXControl 3

@@ Line 1: / Line 1: @@
-{{Hauptüberschrift
+ {{Hauptüberschrift
 | logo = Im-aim.png
 | ueberschrift = First Steps: {{PAGENAME}}
@@ Line 5: / Line 5: @@
 {{DMXC3_lesson/en}}
+{{NavigationTop-Tut3
+| zurückLink = Anhang_1_Tut3
+| zurückText = Anhang 1
+| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
+}}
-__NOTOC__
-__NOTITLE__
-{{Hauptüberschrift
-| logo = Im-aim.png
-| ueberschrift = First Steps: {{PAGENAME}}
-}}
-{{DMXC3_lesson/en}}
+===Hints for testing and error handling===
+In this article you will find out what you should do in case of a fault in order to support developers in debugging. You will receive information on how you can check for errors and how and where you can report a bug. But first, you learn something about the targeted search for errors.
-===The kernel menu structure===
+==An error occurs==
+You are doing something in DMXControl 3. Then suddenly:
+{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_Fehlermeldung.png|1|Fehlermeldung in DMXControl 3 Beta|center|700px}}
-The kernel provides a command shell. By typing "help" you get an overview about all supported commands.
-[[File:DMXC3L01 konsole.JPG|600px]]
+The error occurs in the beta is not serious and can happen. Bad it would be if this error is undocumented, because it can not be resolved. Therefore, you should proceed as follows:
+Have a look into the '''Logs panel''' ('''Help''' => '''Logs''').
+There DMXControl writes information about the latest events. At the bottom now one or more entries as the be seen in Figure 2 are probably present.
+{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_Logs.png|2|Logs-Panel von DMXControl 3|center|700px}}
-There are some command options in the command line mode for getting detailed information on the status of the kernel:
-* shutdown: Shut down the kernel.
+Furthermore, these log messages are stored in files. This you should definitely export ('''Help =>'''Export log files'''), because they are needed laterly.
-* status: Displays information about the status
+{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_ExportLogs.png|3|Exportfunktion für die Log-Dateien|center}}
-* menu: Access to control menu
-* clear: Clears the console
-* notification xxx: Sends a notification text to all connected Sessions
-* width xxx: Defines the width of the console (number of characters)
-* load xxx: Loads a project from a file
-* save xxx: Saves current project to a file
-* dmxout [channel, val]+: Sets DMX Out Values
-* dmxin [channel, val]+: Sets DMX In Values
-* help: Help menu (also accessible via "?")
-Additional second level menu commands exists for "menu" and "status".
+If you can reproduce this fault, please report it via '''bug tracker''' on DMXControl home page.
+The '''bugtracker''' for DMXControl 3 you can also find directly under http://www.dmxcontrol.de/flyspray/index.php?project=3&do=index&switch=1.
-menu commands
-* AssemblyManager
+There all errors are collected so that the developers quite easy can see the error and fix it. You can report a fault completely anonymous, but it's better if there are any further questions, to register without any further obligation.
-*
+Before you report a bug, please search at first  if this bug is already listed in the bug tracker. Is your fault a new one, you can report it via '''Create new task'''.
+{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_Bugtracker.png|4|Ansicht des Bugtrackers|center|700px}}
+Please describe as accurately as possible, as it has come to this error. Please also attach your project and the exported log files to the new task in the bugtracker. Then the developers can fix this soon hopefully.
+Thanks for your support!
 __NOTOC__
 __NOTITLE__
 [[de:Anhang 2]]
 [[en:Appendix 2]]
+{{NavigationTop-Tut3
+| zurückLink = Anhang_1_Tut3
+| zurückText = Anhang 1
+| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
+}}
+[[Kategorie:DMXControl 3]]