Template:Hauptüberschrift
{{#tree:id=dmxc3|openlevels=1|root=DMXC 3 lessons|
- preamble
- lesson 1: Installation and configuration
- lesson 2: The GUI panel concept
- lesson 3: Creating and patching fixtures
- lesson 4: The live view panel
- lesson 5: Setting properties with property panels
- lesson 6: Output plugins
- lesson 7: Summery and details - Setting
- lesson 8: Scenes (cues) and scene lists
- lesson 9: Fanning, chasers and other effects
- lesson 10: The programmer view
- lesson 11: Trigger concepts
- lesson 12: Editing scenes and scenelists
- lesson 13: Presets
- lesson 14: Summary and details - Programming
- lesson 15: Working with parallel scene lists
- lesson 16: Softpult
- lesson 17: Artnet
- lesson 18: Multi-media: Beamer tool, Matrix etc.
- lesson 19: Other clients and plugins (Android, iOS, ...
- lesson 20: Create new device definitions
- lesson 21: free topic
- lesson 22: Hints for testers and test reporting
- appendix1: Summary of commands ans shortcuts
- appendix2: Kernel menu tree
}}
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 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!
Known Issues
Issue: GUI Elements display glitches
Symptoms:
This could look like shown below: Also if you move windows it happens that thay are not displayed correct. [Dmxc_3_menu_errors.jpg] This can occur if you have a NVidia graphics card and use an old driver version.
Prerequisites:
I experienced this issue with a GeForce G 103M Driver Version 258.96 + PhysX 09.10.0513 on Windows XP x86_64.
Cause:
Don't ask me.
Resolution:
Consider updating the driver to the latest version. Version 266.58 + PhysX 09.10.0514 is known to work.
Issue: Kernel not starting
Symptoms:
Kernel does not start. Quellcode 1 2 3 2013-01-07 12:50:38,692 [Main] ERROR org.dmxc.lumos.Kernel.Resource.Xml2ManagedTreeConverter - Error in Reading KeyValue Pair: Attribute System.InvalidOperationException: Temporäre Klasse kann nicht generiert werden (result=1). error CS0016: In die Ausgabedatei c:\Users\Jens\AppData\Local\Temp\tugsyzgs.dll konnte nicht geschrieben werden -- Zugriff verweigert .
Prerequisites:
Comodo Personal Firewall / Internet security installed
Cause:
Comodo runs Lumos in a sandbox. This sandbox prohibits access to some files or locations. Lumos uses XmlSerializer to (de)serialize objects that it doesn't know. To instantiate a XmlSerializer object the CLR creates temporary assemblies and loads them afterwards. These assemblies are stored in AppData\Local\Temp\ however the sandbox doesn't allow (write) access to this directory (wtf?)
Resolution:
Don't use this crap (i mean comodo not lumos) Put Lumos.exe on the list of trusted applications Should we contact Comodo and try to get on their shipped whitelist? There is the possibility to generate this XmlSerializer assemblies at compile time and then ship them, but plugin authors would need to do the same. Then we get a huge chaos because there are different versions for the same types out. Also this stuff needs to be in the Kernel root dir... Suff from third parties belongs in the plugin dir.
Issue: Grouping of icons ins stage view does not work.
Symptoms:
If you hold down a button (e.g. m for matrix grouping) and move the mouse, the icons are not getting moved. Btw. this is not an issue in regards to Lumos, this symptom also occurs if you try this on your desktop
Prerequisites:
Synaptics Touchpad
Cause:
Synaptics implemented an option called PalmCheck which should reduce cursormovement while typing. Whenever a button is pressed the mouse input gets disabled...
Resolution:
This option can be disabled unter Control Panel->Mice->Device Settings->Settings->(Point)->Sensitivity->PalmCheck
| |||||||||