DWG图纸组合在AutoDesk Forge上失败 [英] DWG Sheet Combination failing on AutoDesk Forge
问题描述
我们正在使用Forge将STEP文件导入到output.DWG的模型空间中.然后，DLL将多个DWG文件的模型空间几何形状合并为单个DWG的多个布局/图纸空间.直到最近，当合并过程完全停止发生时，此工作表组合才能正常工作.
We are using Forge to import a STEP file into the modelspace of an output.DWG. Then a DLL combines modelspace geometry of several DWG files into several layout/paperspace of a single DWG. This sheet combination was working perfectly until just recently, when the combination process completely stopped happening.
最近Forge中有一些我们不知道的变化吗?更新/补丁，或可能导致此问题的类似内容?
Has something in Forge changed recently that we're not aware of? Updates/patches, or something like that which could have caused this issue?
这是生产应用程序的一个问题，目前被视为中断，并且非常敏感.
This is an issue for a production application and is considered an outage at this point, and is very time-sensitive.
编辑:以下是我们注意到此过程生成的日志文件之间的一些差异.在第一部分中，在提取过程中，AutoCAD编写的字词略有变化:
Here are some differences we noticed between the log files generated by this process. In this first section, the verbiage being written by AutoCAD has changed slightly during an extraction process:
[08/01/2019 17:15:35]结束下载https://.... 1556909字节已解压缩到文件夹中T:\ Aces \ Jobs \ a43e5ca7faaa4db8b5b5374aaef71b36d3 \ cadlayouts.
[08/01/2019 17:15:35] End downloading https://.... 1556909 bytes have been unpacked to folder T:\Aces\Jobs\a43e5ca7faaa4db8b5374aaef71b36d3\cadlayouts.
[08/19/2019 17:25:53]结束下载文件https://....1771363字节已写入:T:\ Aces \ Jobs \ d12f3bed13b84d29b31226222e3cf3c9 \ cadlayouts.
[08/19/2019 17:25:53] End downloading file https://.... 1771363 bytes have been written to T:\Aces\Jobs\d12f3bed13b84d29b31226222e3cf3c9\cadlayouts.
在8/19的日志中，所有行之间的登录时间:
In the log from 8/19, all lines logged in between:
启动AutoCAD Core Engine标准输出转储.
Start AutoCAD Core Engine standard output dump.
并且:
结束AutoCAD Core Engine标准输出转储.
End AutoCAD Core Engine standard output dump.
被写入两次，但是从8月1日开始的日志文件或该日期之前的任何日志中都没有发生这种情况.
Are being written twice, but this did not happen in the log file from August 1st or any of the logs before that date.
修改2:昨天，我们使用了.NET DirectoryInfo 类将所有目录拉入一个列表，将所有文件拉入另一个列表，并将它们全部写入日志.相反，应被识别为目录的cadlayouts实体(因为它是Forge提取的zip)，而是被列为文件.在工作项将DWG合并到输出中之前，我们的流程运行 Directory.Exists()检查，并且此调用绕过我们的组合逻辑，为cadlayouts文件夹返回 false .如果文件系统上生成的实体不被视为目录，那么Forge zip提取过程如何正常工作?
Edit 2:
Yesterday we used the .NET DirectoryInfo class to pull all directories into one list and all files into another and write them all to the log. The cadlayouts entity that should be recognized as a directory (because it's a zip that is extracted by Forge) is instead listed as a file. Our process runs a Directory.Exists() check before the work item merges the DWGs into the output, and this call returns false for the cadlayouts folder, bypassing our combination logic. How can the Forge zip extraction process be working correctly if the resulting entity on the file system is not considered a directory?
推荐答案
听起来您的输入参数是zip，并且您希望将其解压缩到文件夹中.请查看下表中的第4行.我怀疑这就是您所遇到的. WAS 此处是最近的更改:我们曾经查看下载的位，如果找到了zip标头，则无条件地将其解压缩.(即我们在第3行和第4行的行为相同).现在，只有在您要求我们这样做时，我们才这样做.
It sounds like you have an input argument that is a zip and you expect it to be unzipped into a folder. Please look row 4 in the table below. I suspect that this is what you are experiencing. There WAS a recent change here: we used to look at downloaded bits and unconditionally uncompressed if we found a zip header. (i.e. we acted identically for row 3 and row 4). We now only do this if you ask us to do it.
The first column in the table is the value of the zip attribute of Activity's parameters while the second column is the pathInzip attribute of Workitem's arguments.
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| # | Activity | Workitem | Arg direction | Comments |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 1 | zip==true | pathInZip!=null | input | Zip is uncompressed to the folder specified in localname. Any path reference to this argument will expand to full path of pathInZip. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2 | zip==false | pathInZip!=null | input | Zip is uncompressed to the folder specified in localname. Any path reference to this argument will expand to full path of pathInZip. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 3 | zip==true | pathInZip==null | input | If zip is provided then it is uncompressed to the folder specified in localname. Any path reference to this argument will expand to full path of localName. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 4 | zip==false | pathInZip==null | input | If zip is provided then it is left compressed. Any variable referencing this argument will expand to full path of localName. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 5 | zip==true | pathInZip!=null | output | Workitem will be rejected. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 6 | zip==false | pathInZip!=null | output | Workitem will be rejected. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 7 | zip==true | pathInZip==null | output | Output(s) at localName will be zipped if localName is a folder. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 8 | zip==false | pathInZip==null | output | Output at localName will not be zipped. |
+---+------------+-----------------+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
这篇关于DWG图纸组合在AutoDesk Forge上失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
