Jump to content

Petri

Member
  • Posts

    2,011
  • Joined

  • Last visited

Everything posted by Petri

  1. Robert, 51000 points does not sound much to me so if the VW 10 DTM chokes on that, it is still useless. OK, it may be a lot for a single house site, but there are other types of projects... With filtering, I have spent endless hours in getting rid of intersecting polygons; when converting the 3D polys to 3D loci, the problem per se goes away, but of course produces wrong results. And boy, is it difficult to find these intersections, as there is a dialog for each and every one of them, reporting page-related coordinates! Why can one buy a $200 DTM add-on to AutoCAD, one which works with hundreds of thousands of points, can use attribute data to generate the model (the standard way of getting terrain info from GIS systems), does slope analysis correctly etc etc, but one has to pay significantly more for the inferior (mostly useless) DTM capability in VW?
  2. Katie, you SHOULD tell how these style (class) names are modifid to be useful or point the person to the appropriate tech note or manual section. I'm sick and tired of giving the same instructions over and over again.
  3. Pamela, Check http://www.vectordepot.com/PlugIns1.shtml and also the marketplace of the site for useful add-ons. I think the one that might help you is called Broken Line; I've been thinking of publishing my 'Marker Poly' which does pretty much the same, but with polygons. Stay tuned to VectorDepot - the premium 'shame list' of NNA's shortcomings...
  4. John, Let's say it is doable, but quite complex. If I had hundreds of walls to create, I might write a script, but (after thinking about it a bit more), only might.
  5. Too many uncertainties to my humble taste. If the polygons were rectangular & have exactly 4 (or 5) vertices, it might be feasible, if not, then not. In either case, in the time you join the walls, you draw them. Someone of course may have resolved the somewhat complex trigonometry and logic already, but starting from scratch is not really appealing.
  6. Do the ungrouping in a 3D view.
  7. quote: Originally posted by propstuff: Exactly the same thing that happens now if you use the Undo command 1,2, 3, or whatever times. Yes, I know Adobe's approach, but can't really see the benefits. The implementation of the undo interface won't make the operations themselves any faster - if anything, it could be slower. After a series of operations, you don't really know what you did at a particular stage. Even in PhotoShop, I know I make dozens of changes in a minute and have to use simple undo steps. Not that I would oppose a history palette, I just don't see it as a priority. Also, I did make a false assumption of your particular request: the issue has been raised earlier several times, often with 'non-linear' undos in mind, so my tone was unduly blunt.
  8. quote: Originally posted by propstuff:Being able to jump back to the desired instance directly would be a joy.While this is a nice idea, more often than not, undoing an undesired action in the past would also undo more recent actions, with unknown consequences. Consider the matter from time travel point of view: the last action is a solid subtraction. If you undo the creation of one of the objects used, what would happen to the subtraction?
  9. quote: Originally posted by PeterT: Petri, What version of Illustrator are you using, and and when you say "fully editable", do you mean it comes in as a Vector drawing with objects that can be moved about individually, deleted or modified? As individual vector elements that can be moved, deleted etc. into ancient Illustrator 7.
  10. I just did an EPSF export from VW 9.5 on Mac OS X and took it into Illustrator. Fully editable, no problems. Well, fonts did not export, but I had used TrueType fonts in the file. Your several consultants - well, I don't know what their problem is because I have used Illustrator hundreds of times to touch up VW graphics.
  11. quote: Originally posted by P Retondo: Toggling "scale text" in my layers options does not affect this behavior. You aren't doing anything wrong and the behaviour is not a bug - I believe this is how it is designed to work. Whether it is good design, is another issue. I can't even guess whether the behaviour can be changed. The 'scale text' toggle is not actually a layer option, but rather tells the program whether to change text size when the scale of a layer is changed.
  12. quote: Originally posted by Petri: quote:Originally posted by P Retondo: i think there are two much better alternatives: 1) to use only the "None" class when bringing in automated or imported objects; or, Which is 'no classes' To continue: I am not sure how well this would work. It would then be left to the user to reclassify everything in every symbol. Even 'bad' class names are better than no classes at all in complex symbols. I have quite enough experience in editing imported symbols (or AutoCAD files without layers) to have this opinion. A typical case has been furniture.
  13. quote: Originally posted by P Retondo: i think there are two much better alternatives: 1) to use only the "None" class when bringing in automated or imported objects; or, Which is 'no classes' quote: 2) presenting a dialog box giving the user options about how to set up a class structure for the object - a more powerful option.Theoretically a good idea, but before one knows how a symbol is constructed, not really a goer. quote: Besides eliminating the annoyance of having to re-tailor names and attributes, either of these alternatives would prevent the time-consuming side-effect of PIO use that we currently suffer from - having to edit all of our saved sheets to properly display or hide the new classes.These (obvious) problems are caused by lack of communication & instructions - and therefore the poor user, not so much by technical reasons. I'm sure most veteran users know that I am not an apologist for NNA - on the contrary.
  14. quote: Originally posted by P Retondo: Petri, if you have 500 classes, I'm impressed No need to be: they usually come from imported AutoCAD drawings by others. quote: It's not that I don't agree that "Style 1", etc., are silly names. It's that I believe the issue is deeper than just the naming. The program is telling us what to name the classes, No, not really. You can give the classes any name you like. quote: and is also telling us that we will have these classes(and their default attributes), whether we want them or not, if we want to use a PIO. Not if you edit the lists. And the classes do not have default attributes. quote: This makes it more difficult to tailor the use of VW to each user's standard and way of working. Agreed, a bit more difficult, but only a bit. quote: By the way, this issue also goes beyond window and door parts - it applies to other PIOs, and to some of our library symbols, which drag unwanted classes into the picture when they are used. The only alternative would be to have no classes in library symbols. [ 04-06-2004, 07:12 PM: Message edited by: Petri ]
  15. quote: Originally posted by skfurn: I've been wanting to export drawings for my website in JPEG format. By far, the best results with maximum control come from a slightly convoluted process: print as PDF, open in PhotoShop, save as JPEG. In OS 9, there is the excellent alternative of using Print2Pict to create GIFs, which, for my money, are just as good as JPEGs, if not better. And if control is not a huge issue, screen shots are not a bad method, either, taken to PhotoShop or whatever you have, for cropping etc.
  16. Sorry - I disagree. I have files with hundreds (up to 500?) classes and the last thing I want is ten pop-ups with 500 classes. Control, control.
  17. quote: Originally posted by mike m oz: I still maintain however that it shouldn't be this hard. Well, ideally not, but when I have gone through the alternative scenarios in my mind, I have generally found them even worse, at least with the current PIO concept & technical structure. Since I write PIOs myself, you can bet I have thought of the matter - I don't enjoy the process any more than you do, but I can't think of a better way. One alternative would be to have text entry by typing. No thank you! Creating new classes via PIO interface does not appeal to me either. If you make that too easy, you end up with too many too easily. This stance rules, in my mind, out the seemingly appealing feature of FileMaker Pro: the author of the system may enable the end user to edit value lists on the fly. Well, as an occasional FileMaker developer, I have done this on a couple of occasions, with disastrous results. Won't do it again, not even to databases I use myself. Call me a control freak, but the current approach has its benefits as it gives at least some control and consistency, which is important in a practice with more than one person. The improvement that I would wholeheartedly support is a central depository of value lists (again, a FileMaker feature) so that in the PIO one would only need to define which list to use in what popup. Unfortunately I have the feeling that this would be a major change in the PIO architecture. I probably should have mentioned this before as a tip: in my colour/material value lists, I always have a choice called 'Special.' This I use for the unexpected colour or texture that is desperately needed in a project. Now, as comes to this famous stair and your - understandable - request for more options, well, I have two quite complex PIOs with so many parameters that the object info does not show them all at once even with 1600x1200 resolution. And boy, are they difficult to use! One can easily go over the top. In my view, there are so many more fundamental flaws and shortcomings in the stair PIO that more options is not a priority to me. On the other hand, your wish would be quite easy to fulfil: half a dozen popups (and, hey, lists for you to change & maintain) and the odd additional line of code here and there. Anyways, I'm glad I was able to help so, in exchange, I hereby nominate you as the value list editing advocate on this board. I have my hands full on the mailing list, where this question pops up (well, indeed...) at regular intervals.
  18. A better eyedropper tool is available at http://www.vectorbits.com/ Manuel Garcia de Parede has created this excellent tool and sells it for a meagre USD 10. Demo is free. It does class attributes, text attributes and wall heights. [ 03-24-2004, 06:09 AM: Message edited by: Petri ]
  19. quote: Originally posted by iboymatt: if shown to you would only take 1/2 hour. Much work could indeed be done to improve useablity of the system set up. Surely it does not take half an hour! Well, maybe if you include the time you need to think what classes you want to use, but that is another thing. Instructions are eg. in my message http://techboard.nemetschek.net/ubb/ultimatebb.php?ubb=get_topic;f=12;t=003384;p=1#000005 You can even type the list in a word processor and copy & paste it into the value list. After you know what the classes will be, it takes a minute or two.
  20. Well, Mike, the good folks at NNA are not clairvoyants and cannot possibly guess what classes users might want to use.
  21. Well, here's what I'd do: run this script. PROCEDURE DelDups; { ? Petri Sakkinen 2000 - 2004 } VAR x, y : REAL; lName, sName : STRING; sN : ARRAY [1..1000] OF STRING; xS, yS : ARRAY [1..1000] OF REAL; sym : ARRAY [1..1000] OF HANDLE; i, j, n : INTEGER; ok : BOOLEAN; PROCEDURE MakeArrays (h : HANDLE); BEGIN GETSYMLOC(h, x, y); sym := h; xS := x; yS := y; sN := GETSYMNAME(h); i := i+1; END; PROCEDURE CheckForDups; BEGIN FOR n := 1 TO i DO BEGIN x := xS[n]; y := yS[n]; sName := sN[n]; FOR j := n+1 TO i DO IF((xS[j] = x) AND (yS[j] = y) AND (sN[j] = sName)) THEN DELOBJECT(sym[j]); END; END; BEGIN ok := YNDIALOG('Delete duplicate symbols on the active layer?'); IF ok THEN BEGIN i := 1; lName := GETLNAME(ACTLAYER); FOREACHOBJECT(MakeArrays, (T=Symbol) & (L=lName)); CheckForDups; END; END; RUN(DelDups); And you guessed it: it was written exactly to get rid of multiple plant symbols on top of each other. Other possibilities include: - a symbol accidentally placed in or moved to a location outside what you consider 'the drawing' - a symbol in a wrong, invisible class - your legend may have the symbol (this would not account for three, but as a general rule) In the database query, it is a good idea to limit the listing to the appropriate layers and classes.
  22. Does anyone have experience with Onyx Tree Pro? Issues I am wondering about are - difficulty of use - size of models The latter is especially important in large-scale projects. Then of course the trees do not have to be highly detailed, so is it possible to generate sort of 'exaggerated' foliage with less vertices or do some other clever tricks to the same effect? I hate my current lollipop etc. trees but at least they render fast...
  23. I believe you want 'duplicate by vector' ie. by distance of two user-defined points. The lack of this (and respective move) very basic function has puzzled many users - and at least one, Peter Vandewalle, has put tools for this into public domain. See http://www.vectordepot.com/PlugIns1.shtml, files Pt2Pt Copy & Pt2Pt Move. Haven't tested them as I have had my own for many years. Peter has chosen menu command approach, mine are palette tools. If they are not encrypted, you may be able to use them to create tools - that is in my view a more efficient approach.
  24. Petri

    linear object

    GetSymLoc gives you the starting point, then you can calculate the endpoint with GetSymRot & the LineLength of the PIO.
  25. quote: Originally posted by mike m oz: Surely it can't be that difficult to have them with real names rather than these generic ones. You are right - it is not difficult. Just edit the pop-up value lists of the PIOs in question.
×
×
  • Create New...