Nicolas Goutte

If you mean just the door, without cabinet, just disable the parts in the corpus, the back and whatever might be generated. Be careful of your measures in that case.

As far as I know, macOS deletes only files in the standard temporary folder on reboot, which according to the screenshot above is not the case. Yes, sure if they are kept, it is that something is wrong. Something is refrain the files to be deleted. On Windows, it might be an antivirus, permission (You can set delete permission separately on NTFS) and a few others. Curios that this happens on macOS, however, and not even on a folder on a server.

I think I have written it somewhere in this forum already (but I have not time to find it) VW saves first a drawing to a temporary file, delete the destination file and then moves the temporary file to the destination file. In case something goes wrong in this process, files may stay behind.

I do not think that it is possible. One way is perhaps use notifications to be notified what is happening currently in VW, but I am not sure if you could achieve what you want through the notification mechanism. (I know too few of it to know its full potential.)

As far as I know, the license is per computer. Therefore you might need to register the data for the new user, but the activation should work fine. (Anyway you cannot deactivate by yourself, VW support would have to do such a thing... if/when needed)

It mainly depends on the third party libraries VW uses, starting with Parasolid.

Translating Intel machine code into ARM machine code will always be costly, whatever the technology used for it. (I do not think it is worth to try to do any optimization on the Intel version of VW, if in the long-run VW will be compiled for ARM directly.)

Have you check the classic stuff for VW? That the right GPU is really used and that its driver is up-to-date.

The second question is with a high probability: yes. Apple has done full transitions already two times: Motorola 68000 to PowerPC, PowerPC to Intel. So the first question is probably yes too, in the long term (certainly not VW 2021, as macOS 11 is not officially released yet, but VW 2021 is already finished).

Sorry, the code we use is shared between many classes (especially to be testable). And I was not the one who has written it, so I cannot make a small example out of it.

Yes, we use both. However we do not take care of the return value of TrackHotSpot but use the CParametricHotSpot that is passed as parameter reference.

Or use ulimit -s directly. (from https://stackoverflow.com/questions/10214363/increase-stack-size-in-os-x-lion)

For the bug itself, I have just two further ideas: - does it crash too if you give an invalid, but non-empty string? - Is your string in the form "" or is it an empty TXString? Does it make a difference? As for stack size, may be you can change it on system level. sysctl(8) seems ti have two values concerning stacks: kern.stack_size: 16384 kern.stack_depth_max: 10096

It seem consistent with https://stackoverflow.com/questions/18909395/how-do-i-increase-the-stack-size-when-compiling-with-clang-on-os-x However, you are not controlling the main program (VW), so I do not know if it makes any sense to try it for a plug-in. Also exceeding the stack should be uncommon. Are you sure you have not an endless recursion somewhere? Or may be the crash is really in VW, because of what the plug-in has done just before.

I have taken the time to check that Default-Tool-Project. (Sorry I had no time to spare before.) This one has still a real Debug target; something that does not work since a few VW major versions ago. See the previous discussion:

Also the problem of releasing a Release target is that the compiler is allow to change the code. So it could happen that the line where you set the breakpoint is not in the generated plug-ins anymore, so that the debugger does not stop.

You are sure to have the Release plug-ins seen by VW. And only that one, not both.

Mostly it happens when you are not debugging what you think you are debugging. (The exakt version of what you start differs from what is in your IDE (Xcode or Visual Studio)

Even in C++-Code, it can happen that you do not see the text if VW has no time to draw it.

Yes you can use the Fake-Debug trick. As long as the C++ code is not optimized, the breakpoints should work correctly and be at the right place.

https://developer.vectorworks.net/index.php/SDK:Parametric_Extended_Properties

Most are text files, so you could compare.between your two machines, what they have for settings.

See the "Setting" folder in your VW user folder. There are all settings.

On Windows, you cannot use the Debug mode, as on Windows the C(++) runtime for Debug and Release differ, but VW is available for us (third party developers) only as Release mode. See what I had written months ago:

Double check that the "'pip list' " you have written as a parameter to subprocess.Popen has no special character.