Jump to content

Tolu

Vectorworks, Inc Employee
  • Posts

    531
  • Joined

  • Last visited

Everything posted by Tolu

  1. Hi Richard, There are two ways to accomplish what you are trying to do. However, how you want your DLVP to react will determine which method you use. You should be aware of the following two fundamental things: - SLVP can only control local classes/layers (i.e. classes/layers that exist in your drawing or classes/layers you see on the Navigation Palette or Organization dialog). - Similarly, RDLVP (referenced DLVP) can only control referenced classes/layers (i.e. classes/layers that exist in your referenced drawing). Method 1: There is a checkbox control, ?Use current document?s class visibilities?, on the Viewport class properties dialog for RDLVPs. This allows a RDLVP to respond to changes in the visibilities of local classes in the drawing that are also available in the RDLVP (changes made via Nav. Palette or Org. dialog). This setting is per RDVLP. With this checkbox turned on for RDLVPs that are embedded in a SLVP, the class visibilities that you specify in the SLVP will affect embedded RDLVP. Note that with this method, whenever you change the current document class visibilities, your RDLVPs will also change, but they will always look the same when shown embedded in a SLVP. Method 2: You can duplicate your RDLVPs, put each RDLVP on different layers (or assign then to different classes, your choice), and make each RDLVP show/hide the necessary classes. Then on the SLVP side, make each SLVP show/hide the RDLVP based on the layer (or class) that your put them on. Hope that helps. Regards, Tolu NNA
  2. In regards to the huge file size, there is an option not to save reference cache to disk. This will reduce your file size, however, you will be required to update the reference when you open the file. For the slow down, here are a few questions: 1. What version of VW are you running? A detailed signature will be helpful here. 2. What exactly is slow? Reference update speed, DLVP draw speed? Could you please provide details? 3. Does the slow down happen always, frequently, or sometimes? Best Regards, Tolu
  3. I am glad that helped. The "small mountain" means use viewport specific class definition (i.e. the viewport determines the definition of that particular class). The toggled state which gives you the "VW file" icon means use current document's class definition (i.e. the current document determines the definition of that particular class in the Viewport). The "arrow" indicates whether or not to update the class definition (as defined by column 4). All these settings work hand-in-hand. For example, when the "small mountain" is on and the "arrow" is on, this means the class definition is as defined in the viewport's source. I hope that helps. BTW, the help does a better job explaining. Regards, Tolu
  4. Hi David, Thank you very much for the sample files. >Thank you for confirming our suspicion that there is no way to >prevent VW from wasting time trying to find information from >remote files that is turned off in the DLVP. As I stated in my previous post, because layers from file 1 made it into file 3 does not mean that VW is reading them from file 1. VW will read and use the layers of file 1 that are present in file 2 if it finds that those layers are up to date. Specifically, when you update the reference in ?Untitled 3.vwx?, NNA#1#1_Design Layer-1 is read from ?Untitled 2.vwx?, NOT ?Untitled 1.vwx?. Furthermore, NNA#1#1_Design Layer-1 is an empty in ?Untitled 3.vwx?; therefore it is not a contributing factor to your slow down. As such, if you purge "unused layers" and run the script, you will not see NNA#1#1_Design Layer-1 listed because it would have been deleted because it is empty. I currently unable to determine what is causing your slow downs. If you are still seeing slow downs, I had be glad to take a look at your files and your server configurations. You can also contact tech support. Best Regards, Tolu
  5. Hi David, Please submit a bug report: http://www.nemetschek.net/support/bugsubmit.php You can send the files to: bugsubmit@nemetschek.net Thanks Tolu
  6. What you need to do is make the referenced Design Layer Viewport (DLVP) use the current document's class definition and visibilities. To do this: 1. Select the referenced DLVP 2. Click the "Classes..." button on the OIP to display the "Viewport Class Properties" dialog 3. Select all the classes and toggle on the column after the visibilities. This makes the DLVP use the current document's class definition. You will get a message effectively asking if you want to update the class in the current document to have the same definition as the source document. Click "Yes" to continue. 4. With all the classes still selected, toggle the column before the class names such that the classes are not updated whenever references are updated. 5. Finally, turn on the "Use current document's class visibilities" checkbox to make the DLVP use the current document's class visibilities. Please let me know if that helps. Regards, Tolu
  7. You are referring to the "Use current document's class visibilities" setting for the DLVP. When this is checked, it causes the DLVP to ignore its visibilities and uses the active document's class visibilities which is exactly what you described above. However, Pat is referring to the "Retain Design Layer Viewport class override" checkbox control that is available on the "VP Class Properties" dialog for SLVPs.
  8. Hi David, Besides the suggestion about saving cache, there isn't a setting available that will prevent file 3 from accessing the information from file 1. If you do not want file 3 to access file 1, then make sure that the Design Layer Viewport (DLVP) in file 2 of file 1 is placed on its own layer and that that layer is NOT visible in any DLVP that you create in file 3. >The file 1 information is turned off in the viewport in file 3 How are you accomplishing this? The DLVP in file 3 has no direct access to the information in file 1. >but Vectorworks wastes time and network resources reading it anyway. Again, I am not sure exactly how your files are setup, but because layers from file 1 exists in file 3 does not mean that VW is reading them from file 1. VW will read and use the layers from file 1 that are present in file 2 if it finds that those layers are up to date. In order to correctly determine the slowdown you are seeing, we'll need your files and your server configurations. Thanks, Tolu
  9. Hi David, Could you send me your files or sample files (tfapohunda at vectorworks.net)? Vectorworks should only follow the reference links as I described above.
  10. Hi David, Vectorworks will follow the reference links from file 2 back to file 1 only if the needed information from file 1 is not already present in file 2. If you do not want this, you will have to edit the reference in file 2 and select "Save Reference Cache". This will guarantee that the reference data from file 1 is always saved with file 2. As such, when file 3 attempts to update its reference from file 2, all the needed data from file 1 will always be present in file 2. Let me know if that helps. BTW, what version of Vectorworks are you using? Regards, Tolu
  11. Hi Grant, Please submit a bug report: http://www.nemetschek.net/support/bugsubmit.php You can send the files to: bugsubmit at nemetschek.net Thanks Tolu
  12. Hi, If your references are using "Absolute path" and you change the name of a top level folder, the references will be broken. Is that what you mean by "lost"? However, when you open the file, you should be informed about broken references. My advice is to always use relative path, so you copy/move the top level folder to another computer and your references will still be intact. You can get to this from the Organization dialog -> references tab, select all references, and click "Edit...", and select the "Relative Path" radio button. In regards to viewport settings being lost. Viewport settings are not path based and those reside with each file. So changing the top level folder should not affect/discard any viewport setting. I will be glad to take a look at the files. You can send them to tfapohunda at vectorworks.net Best Regards, Tolu
  13. Hi Steve, Please submit a bug report: http://www.nemetschek.net/support/bugsubmit.php You should also send the files with which you are having problems to: bugsubmit@nemetschek.net Thanks, Tolu Fapohunda NNA Engineer
  14. I am unable to reproduce this. Can you please submit a bug report with the file attached. http://www.nemetschek.net/support/bugsubmit.php You can send the files to: bugsubmit@nemetschek.net
  15. Pete, please submit a bug report with the file(s) included. Submit a bug report: http://www.nemetschek.net/support/bugsubmit.php You can send the files to: bugsubmit@nemetschek.net Tim, if you are using SP3 and you are seeing 'NNA#_' worksheets, please submit a bug report as well.
  16. You are getting that dialog because the active file is set to use DLVP as the referencing system and you are trying to create a reference via the references tab. If you want to use DLVPs as the referencing system, you should create a viewport, otherwise, on the references tab of the organization dialog, click the Settings... button to switch to Layer Import (AKA old style referencing) system. > Why won't it remember that I changed my "settings"? Because the setting is file based. If you want it off in all your new files, you should create a template file.
  17. Hi Markus, Could you please send the files exhibiting this behavior to me at (tfapohunda@nemetschek.net)? Thanks, Tolu
  18. bclydeb, Make sure you are using the latest service pack, SP3(88670).
  19. Bob-H, What do you mean the Annotation layer? You cannot annotate design layer viewports like you can sheet layer viewports. Furthermore, if you are using design layer viewports as your referencing system, you cannot directly move objects. Please can you clarify the problem you are seeing and the method of referencing you are using so i can try to reproduce the problem? Thanks, Tolu
  20. IanH, Are you saying you also experiencing random shifts using SP3? Please, submit a bug if you are running SP3 and you are still experiencing random shift in origin or in viewport locations.
  21. Hi Martin, Could you please repost the crash log as a text file? Using PDF totally messes up the format and renders it unusable. Perhaps, you can send it to me directly at TFapohunda@NEMETSCHEK.NET Thanks, Tolu
  22. Please could you submit a bug report with your crash logs attached? Thanks
  23. Paul, did you attach the crash log to the bug report you submitted? If not please, send it to me (tfapohunda@gmail.com). Also, What version of VW are you using? >I don't really want to have to delete the viewports in the layers as i still need them. You must be using the old style. If you need the Viewports, you will have to use DLVPs as your referencing system. Open the Organization dialog Switch to the Reference Tab Click 'Settings...' Under 'Use this method to reference VW files', choose 'Design Layer Viewports'
  24. I have submitted a bug (bug# B065675 for your reference). The problem is currently being investigated. FWIW, I will updated the bug report stating that "you experienced at least 3 more crashes today". Tolu
  25. To JHEarcht Yes it is a Mac thing Leonard, thanks I got the files. I am looking at them now.
×
×
  • Create New...