Project

General

Profile

Actions
Copy link

Support Request #12014

closed

EBPRODUCTSUPPORT-7810 Failed to set map property using SCFE

Added by hidden over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Customer:
ELEKTROBIT
Department:
SUPPORT
Requester's Priority:
Normal
Support Level:
2nd Level
Resolution:
Duplicate Issue
Product Issue Numbers:

https://support.digitalwerk.net/issues/11974

Affected Products:
ADTF 3.8.0, ADTF Device Toolbox 3.2.0, ADTF Device Toolbox 3.3.0
Platform:
Windows 10 64bit
Topic:
DeviceTB::Common
FAQ Links:

Description

Supportanfrage

One of our colleagues found a bug of the device toolboxes (same for 3.2 and 3.3) in combination with ADTF 3.8:

In Configuration Editor, add a CAN Config Decoder Filter. Add Can Support Service and set a dbc file. Right Click and select CAN Signal Config Editor and create and save a configuration.
After closing the Editor the pins are correctly created according to the Configuration but the MapFilename in the Properties of the filter is set to some internal Qt command. So launching fails. See pic.
[cid:]
In ADTF 3.7 and Device Toolbox 3.2. the MapFilename was correctly set to the saved file path. So obviously this is a bug related to the new Qt version.

Lösung

Der Bug kam in der 3.8 mit den linked graph properties und wurde zur 3.9 im Zuge des redesigns gleich mit gefixt, dafür gab es kein explizites Ticket.
Workaround für 3.8 ist das Setzen via Property editor, nur der Close des SCFE sorgt dafür, hier haben wir was auf QML Seite übersehen...

Files

image001.png (28.6 KB) image001.png hidden, 2020-09-01 10:15
Actions
Copy link
 #1

Updated by hidden over 3 years ago

  • Project changed from Public Support to 7
  • Status changed from New to In Progress
  • Topic set to DeviceTB::Common
  • Customer set to ELEKTROBIT
  • Department set to SUPPORT
  • Affected Products ADTF 3.8.0, ADTF Device Toolbox 3.2.0, ADTF Device Toolbox 3.3.0 added
  • Platform Windows 10 64bit added
Actions
Copy link
 #2

Updated by hidden over 3 years ago

  • Resolution set to Known Problem

Unfortunatly that seems to be a (already known) bug, which will be fixed within the next ADTF 3.9 version.
As a workaround you have to manually set the property once again.

The new version will hopefully released within the next weeks

Actions
Copy link
 #3

Updated by hidden over 3 years ago

  • Status changed from In Progress to To Be Closed
  • Resolution changed from Known Problem to Duplicate Issue
  • Product Issue Numbers set to https://support.digitalwerk.net/issues/11974
Actions
Copy link
 #4

Updated by hidden over 3 years ago

Hi Benedict,

could you give us the Bug-ID? I looked up https://support.digitalwerk.net/projects/download-center/wiki/KnownProblems but guess there are no recent updates there.

Interesting information that you plan directly for 3.9.

Grüße,
Jochen

Actions
Copy link
 #5

Updated by hidden over 3 years ago

unfortunatly i neither have nor find the requested bug-id. I will ask the person in charge on monday

Actions
Copy link
 #6

Updated by hidden over 3 years ago

Hi,

any news regarding the bug ID? Because the case is set to "to be closed"?

BR, Anja

Actions
Copy link
 #7

Updated by hidden over 3 years ago

Hi supporters,

looks like the ADTF 3.9 provides a reworked property editor. The release notes do not mention this bug explicitely. So I guess one has to check again whether the bug is removed.

Could you verify whether the bug is removed in version 3.9/Device TB 3.3?

BR,
Jochen

Actions
Copy link
 #9

Updated by hidden over 3 years ago

  • Status changed from To Be Closed to In Progress

Hallo Patrick,
kannst Du Dir das bitte nochmal ansehen? Siehe Auch verlinktes Ticket.
Die Lösung sollte bereits korrekt im ADTF 3.9 Release enthalten sein.
Danke

Actions
Copy link
 #10

Updated by hidden over 3 years ago

Matthias Fick-Gredler wrote:

Hallo Patrick,
kannst Du Dir das bitte nochmal ansehen? Siehe Auch verlinktes Ticket.
Die Lösung sollte bereits korrekt im ADTF 3.9 Release enthalten sein.
Danke

Habe es mit ADTF 3.9.0 und DeviceTB 3.3.0 ausprobiert. Bei mir tritt der Fehler nicht auf.

Actions
Copy link
 #11

Updated by hidden over 3 years ago

  • Status changed from In Progress to Customer Feedback Required

Hallo Jochen,
Hallo Anja,

Lösung sollte in der aktuellen Version enthalten sein.
Wenn von Eurer Seite nicht dagegen spricht, schließen wir damit das Ticket.

Gruß
Matthias

Actions
Copy link
 #12

Updated by hidden over 3 years ago

  • Subject changed from EBPRODUCTSUPPORT-7810 CAN Config Decoder Filter and Signal Config Filter Editor in ADTF 3.8 to EBPRODUCTSUPPORT-7810 Failed to set map property using SCFE
  • Description updated (diff)
  • Status changed from Customer Feedback Required to To Be Closed

Der Bug kam in der 3.8 mit den linked graph properties und wurde zur 3.9 im Zuge des redesigns gleich mit gefixt, dafür gab es kein explizites Ticket.
Workaround für 3.8 ist das Setzen via Property editor, nur der Close des SCFE sorgt dafür, hier haben wir was auf QML Seite übersehen...

Actions
Copy link
 #13

Updated by hidden over 3 years ago

  • Project changed from 7 to Public Support
  • Private changed from Yes to No
Actions
Copy link
 #14

Updated by hidden over 3 years ago

  • Status changed from To Be Closed to Closed
Actions
Copy link

Also available in: Atom PDF