Jump to content

Mark Farnan

Vectorworks, Inc Employee
  • Posts

    96
  • Joined

  • Last visited

Everything posted by Mark Farnan

  1. Have you tried the Align/Distribute context menu command when two or more objects are selected?
  2. > To be able to import multiple images at once Can't you do that with drag and drop?
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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?
  8. Hi Christiaan, I see that also. Consider this issue reported. Please let me know if you see anything else. Thanks, Mark
  9. 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
  10. 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
  11. Sorry everyone. Let me check what's going on here. I'll get back to you when I find out. Mark
  12. 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
  13. 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
  14. Hi everyone, 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/VW69097.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
  15. Junker, A fix is in the works but we still have more work to do on it. I'm sorry I can't give you timeframe at this point. But with some care on your end this problem should not still be "haunting" you. Are you using Expose a lot? If so that might be what's going on. If not and if you're following the recommendations I listed above and you're STILL having problems, please let me know. Thanks, Mark
  16. dr paaj, If the corrupt files are zero K then it certainly sounds like you are experiencing the file corruption problem that has been identified in this thread. I'll post our recommendations again because they've changed slightly as we've learned more: Our investigation so far has shown that the problem happens when you minimize a VectorWorks document or use Expos? to activate a document, then immediately save. If you minimize a VectorWorks document or use Expos? you may notice that the data bar and mode bar of the newly activated document are not displayed. THIS is when the problem happens. If you don't click on that document to fully activate it, any save you do can or will cause the partially activated document to become zero K on disk. Another point to note: when you get the "An error occurred while saving this file. This file is now corrupt on disk. Try saving to a different location..." message, you may find that you are unable to save to a different location (the error dialog will just keep coming up). In this case, try clicking in the document that you are trying to save, and then save to a different location. At this point we would advise Mac users to make sure their Autosave is saving to a backup folder and to not minimize VectorWorks documents or use Expos? to activate documents. We are testing a possible solution to this problem and hope to get the fix in the hands of our users as soon as we can. Mark
  17. Hi Matt, I don't have anything on this one. Are your corrupt files zero K? Mark
  18. Hi Donald, I don't doubt that there are more anomolies when you put documents in the dock. We've made good progress on our investigation and have found that we are not always fully activating the document that should be activated. I wouldn't be surprised if apple-tilde and maybe other actions that activate documents might cause similar problems. Thanks for all of the clues. Mark
  19. Hi everyone, Here?s more information on the zero K file corruption problem: Contrary to our initial suspicions, it now looks like "open files that are not yet saved to disk" don?t have anything to do with the corruption. The problem appears to happen when you minimize a VectorWorks document and then immediately save. In VectorWorks 12 on the Mac when you have more than one VectorWorks documents open and you minimize one of them you'll notice that the data bar and mode bar of the newly activated document are not displayed. THIS is when the problem happens. If you don't click on that document to fully activate it, any save you do that doesn't involve clicking on that document (like through Autosave or if you use cmd-s) can or will cause the partially activated document to become zero K on disk. It is still true that if you get the "An error occurred while saving this file. This file is now corrupt on disk. Try saving to a different location..." message, you may find that you are unable to save to a different location (the error dialog will just keep coming up). In this case, try clicking in the document that you are trying to save, and then save to a different location. At this point we would advise Mac users to make sure their Autosave is saving to a backup folder and to not minimize VectorWorks documents. We are continuing to investigate how to best fix this problem and get it in the hands of our users. Thanks to everyone for helping us reproduce this problem. Mark
  20. Hi Fran?ois, Are you using the "save to backup folder" feature of autosave? Mark
  21. Hi Tom, You might try posting this as a new thread under General Discussion (maybe "Disappearing VectorWorks Files on Windows"). We'll try to get it to happen here, and I'll keep an eye on the new thread to see if anyone else is having the problem or has any ideas. Best regards, Mark
  22. Hi Tom, This is more of a missing file problem than a file corruption problem. To my knowledge we have no other users reporting this behavior. We'll do some testing here - please let me know if you get more clues. You may want to move at least a couple of your machines back to the previous version of Explorer to see if that helps. Mark
  23. Graham, I'm not seeing this on my G5 running MacOS 10.4.8. Are you running 10.3.9 like Donald is?
  24. Hi everyone, Just yesterday afternoon we were finally able to reproduce this problem. While our reproducible case is probably not related to every problem mentioned in this thread (especially not Tom's recently posted disappearing files on Windows problem), I think we have our claws on the root cause of many of the issues described here. While we continue our investigation, here are some recommendations based on what we know so far: - If you're on a Mac and you're using Autosave, we recommend using the "save to backup folder" option so you minimize your chances of losing your original file. - If you get the "An error occurred while saving this file. This file is now corrupt on disk. Try saving to a different location..." message, you may find that you are unable to save to a different location (the error dialog will just keep coming up). In this case, try clicking in the document that you are trying to save, and then save to a different location. - This problem may be related to having files open that are not yet saved to disk. This would include newly created files, as well as files converted from a previous version that have not yet been saved to disk. Try saving these files to disk before proceeding to work on them or any other files that you might have open. Hopefully following these guidelines will reduce or eliminate some of the problems you're having. We'll let you know more as we learn more. Thanks for all of the clues that you've provided in this thread. Mark
×
×
  • Create New...