Hi @Turro75 !
Turro75 wrote: ↑Wed Oct 03, 2018 7:36 am
kbwbe wrote: ↑Tue Oct 02, 2018 1:28 pm
@Turro75,
please test whether it is working for you on windows or not...
Ok it is working on Win10,
I still get the error if the edited obj hasn't closed
Code: Select all
Running the Python command 'a2p_updateImportedParts' failed:
Traceback (most recent call last):
File "C:\Users\xxxx\AppData\Roaming\FreeCAD\Mod\A2plus\a2p_importpart.py", line 443, in Activated
updateImportedParts(doc)
File "C:\Users\xxxx\AppData\Roaming\FreeCAD\Mod\A2plus\a2p_importpart.py", line 413, in updateImportedParts
importPartFromFile(doc, absPath, importToCache=True) # the version is now in the cache
File "C:\Users\xxxx\AppData\Roaming\FreeCAD\Mod\A2plus\a2p_importpart.py", line 171, in importPartFromFile
importDoc = FreeCAD.openDocument(filename)
The project 'C:\Users\xxxxreplacement\cubo1.FCStd' is already open!
I still don't get this error on my system. Thanks to @Turro75's help I can now provide my versions, somehow openSUSE doesn't compile in the FC version number:
Code: Select all
OS: "openSUSE Tumbleweed"
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.Unknown
Build type: Release
Python version: 3.6.5
Qt version: 5.11.1
Coin version: 3.1.3
OCC version: 7.3.0
Locale: English/Denmark (en_DK)
Turro75 wrote: ↑Wed Oct 03, 2018 7:36 am
@Manuel
the importer is ignoring the color of the single face, it imports only the whole shape color. May be I miss something in the previous posts, it is an intended behavior?
cubo1 is fully green while cubo2 has a violet face over a green shape. both are imported as green only.
regarding the complete FC version output: menu help->about FreeCAD -> copy to clipboard
then paste in a text field.
Do you refer to current devel branch? If so, @kbwbe removed my color-import approach for the release in master & devel.
And even with my approach it wouldn't preserve single-face colors, I assume. My main goal was only to preserve imported part's color & transparency, set in the final shape of the part, and therefore, although processing each face, it would only recalculate faces' values from the whole shape color & transparency of the object into a usable diffuseColor for FC 017. (At least that's my understanding of what I coded.) The same result can be achieved with the simplified and faster code for the compound shape (although data volume remains the same and single-face colors aren't preserved, either).
https://github.com/kbwbe/A2plus/issues/96
I don't know, when we follow the toponaming idea to the end, if we'd be able to attach color & transparency to the corresponding faces.
And I also don't know if we want this? Guys, what's your opinion about it?
@wandererfan:
I'm not used to compound shapes. Would it be able to keep per face color & transparency info for the single faces - in combination with the proper toponaming relative info?