Jump to content

P Retondo

Member
  • Posts

    1,914
  • Joined

  • Last visited

Posts posted by P Retondo

  1. Andrew, good thought, but I already tried that to no effect. Biplab, I will send you the two files so you can see what I'm talking about. Your description sounds very close to what I'm seeing. I don't have your email, however.

    [ 09-10-2004, 01:43 AM: Message edited by: P Retondo ]

  2. Katie, geometry . . . what can we say?

    Using the reshape methods described above, I rely on the "perpendicular" and "parallel" screen cues to know that I'm not skewing the shape instead of stretching it. "Perpendicular" means you are constrained to a line perpendicular to a side of the shape, and "Parallel" means you are constrained to a line parallel to a side. But - these constraints only sometimes appear. I wish I knew how and why. Any tips from NNA?

    P.S.: if you can't get these constraints to appear, do something like the following: if you are reshaping using the center of a side, pull it to the center of the opposite side (screen hint will say "center"). Keeping your cursor snapped to that point, enter a NEGATIVE number in the "L" variable at the top of the screen, push "Enter" and click the mouse. Your side will move out the distance you entered in the "L" field, and the rectangle will stay a rectangle. (If you were trying to make the rectangle smaller, enter a POSITIVE number in the "L" field.)

    [ 09-10-2004, 01:37 AM: Message edited by: P Retondo ]

  3. Biplap & Kaare, where do I find the command to import an IGES file? I can find "Export IGES" under File->Import/Export . . . oops, I found it in my Workspace editor and added it to the menu!

    But the object I get, although it is identified as a NURBS surface, is "kinky," not smooth the way it looks in Rhino. The nurbs curves that aligned with the surface in Rhino are no longer aligned, and are composed of a series of chords. Is there some kind of limitation involved here? Degree, number of nodes, something else?

  4. Tom, thanks for the feedback. I guess there isn't a way to swap NURBS objects back and forth. I wish Rhino and VW could combine the best features of both programs into one.

    PS: actually, check out this same thread in the 3d discussion area. It turns out you can import an IGES file, and get NURBS objects to cross over. But it hasn't been totally satisfactory.

    [ 09-09-2004, 02:06 AM: Message edited by: P Retondo ]

  5. Tom, I tried the experiment you suggest, and was able to select any two given corners using a marquee. I don't understand your comment - it is true of certain asymmetrical quadrilaterals, but not of a rotated rectangle.

    Grabbing the center without using the marquee tool at all is, however, the quicker way to get the desired results. Two ways to accomplish the same effect.

    [ 09-09-2004, 01:35 AM: Message edited by: P Retondo ]

  6. I've been working between VW 10.5.1 and Rhino to create a 3d model of a curved lattice-work railing. Rhino can map a complex flat surface onto a curved surface, but I can't find a way except through .dwg import and export to get the objects back into VW, which then come in as 3d polys or meshes, not nurbs. Is there any way to do this? Does VW import IGES files, and would this help?

  7. I've been working between VW 10.5.1 and Rhino to create a 3d model of a curved lattice-work railing. Rhino can map a complex flat surface onto a curved surface, but I can't find a way except through .dwg import and export to get the objects back into VW, which then come in as 3d polys or meshes, not nurbs. Is there any way to do this? Does VW import IGES files, and would this help?

  8. I generally use the "transparent" option for cursor cues, since they are less likely to block the view of objects I want to see. But when I want to snap to something in the region of an object with a fill pattern, it is often impossible to read the cues unless "opaque cues" has been checked in the program preferences. It would be great if a key like "alt" were designated that could toggle between transparent and opaque, so that we could always get the smart cursor visibility desired, on the fly.

  9. Nicholas gives an excellent description of what you need to do. If you are an AutoCAD user, you can get tripped up by the simple differences in the mechanical steps each program operates with - 1) unlike in AutoCAD, with VW you first have to select the object(s) whose vertices you want to move, before you drag the marquee. Your stretch action will skip any vertices within the marquee that belong to an unselected object. 2) You can activate the 2d reshape tool, then click and shift click to populate your selection set, but only with polylines and polygons. To stretch multiple lines and rectangles, you have to make your selection before you activate 2d reshape.

  10. jan15, cairo is referring to the AutoCAD stretch which moves selected (but not all!) vertices of multiple objects. The method is different from "resizing" a group - one major difference is that when objects are resized intermediate vertices are translated proportionately, whereas with AutoCAD "stretch" all selected vertices are translated by the same vector (distance + direction). In this sense, "stretch" is a misnomer and the command doesn't mimic elastic behavior as seen in the real world.

    VW 2d reshape can accomplish the same thing as AutoCAD stretch, almost (I first learned about this capability from Katie in this forum!). You can select vertices from a set of multiple objects to be stretched at once. If the set contains lines or rectangles, you have to first select those objects before selecting the reshape tool.

    The method will work on rectangles and lines as well as polylines and polygons, but not on arcs or circles. I don't think there is any limit to the number of vertices you can move at one time. As far as I know the lasso (= fence) selection method won't work to select the vertices, a drawback when compared to AutoCAD, but I've never actually used that whereas when I work in AutoCAD the stretch command using a marquee is one of my top 5 tools. In both programs, it's a tremendous time-saver.

    [ 07-30-2004, 02:01 AM: Message edited by: P Retondo ]

  11. Further on this problem: when I create a group, it is assigned to my new problem class, instead of to the active class.

    Bruce, I think you responded some time ago to a similar problem with corrupt or problem classes in a file containing a large number of objects similar to Kevin's. As I recall, you said something about a list being too large - I'll check my old emails to be more specific.

  12. I find that wall join is, like some other editing tools in VW, strangely affected by nearby walls or other objects that should have nothing to do with the operation (I submitted a sample file to bugsubmit a long time ago about a similar trim tool bug). When quirky results occur, I put the two walls I want to join into a group, enter the group, and the operation works successfully. There is obviously something wrong with the code when the proximity of uninvolved objects affects an operation.

    VW 10.5.1

    Win2K/XP

  13. Katie and Petri, you are both right, in a way - it is confusing, and it is just as though I had renamed the "None" class - but I didn't. Just created a new class, and everything that was "None" before became the newly created class: 1) all objects assigned to "None" were reassigned, 2) all defaults set to "None" were changed, 3) all saved views set to Active Class = "None" were changed. "None" class was changed from visible to invisible in all saved views. This was all done by the program on its own in very little time, and it took me 6 hours to fix.

  14. I created a couple of new classes in my project. All objects (numbering in the thousands) in the "None" class on every layer, including windows embedded in walls and layer links, were converted to one of my new classes. All of my saved views were converted to having this new class as the active class. I'm still fixing all of this after several hours. Anyone have an explanation for this occurrence, other than one terrible bug?

    More odd behavior: my new class shows up unexpectedly in the Select Wall Type plug-in - a wall type I created was given this default class assignment automatically. Also, if I delete a class in the project, objects that were assigned to that class are now assigned to the new class instead of to "None." And operations involving display of objects in this new class are very sluggish - e.g., bringing up a view with a layer link to the layer containing the object.

    VW 10.5.1

    Win2K

    [ 07-26-2004, 03:23 AM: Message edited by: P Retondo ]

  15. In the natural world it is extremely rare for a piece of wood to have two heart centers - so why does the VW wood trim PIO show "S" shaped grain patterns? In all conventional architectural details, the grain is shown as roughly concentric curving lines. Could this tool be revised to use the traditional graphics? If nicely done, this would truly be a time-saving tool, but as it is currently designed, the tool is unusable if you care at all about the authority of your drawings.

    This raises in my mind a question of software engineering process - how does it occur that something is programmed contrary to reality and universal drafting convention?

    VW 10.5.1

    [ 05-31-2004, 03:36 PM: Message edited by: P Retondo ]

  16. Colin, had the same problem with an HP 800 (non-PS). Updated the driver to v 5.35, and the problem disappeared. Things may be different with a postcript printer.

    VW 10.5.1

    Win XP

    [ 05-27-2004, 01:03 AM: Message edited by: P Retondo ]

  17. Wall elements set to "default line style" take their color, lineweight and dash style from the attribute palette settings at the time the wall is created. When editing a wall's cavity lines, only color can be changed via the attribute palette, and lineweight and dash style of wall cavity lines have to be changed in the cavity edit dialog box (via the OIP).

    However, if the class to which the wall is assigned has the "use at creation" button checked in its setup box, then the class style supercedes the attribute box defaults, except with respect to the weight and dash style of cavity lines.

    Whew! This is way too complicated. The whole wall type method needs to be revamped so that there is a more intuitive and rational way to control and edit the way these objects look. We need something akin to the method for setting attributes for classes, but with control over all the elements of the object. Come to think of it, how about having a complex class type for walls, with a dialog box that includes other wall attribute controls in addition to the usual items found in the class edit box?

    This could replace the "wall type" concept altogether. I.e., make it so that a named wall class defines all cavity, thickness, and height attributes. You want your wall to be a certain type - choose that by assigning a class. You want that wall type to be globally different - edit the class.

    VW 10.5.1

    [ 05-20-2004, 12:16 AM: Message edited by: P Retondo ]

×
×
  • Create New...