Jump to content

Petri

Member
  • Posts

    2,011
  • Joined

  • Last visited

Everything posted by Petri

  1. Changing default data does not affect placed instances. Never does.
  2. Sorts by Text fields (and Name) are alphabetic, by Number fields numeric.
  3. Permissions? What does 'Get Info' say about ownership and permissions, Jim?
  4. Why do you need to import your own data? Try first setting layer scales to be the same.
  5. Well, Jon - no-one expects you to give them out for free, I'd imagine. They may not buy them, but I can't recall seeing abusive anonymous messages berating you...
  6. I had a lengthy discussion with him - he was totally frustrated and even annoyed by the situation: various people on the Architosh-board and private emails demanding the utility to be free. Here we had a genuine, independent developer (not even a VW user himself), pushed out by the ignorance and stinginess of VW users: they want features, but when it comes to paying for them... Now, if I spend even several days in writing a program, why on earth should I give it to someone else for free?
  7. Jim - you are right, but also wrong. As long as one talks about doing exactly the same thing (like the conventional CAD - lines on electronic paper), you are right. However, programs such as ArchiCAD and VectorWorks are based on a different 'paradigm' altogether. (They are not the only ones.) After one gets used to thinking in modeling terms (I'm not talking even about 3D here), going back to the simplistic drafting is difficult. When for 15 years (= my case) one has manipulated walls, slabs, columns, roofs, beams, windows, doors etc, starting to even think about 'extending a line' seems - how should I say it? Arcane? So, it's not Ford vs Chevy at all! (I started with conventional CAD 1987...) [ 11-26-2004, 09:37 PM: Message edited by: Petri ]
  8. An Italian developer once had a hatch creation utility (you drew the hatch in the normal fashion and it converted the linework into a hatch), but virtually no-one bought it, so he gave up.
  9. quote: Originally posted by jan15: And it's easy to make hatches. You're the first one who has said that! Try creating anything more complex than simple cross-hatching or brick bond and I think you are in trouble...
  10. No such problem here - good for me, bad for figuring out the reason. Whoops - you said Office 2004... We have Office X - there are reports of Word 2004 being even slower than X, so we have not rushed to upgrade. [ 11-22-2004, 11:53 AM: Message edited by: Petri ]
  11. OK. Let's get back to the track, for the benefit of PJvH. One of the really excellent things in VW for landscape architects is scheduling of plants, garden/street furniture, surface areas and 'lenghts' (of, say, edge types or kerbs - curbs, to you Americans.) (Something that AutoCAD does not do, dear Jckii...) I understand that Landmark comes with predefined reports that may or may not suit one's preferences; modifying them or creating custom reports is fairly straightforward. I can't comment on the plant database, since we have not used it, but I'm sure it is better than nothing. G-Pang refers to workgroup referencing. Well, we use that to generate three different-looking drawings from one design file: a working drawing (a rather austere line drawing), a permit drawing (fewer details, a bit more pizzazz) and a marketing drawing (no details, but fancy presentation). If budgets would allow, the fourth type would be a 3D image. We prefer to do the design in the 'permit drawing' mode, but after contract documentation, often need to switch to work in working drawing mode - this takes roughly 5 minutes - and the permit-style is automatically generated from the working drawing. Of course the presentation drawing will also reflect the current design - if we so choose, that is.
  12. Been there, tried that - at least three times. A user group needs quite a user base to be functional and neither MC/VW nor ArchiCAD has not had that in Melbourne. Well, probably I was a lousy convenor.
  13. For vector data, VW uses the world coordinates of imported files (in my line of work, we are talking about millions of units in x/y cartesian coordinates) without a hiccup. But GeoTIFFs - no. And of course, VW won't even recognise EWC-files (the emerging standard for aerial photos; if you are on the Mac-platform, GraphicConverter is AFAK the only program that can open & convert EWC.)
  14. quote: Originally posted by jckii: Thank you, Petri, you chose to edit out of my post the most important issue with VW, which is drawing exhange among consultants. OK - let's go through this one by one. quote: If VW was able to come up with an export-to-DWG function that did not result in every one of my consultants (ALL of whom use AutoCAD) calling me up with problems with unusable files, what you're sayng might hold some water.After exchanging data with tens - no, hundreds - of consultants, I have never been called up about unusable files. Maybe the difference is that I know what I'm doing. quote: Don't give me that old line that "This is a common reaction from people who try to use VW in the same manner as AutoCAD" - I have gone by the book, and beyond, Well, something very fundamental is wrong then. Perhaps you had the wrong book? quote: from day one with VW, and regardless of how you use it, VW is riddled with problems that I never had in AutoCAD: the snaps are lousy, How? I think the snaps are quite good. What exactly is it that you can't snap to? quote: dimensioning is inconsistent and inaccurate,I have never noticed this - could you elaborate? quote: window, door and other parametric tools are hopelessly unreliable and inflexible, not to mention tricky to manipulate, They may be inadequate, but surely better than AutoCAD's standard parametric objects for the same. Unreliable - no. quote: workgroup referencing is cumbersome, obtuse and slow, But far superior to AutoCAD's XREFs. Different - yes. quote: and the very fact that the program has a "nudge" tool is testimony to the fact that accuracy is compromised. Please, don't be ridiculous! For things like loose furniture, text, even plants in the architect's site plan, it just makes life easier! The accuracy is not compromised a bit: nudged objects are in precise positions. quote: VW is fine for graphics, and maybe for small, one-person boutique projects - for accurate drafting and extensive documentation of large projects, forget it. Well, here is a scintilla of truth: VW is NOT a drafting program, but a design and modeling program. If one is at the drafting level in the food chain, AutoCAD may just be the ticket. quote: Add to that the fact that many intuitive, obvious drawing tools one would expect as standard in any decent CAD program are only available as "plug-ins" that one has to buy or download from somewhere else, and then install, or worse, that you have to write scripts for yourself.I thought that AutoCAD add-ons were a big industry... quote: We are architects, not computer geeks, and the last thing I want to worry about when drawing, designing, managing a building project is how to deal with, or expand, the ridiculous limitations of my software.Well, if this were so, why would Autodesk promote its (fairly) new aquisition Revit as the next generation tool for architects? (Not to mention the fact that we are NOT discussing architectural drafting here at all.) quote: Your trainees most likely use AutoCAD to do the parts of projects that VW cannot handle! True. Large terrain models (like 10 million points) cannot be created with VW. There are also some other more or less expensive 3rd party add-ons for AutoCAD that some people need for, say, subdivision planning and roadworks or GIS-functionality. But they do not have any need for plain vanlla AutoCAD, not to mention LT. One firm in question has LandCADD, but I don't think it has ever been used.
  15. quote: Originally posted by jckii: No. I don't know Landcadd, but do not buy VectorWorks if you can help it - in other words, if you're not on a Mac. Get AutoCAD LT: it costs about the same (OK, a little more), it references decently, is way more accurate and intuitive, This is a common reaction from people who try to use VW in the same manner as AutoCAD - except that I can't remember anyone saying that AutoCAD would be more intuitive. Having trained tens of landscape architects to use VW (many with prior AutoCAD experience and some with the choice available permanently), could not disagree more. Of my trainees, not a single one has - after the proper training and VW implementation - gone back to AutoCAD by choice. Some use AutoCAD to do specific parts of the projects, but usually bring the results to VW. The facts are that LandCADD requires full AutoCAD and that VW is exactly as accurate. Whether one needs Landmark is another thing; we have it, but the only feature we have ever used is the terrain modeler: our line of work is not suitable for the strictly regulated work process of Landmark (and we are not in the U.S.A.)
  16. quote: Originally posted by tgm: [You should be able to edit like symbols using the OIP, simple as that. Truly a no-brainer. Sorry, but I really have to disagree. Firstly, PIOs and symbols are two different animals and, secondly, both can contain several text items that may or may not need to have different fonts. The user interface is anything but a no-brainer - especially if one wants to edit a symbol via the OIP. As someone who has created both PIOs and symbol libraries for others, I appreciate your position, but there is no simple solution.
  17. All above is certainly good advice, but there are situations when circular paths are quite sufficient, by adding some half a meter of tolerance. If anyone wants the turning radius PIO, drop me a line: petri@4dform.com.au.
  18. Hmm - maybe I should post the one I have to VectorDepot.
  19. A - ha! You are not talking about symbols, but plug-in objects. With PIOs, the programmer decides how fonts are applied; the problem with the PIO approach is that the list of fonts does not reflect your system's fonts, but is 'semi-hard coded' in the value list of the parameter. If a PIO only contains one text item (or items that logically use the same font), the font menu is a more user-friendly solution.
  20. quote: Originally posted by tgm: Anyone from NNA want to comment on why all the symbols using text cannot be editted using OIP as stated above??? Tom A symbol can contain several text items, with different fonts. In the symbol definition, OIP works. You can't edit the symbol definition without entering it anyway - why would text be different?
  21. This feature is already in VW: parametric objects can be written in such a manner. I have at least a dozen or so: windows, glazed walls, balustrades, beams, parking spaces and so on. For some reason, the NNA Integrated Products team seems to come from the Drafting school of CAD and assumes that when you place an item in the model, you already know exactly how long, wide, tall etc. it should be and are willing to make adjustments numerically. Not that my home-brewed stuff would be ideal, far from it, because they have always been created in a hurry just to get a job done, but I rarely use NNA's PIOs.
  22. I run my VW 9 under Classic - simply because of the speed problem in OS X. 'Fortunately' I have some other programs that also require Classic (and no OS X version), so I need to have Classic running anyway. The selection speed (?) is indeed one of the most irritating issues, right after OIP slowness.
  23. In MC 6, MiniPascal commands were usually incorporated in the documents, in command palettes, but the other alternative was to have stand-alone macros. There may not be an extension at all (Mac users usually do not bother with such arcane concepts), but possiblities include TXT, VS, MP and what have you. The most common location for stand-alone macros was, I think, the MiniCAD folder or a subfolder in it. Check some old documents to see if they are in palettes; if so, option-clicking the macro opens the editor. Happy hunting!
  24. And THAT is where the danger hides - and the reason for suggesting the PIO option. Perhaps one could incorporate an update script (using FOREACHOBJECT(doIt, S='locationsymbol')) in a Saved Sheet or a printing command such as my little 'Print and stamp' (date and filename stamps updated, printing launched), but one beautiful day you forget... Well, the latter would be fairly fail-safe if CMD-P would be the shortcut for that and standard Print 'hidden' in a submenu. Whether one uses PIOs or symbols, there is the additional matter of remembering to recalculate the report.
×
×
  • Create New...