Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Petri

  1. GraphicConverter and/or CADintosh (both by Lemke Software http://www.lemkesoft.de/) might also work, if one is using a Mac. CADintosh should be able to convert HP-GL to DXF. However (AFAK), PLT does not necessarily mean a particular file type, ie. HP-GL.
  2. Seena, All VW-specific objects (walls, floors, roofs, parametric objects) will be converted to generic 3D objects. You can easily see what happens by exporting as DWG and importing back.
  3. Ceterum censeo, it is about time to make database reports editable - id est,to have a two-way link between any user-editable fields (data records and PIO input) and the listing in a report. I make do with named objects and scripted reports (a normal line for each entry) & returning data, but a normal user cannot be excpeted to do it this way (and I hate writing scripts for the purpose.) Surely, it can't be that difficult - GIS progams such as MapInfo have been able to do it for decades (called exempli gratia 'browse table.)' Right - there is no persistent internal object ID in VW? Well, introduce the concept. At least I surely could use this every so often in my scripts. Sat sapienti.
  4. quote: Originally posted by propstuff: Using classes to name colours sounds like way too much confusion to me. I'd like to amplify this by reminding that there are only 256 colours to work with and that importing a colour palette will inevitably & always throw the previously defined colour scheme out of whack by approximating the old colours to the new scheme. With all due respect, the approximations must be done with an improbability engine.
  5. We do, but it easily leads to otherwise illogical classification of objects and/or proliferation of classes to an unmanageable number; well, at least with our rather complex colour schemes it does. This would be avoided if gradients could be used in 3D. The user interface could be either incorporated in or based on textures. With VectorScript it is possible to define accurate gradients without gradation, ie. solid colours in 24-bit colour space.
  6. quote: Originally posted by propstuff:Oh, and I still want better colour management in VW. :-) It is an absolute shame that gradients can't be used in 3D. IMHO, named colours would be so much easier to use. [ 09-26-2004, 06:23 PM: Message edited by: Petri ]
  7. quote: Originally posted by propstuff: Manual was telling me fibs? He's from Barcelona, he knows noothin. VW 9 Manuel does (page 60) say "Click Import to use a color palette from another drawing or program." Fixed in VW 11 Manuel, it seems. Dunno about VW 10. [ 09-26-2004, 02:00 AM: Message edited by: Petri ]
  8. Well, Eric - now you are talking! We wanted croppable layer links, to be able to do a variety of things from drafting to presentation - but instead got viewports that are only good for printing. Very good, it seems, but they do nothing in terms of making the design process easier and more efficient. WE WAS ROBB'D!
  9. quote: Originally posted by Katie: You can open two different versions of VW at the same time - VW 10 and Viewer 11, but you cannot, without holding down the "m" key open VW 11 and viewer 11 at the same time. I have VW 11 and VW 11 Viewer open right now, without any key pressing. (Mac OS X)
  10. But, Jonathan - as a layer link it IS like a symbol... Since the current system works with a consistent user interface (ie. data behaves and is handled the same way regardless of its source, current work file or referenced file) and allows easy rotating, mirroring and moving, why would we need a new confusing paradigm?
  11. Petri

    Edit Save View

    Occasionally one may want to include a script to a view change, such as changing class attributes, layer scales or font sizes.
  12. Curious. I have on occasion done this with VW 9 on Mac OS. The same file cannot be printed with the Viewer and edited with VW at the same time, though.
  13. quote: Originally posted by John CPR: I have started to look at layer linking but it looks very convulted. I don't want to argue (and definitely don't want to be an apologist for NNA and VW!), but I can't really understand how layer linking would be convoluted - it is at most two menu commands (create LL, unlock.) After that one can eg. duplicate the link if need be. quote: Originally posted by eric.rktek But to name names, mving and positioning reference files is much easier to deal with in AutoCad and Microstation. Can't say that I would know how it works in these programs, but the underlying logic and purpose of VW's referencing is such that moving and positioning does not make sense. The reference is not a single object and the whole idea is that it is in the same coordinate system as the data in your current work file: this ensures data integrity.
  14. Processing and querying even medium-size databases, especially if one wants to update or populate a database using external data is painful, sometimes almost impossible. The option to index fields would make things a lot easier. At present, I use techniques such as FOREACHOBJECT and temporary names, but they are slow and the latter is even dangerous, not to mention the multiple steps required. Validation would not be a bad thing, either.
  15. I'm not even sure why one would like to move and rotate reference files, unless they are used as sort of symbols: say, a multi-unit residential development, with each type in a separate file, referenced to an overall plan.
  16. quote: Originally posted by jonas mac: Briefly , a fundamental in GDS is to use the intelligence of the programme by USING the object structure ,ie, before you draw lines you create an object giving it a name and a hook/insertion point so that when you click on any part of the drawing it tells you on the screen what object you have clicked on. I don't think it is possible to create such object structure in VW and get it translated via DWG/DXF, but who knows. Ask your friends how they tackle AutoCAD drawings; they might even give you a sample AutoCAD file to import into VW to see how it is configured.
  17. Use layer linking for the referenced data.
  18. quote: Originally posted by Kevin: My issue with the speed of VW is the speed of the OIP. Tabing through it is slow. Expanding the Door and Window OIP is slow as well. It has become a real annoyance. Yep - I should have included that, not to mention file dialogs. The current Finder (10.3.5) is still hopelessly slow and, compared with OS 9, lost some important features like remembering what file was opened last in a folder via Open dialog. Maybe one day we get our fast Macs back: I do whenever I use Classic...
  19. quote: Originally posted by david bertrand: I saw the review in MacWorld of VW 11. I emailed the magazine to ask about speed issues that I've read about on this forum. Most speed issues relate to seriously complex files: complex 3D models with NURBs etc, large terrain models (100K+ data points) or simply huge files; OS platform is also an issue and I don't use VW under Mac OS X if I believe I may need to say 'select all' to 40,000+ polylines with nearly a million vertices. (I am _not_ joking!)
  20. David, Please do not try to emulate AutoCAD with VectorWorks - while it might work, it is very inefficient. VW has features and functionality not found in AutoCAD and those are what really make the program so useful and productive. Eg. for building plans, use walls instead of lines & offsets.
  21. Well, Ziska - connecting 3D loci would do little good anyway: the resulting 3D polygon is not likely to be planar. Non-planar 3D polygons are not handled well in any CAD-program, so such surfaces are usually triangulated.
  22. Ben, You might just delete class '0' in each library file - then everything in that class will be reclassified as 'None'. There is little harm done if components of a symbol are in None class, unless you specifically want to control their visibility. [ 09-06-2004, 12:34 AM: Message edited by: Petri ]
  23. Ben, The groups are likely to be in class 'None' although their members are in some other class. If the 'parent' itself is not visible, the 'children' can't be either.
  24. quote: Originally posted by markoos: On another note, I may have a misunderstanding of how classes work, at least in conjunction with layers. I have only been using Vectorworks for a few weeks, and i am more akin to AutoCAD and Microstaion. As I understand it, "classes" in VW are synonomous with "layers" in AC. Think layers as different drawings - either spatially or thematically separated. Technically each layer is a list of objects (meaning among other things that if you delete a layer, everything on it will be deleted.) Classes on the other hand are properties of objects. Using them both in a considered manner clarifies the design process. Layers can certainly be used for 2D drafting. You might have each floor as a separate layer and also each discipline for each floor. (In a large project you would have each floor as a separate file.) Disciplines could also reside in separate files and be brought in for referencing purposes via Workgroup References. This allows several people to work on the same job and makes it easy to update consultants' input. Anyway, you may be in a position to help the office to make a quantum leap in productivity. Your experience with AutoCAD and MicroStation could be put to good use, if you avoid pure imitation of the processes of those programs and instead introduce good working habits based on the capabilities of VW.
  • Create New...