Mark Farnan

Hi @shertzarch There's an outside chance this was caused by a system hiccup we had late last week. Can you check if the problem as described is still happening for you?

Have you tried the Align/Distribute context menu command when two or more objects are selected?

> To be able to import multiple images at once Can't you do that with drag and drop?

[entry deleted]

Hi Gavin, I can reproduce this on monitor 2 (only) if I am using two monitors and monitor 2 is positioned to the left of monitor 1. Do you have your monitors set up like this? Unfortunately I don't see any nudge problems in any case. Mark

Hi Chris, For your update problem, the first 2 things that come to mind are: 1. Did you save the source file before you updated? (Does the Nav Palette show it as out of date?) 2. Maybe there's a refresh bug? If you move the symbol that didn't appear to update, does it then suddenly update? Regarding your four items: 1. You're so right. We'll look to do that. 2. That's a trickier one. Do we do that for all referenced resources? Does that run the risk of complicating the drawing for users who don't really care? Maybe just doing #1 above would be enough? 3. I agree that we can do better than a "Selection is Locked" message there. 4. We don't have that because there's currently no way to just update that symbol definition without updating everything else in the file. So the command would actually be "Update the reference to the file that contains this symbol definition." But your point is well taken - we'll think about how we might be able to address that. Thanks for your thoughts here and in the Wish List Items area. Mark Farnan Core Technologies Manager Nemetschek NA

Hi everyone, We thought that we had successfully addressed all of the zero K file corruptions issues in 12.5.2, but we have found another variation. We think this variation is much less common because the set of users who we were working with last spring who were experiencing these types of problems in 12.5.1 have not reported recurrences using their regular workflows in 12.5.2. Regardless, our current reproducible case is: if you have multiple VectorWorks files open and you activate a VectorWorks file from the dock, do anything or nothing with that file, then send that file back to the dock, then save what appears to be the new active file without clicking on it (using manual save or Autosave), the corruption will occur. If you work in such a way that you think you might encounter the problem described above, we recommend that: a. If you save a file immediately after sending a different file to the dock, click on the file you want to save first. b. If you use Autosave, and sending files to the dock is part of your workflow, consider changing your Autosave settings to: - Autosave to a backup file. - Autosave by number of operations rather than by number of minutes. Rest assured that in the next release, this problem will be fixed and there will be new safeguards in place to prevent the overwriting of existing files with zero K or otherwise corrupt files. Sincerely, Mark Farnan Core Technologies Manager Nemetschek NA

This is the thread: http://techboard.nemetschek.net/ubbthrea...age=1#Post74794 You might want to skip to the bottom and work your way up to the download link. Mark

This fix is just for Macs. I do not have a reproducible case for the Windows problem you're describing. Have you sent this through Tech Support so our Testing team can take a crack at reproducing it?

Hi Christiaan, I see that also. Consider this issue reported. Please let me know if you see anything else. Thanks, Mark

Hi Christiaan, There should be no differences in this build and the shipping 12.5.1, other than that the zero K file corruption should be fixed. Are you seeing a bug in this build that did not exist in 12.5.1? If so what is it? Thanks, Mark

Hi everyone, I think the problem is that everyone who has tried to use this download so far is using a dongled version. I have posted a new application that works with dongled versions here: http://download2.nemetschek.net/seed/VW69163b.zip So, the new instructions are: -------------------------------------------------- For those of you who need immediate relief from the zero K file corruption problem, you can download a beta version of the VectorWorks application that fixes the problem. The use this new application, please follow these steps: 1. Rename the VectorWorks application that is currently in your 12.5.1 VectorWorks folder from ?VectorWorks? to ?VectorWorks ? orig? 2a. If you are using a non-dongled version of VectorWorks, download the following file: http://download2.nemetschek.net/seed/VW69163.zip (Use this file if you don't know what a dongle is.) 2b. If you are using a dongled version of VectorWorks, download the following file: http://download2.nemetschek.net/seed/VW69163b.zip 3. Unzip the file to get the new VectorWorks application. 4. Drop the new VectorWorks application into your 12.5.1 VectorWorks folder. Please let us know if you see any evidence that this new application does not completely fix the zero K file corruption problem. -------------------------------------------------- Maybe someone with a fast internet connection could download this dongled version and confirm that it runs ok, then post to this thread with a confirmation. Thanks, Mark

Sorry everyone. Let me check what's going on here. I'll get back to you when I find out. Mark

Hi everyone, Let's try this again. For those of you who need immediate relief from the zero K file corruption problem, you can download a beta version of the VectorWorks application that fixes the problem. The use this new application, please follow these steps: 1. Rename the VectorWorks application that is currently in your 12.5.1 VectorWorks folder from ?VectorWorks? to ?VectorWorks ? orig? 2. Download the following file: http://download2.nemetschek.net/seed/VW69163.zip 3. Unzip the file to get the new VectorWorks application. 4. Drop the new VectorWorks application into your 12.5.1 VectorWorks folder. Please let us know if you see any evidence that this new application does not completely fix the zero K file corruption problem. Thanks, Mark

This change is just for the Mac. **AND** we discovered a small problem with this build so it has been pulled back. Please look for a new message on Monday pointing to a build where the problem is fixed properly. Mark