Feature Request: add STEP numbers next to each fail in the Read/Write IFC Tab.

[GoogleCodeExporter]

Feature Request: add STEP numbers next to each fail in the Read/Write IFC Tab.

[GoogleCodeExporter]

I would recommend to use a debugger. Then you can easily get the STEP id and 
other information about the concerning object.

Original comment by [email protected] on 5 Aug 2014 at 2:49

• Changed state: Invalid
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Having the STEP ids beside each error would help narrowing down what part of 
the IFC file is causing the issue. But no worries, I will add them myself to my 
local IFC++ codebase if it's a problem.

Original comment by [email protected] on 5 Aug 2014 at 3:36

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I agree that appending the entity id to the error messages makes sense. It is 
now added to the error message above and others in SolidModelConverter. If you 
find other error messages without entity id, please let me know.

Original comment by [email protected] on 6 Aug 2014 at 9:53

• Changed state: Started
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Sure, will do. Thank you kindly

Original comment by [email protected] on 6 Aug 2014 at 10:29

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

More on this enhancement request : please find the following commit 
https://github.com/VTREEM/IFCPlusPlus2/commit/2eefb0031a21e1f1d801ce2b787dc57966
12ce43 :
"Report CSG errors in the err stream even when no exception has been raised."

Original comment by [email protected] on 8 Sep 2014 at 4:40

• Added labels: ****
• Removed labels: ****