Jump to content

Petri

Member
  • Posts

    2,011
  • Joined

  • Last visited

Everything posted by Petri

  1. Polygons & polylines: Perimeter = length. Line thickness has no effect. Walls: Length = length. These can be calculated into a worksheet.
  2. Right. Well, I won't offer more advice to Mr/Ms COMJAX as I don't want to have anything to do with gun-crazy people.
  3. I don't think this can be done. Besides, as one can have several attached records, the results could be rather unpredictable.
  4. One does not want the individually edited & entered data to disappear when one changes the default values, so let's be grateful that records are not updated!
  5. Where is Linux growing? Among hobbyists and very specialised industries. I have not heard of successful, commercial software on Linux. I would imagine that porting is quite a large task - well, at least the Windows-port was, as I understand. As I already said, to make money NNA would need to sell tens of thousands of licences to new users. (The current user base is, according to NNA, around 400,000.) In addition to porting itself, the Linux-version would need technical support - also by all distributors around the world. I gather that even Windows generates more tech support requests per user than the Mac platform. If a CAD-user is tired of Windows, he or she can switch to Mac. I don't see any benefits from a switch to Linux and can hardly imagine an architect or designer switching from Mac to Linux. Why would one do that?
  6. To quote Basil Fawlty: "What's the point? I mean, what's the bloody point?" I simply can't understand why there should be a Linux-version of VectorWorks. Are there tens of thousands of architects and other design professionals committed to the Linux-platform, refusing to use either Windows or MacOS?
  7. Petri

    HP 110nr

    Someone, a couple of years ago, posted a Terminal command that changed the pens of MacOS to round ones. Unfortunately, I can't find it!
  8. You should perhaps consider a separate database system, eg. FileMaker Pro, to hold all the relevant data, including pictures. You get excellent, practically desktop-publishing quality, data sheets. The worksheet data can, with copy and paste, used to select the records in the 'master file'. (Applies to FMP, don't know about others.) The approach also helps in maintaining costing data (not to mention other data.)
  9. I'd guess that if you import DWG into a document with classes that have attributes set to correspond with AutoCAD settings, you need no VectorScript. I'd also guess that you can't really combine import & VectorScript. I know that it is relatively easy to store & import classes and their graphic attributes. The storage can be another VW file (no programming needed), a text file (freeware available for this) or a VectorScript (a fair bit of programming is needed). EDIT: Well, I was wrong about import. The DWG-file changes class attributes in a rather strange manner. Embarrassing to me, but no brownie points to NNA, either! In effect, importing AutoCAD data can ruin your document.
  10. Can we have "material" or "make-up" as another attribute - kinda "cleverer than texture"? And a hierarchical or relational database to back it up? Ideally, perhaps, an ODBC-type of interface/middleware system. (Make-up? Well, that's just combination of materials. Some by length, some by height, some by volume, some by surface area. If you are not NNA staff, you get the picture.)
  11. In the very unlikely situation that symbol definitions would have been changed: a) you have used only one typeface. A script that sets all text objects to whatever typeface you choose, is dead easy to write. I probably have one, or 95% of it, already. Feel free to ask for free code. b) you have used several typefaces. Oh dear - even artificial intelligence does not include artificial crystal balls... c) your users have duplicated the symbols & changed fonts in their LOCAL libaries. In this situation, one can bring in symbol instances & use one's own definition.
  12. quote: Originally posted by Chris D: Our bricks here in the UK are 102.5 wide... I'd like to see bricks with that kind of tolerances? My guess is that they are 100 - 105 wide! Perhaps on average 102.5. As a young boy, I spent a week sorting bricks by size on a building site: the foundations were not quite accurate (what a surprise!) so for each wall the bricklayers wanted bricks of specific length. Anyway, I've tried associative dimensioning a couple of times, but for the reasons Mike describes, gave it up. It's just a waste of time and effort and a likely cause of errors. The situation is not an isolated event: too many features in VW are 'features', ie. they do not actually work in real life. I guess that is the price we pay for the cheap price, so to speak.
  13. Three points is three points. You can't have any additional definitions, since there is only one possible arc that can be drawn through three points.
  14. Despite full reinstallation of OS X & drivers, we have one Mac that does not print via Ethernet to the 130NR. Incidentally (related to getting an el cheapo colour laser), we put an ancient G4 PowerBook to act as an USB shared printing server and that works... No difference in speed, either.
  15. There is a free gradient colour creation utility called 'A Pint of Paint' by yours truly available at VectorDepot. No colour charts included - you have to find out the RGB values from manufacturers.
  16. Still, this is a serious design fault in PIOs and symbols.
  17. Just to get the record straight: WildTools is an add on which seems to cost USD 219. Probably not a bad price, but way above what the average VW user is willing to pay (which is zero). Eg. Motivo (the hatch creator) disappeared because no-one bought it; instead, the author was abused for wanting money for it.
  18. David - do you mean that you actually 'draw in scale'? VW is supposed to be always used in 1:1 scale, with the 'apparent' (printing) scale handled as a layer scale and/or viewport scale. All objects are in real world dimensions. In viewports there is the annotation 'layer' which is in 'paper scale' 1:1 - this might help. Or maybe I misunderstand? As comes to PIOs, quite a few (including drawing sheet items) ship with the program and you will find them extremely useful. Can't really recommend rolling your own, tho!
  19. A G4/800 will be fine for most tasks, especially with OS9 or Classic. At present OS X makes VW quite slow, but hopefully the next release of OS X fixes at least part of the problem. I run VW under Classic in my G4.
  20. The biggest problem with DIY learning is that one can learn bad habits, which are difficult to get rid of. In my time as a trainer, people with little knowledge were by far the worst ones to train - even (good) AutoCAD users were generally easier.
  21. A colleague next door is wondering whether they should move from AutoCAD to Revit. A mid-sized practice, some 40 people, mostly smallish projects, very pragmatic stuff (Seven-Eleven convenience stores and KFC outlets are their bread and butter, so to speak), but quite a mix overall. I of course mentioned VW as a possibility, but was asked how it compares with Revit. Well, I have no idea, but perhaps someone can educate me.
  22. One more technique, not so much for dividing, but related: In the Object Info, go to the dimension you want to change and type the calculation, eg. if the current width of a rectangle is 3600 and you want 1/7 of it, type /7 behind the 3600 and press enter. For creating duplicates at odd distances (like that 514.28571428571 (3600/7), not to mention odd x/y displacement combinations, there are free 'duplicate by vector' utilities at VectorDepot. You can use the four basic arithmetic operators (+ - * /) in all dialogs, too, like layer scale, object scaling and so on. [ 12-16-2004, 07:26 AM: Message edited by: Petri ]
  23. Sorry, Nicholas - you must be mistaken re defaults to instances. But as comes to the use of records, that is exactly how one uses them for doors and similar.
  24. I think I know what you are talking about... (We are architects, urban designers and planners and our projects always seem push VW beyond its limits.) I probably even have the VW add-ons needed - well, not all, but quite a few, perhaps 75%. They combine GIS-techniques with parametric objects and I would not hesitate taking on such a job, technologically speaking, that is. I might use additional software, but not other CAD, rather a full GIS (eg. MapInfo) and a database (eg. FileMaker Pro). The latter can drive VW to a degree via AppleScripts. Accuracy is no longer a problem: we are at present working on a project 1 km wide and 20 km long and there is no loss of accuracy. You will need several 'representations' of the data, several geographic areas and so on, but all this is doable in VW. My parametric buildings can be configured to show themselves in different levels of detail, from boxes to semi-detailed, and gross floor areas (& volumes), plot ratios etc. are calculated and I can export data not only to CAD but also to GIS. Quite honestly, I don't think AutoCAD would be any better - probably worse. The alternatives to VW might be ArchiCAD, MicroStation, ArcView (with 3D Analyser, possibly also Network Analyser and Axwoman - a space syntax tool for ArcView) and maybe Enviro.
×
×
  • Create New...