Jump to content


Vectorworks, Inc Employee
  • Posts

  • Joined

  • Last visited

Posts posted by Hugues

  1. Pete, saving a file mostly only involves writing data to disk. The size of the file to be written, the hard drive speed and the network speed (if saving on a network volume) will determine the speed of the operation. Incremental saving is a solution that could definitely improve saving as the amount of data to be written to disk could be significantly reduced. However, the Vectorworks file format doesn't support it yet.

    Updating source (referenced) files is a completely different process. It does not involve writing the file to disk at all. When updating a source file, data in the target file that references data from the source file must be updated. Updating these data can be fast or slow depending on the changes made in the source file. For example, if a Wall Style was modified in the source file, all walls in the target file that use this style have to be updated. The number walls and their complexity will determine the speed of the updating process.

    Just moving the data from the source to the target file is fast. It is reconciling that data within the target file and regenerating objects that is the expensive step.

    If you are experiencing unexpected slowdowns when updating references, please send us a copy of the files and we will be happy to take a look at it (Tech@vectorworks.net). Your files could help us detect a particular configuration or interaction that is not well enough optimized.

  2. A Default Story Level is a preset configuration that can be used to quickly set up and create levels when creating stories.

    A default story level is like a definition of a level and it must have a level type. You cannot create a default story level with no level type ( level).

    What would be the purpose of creating Default Story Levels with no level types ?

  3. The .lck file isn't there to prevent other users from opening the file. Its main purpose is to provide the file lock information (user, computer and time of lock). This enables VW to tell you who currently has the file open, where and since when.

    It is never used to determine whether another user can open the file. This determination is made by the File System based on the permissions set when the file is opened. The first user to open the file gets READ and WRITE access with READ-ONLY access for other subsequent opens. This is all handled by the File System.

    As for DropBox, it uses a push mechanism to keep your local file in synch with the file in the dropbox server.

    This means that everyone works on local files in their own local dropbox folders independently from each other.

    You are opening your own local file with full permission.

    Also note that this issue with dropbox and multiple user environments is common to other applications. This is the nature of the system.

    DropBox actually has a a mechanism in place that detects and handles potential conflicts during file synchronization when multiple users had the file opened at the same time.

  4. Thanks Matthew, I'll investigate that.

    EDIT: this doesn't quite get me there. I guess you can't get there from here.

    Click on the New button in the "Edit Marker List" dialog to create a new marker.

    You should be able to create any number of new markers of your own based on different root types.

    Is there any particular marker geometry that you haven't been able to create ?



  5. "Please submit a bug report and attach the file(s) so we can investigate."

    How do I pass along a file of 92 MB The file works acceptably in VW2012.

    If the file is too large, compress it and feel free to use dropbox or www.yousendit.com




  6. Jim,

    Looking at your worksheet, I see there are many floating cells (cells with text floating into adjacent cells). These types of cells have caused performance issues on the Mac. These issues were fixed in VW2010.

    Try to reduce the number of floating cells to a minimum.



  7. Hi Pat,

    Thank you for investigating this.

    There is definitely a problem with the LOC criteria when used on objects inside symbols.

    Symbols have their own space and the coordinates and boundaries of objects in it are defined relative to that space.

    What's happening here is that the poly in symbol returns its location relative to the symbol and this is checked against the location of loc1603 that is in a different space.

    Currenly, the only way you would get accurate results with LOC and objects in symbols is by having your reference location in the same symbol.

    Could you please submit a bug? We'll address it in the next release.



  8. Hi Ozzie,

    Is 'Loc1603' a symbol ?

    If yes , then this is the problem.

    The LOC criteria is used to find objects that are located within the bounds of a named object. We have just found that it isn't working if that named object is a symbol. Looks like a bug.

    If your polygon is within the bounds of another object in your symbol you can try with that one.

    And also, use CRITERIAAREA instead of AREA to get the area in area units, so you can get rid of the divide by 1000000*0.08



  9. CS1,

    This is strange.

    Try again and double-check to make sure that the worksheet lists only objects that meet the layer criteria.

    To check that, add a column in the worksheet and enter =L to return the object's layers.

    Also, are you comparing the results from the Custom Selection command and those from the worksheet database ? You may see differences in the number of objects that meet the criteria. The reason is that because DLVPs objects are not selectable, no search is performed in DLVPs when running Custom Selection.




  10. Hi team,

    Custom Selection selects the objects but doesn't change the active layer to make them visible.

    If you want to do a cross document selection using Custom Selection, you'll get the best feedback if all layers are visible and the options Show/Snap/Modify Others is set.

    Objects in symbols will also be selected but you'll have to enter the symbol to edit it.



  11. Hi Sam,

    I am sorry but there is nothing you can do except what you are already doing that is increase the height of the database header row.

    The reason for this problem is that rows in the same database are not allowed to have different heights in Vw08. What you see in the editor is actually misleading at the end the database row will always pick the height or the database header row.

    AutoFit row height only works well with wrap text in spreadsheet cells.

    We have resolved this issue in Vw09.


  12. As Ariel mentioned, you can place a SUM icon on the column where you don't want the numbers to add up. But you can only use a maximun of 3 SUMs in a database.

    If you run out of SUMs, the workaround is to add a quantity column at the end of your worksheet, enter the formula =COUNT. Now you can use a reference to this column to divide the columns where you want to eliminate the summation.

    With H being the quantity column, the formula in your windows width column could then look like this: =(Window.OverallWidth)/H4

  • Create New...