Support Request #1275
closedADTFS-47871 Serveral bugs or unpexpected behaviour of ADTF 3 Support Toolbox in combination with ADTF Control
Description
Supportanfrage
Hallo,
folgende Probleme mit der ADTF 3 Support Toolbox (version 3.0.0) mit ADTF 3.1.0 sind mir aufgefallen (Windows 7).
Current Behaviour
1. Missing entry in version label of filters
2. Misleading error message from adtf_guicontrol when selecting wrong launcher
3. Initialization/Deinitialization from Gui Control fails (adtf 2.14. crashes). Stop/Run works, but no player available displayed.
4. Suggested improvement: possibility to specify default launcher in session (& default control port would also be nice!!!)
Expected Behaviour
1. Version label should be completed with version,
2. error message should point to launcher selection
3. Gui Control should support init/deinit without crash and allow player control
4. If there is a launcher specified in the session file this one should be taken by default if nothing else is configured later, same for port.
Instructions to reproduce the problem
1. For version label: Add a filter of the ADTF 3 support toolbox to the configuration and inspect the properties.
2. For error message launch example ADTF 2 session in the toolbox ("C:\ADTF\2.14.0_vc100\addons\adtf3-support-toolbox\src\examples\sessions\demo\adtf2\adtf2.adtfsession") from adtf_guicontrol without changing the launcher to adtf2
3. Launch the session from 2 with launcher adtf2 configured. Try init/deinit from ADTF Gui Control (crash). Then init from ADTF control in ADTF 2.14 and try run/stop from ADTF Gui Control.
4. By default always the adtf launcher is used and control port 8000.
Hier noch noch Bilder für Punkt 1. & 2.
[cid:image001.png@01D34766.DA1100A0] [cid:image003.png@01D3476F.31B84C20]
Best regards,
Jochen
Lösung
Produkttickets sind erstellt und verlinkt
Files
