Jump to content

C. Andrew Dunning

  • Posts

  • Joined

Posts posted by C. Andrew Dunning

  1. Charles -

    1) If I REM out the subtraction, I can do the subtraction manually.

    2) The value returned is "0" (success).

    3) I believe the LNewObj handle is valid.

    I've built a stand-alone script to seperate this block from the rest. Here are 2 observations and a question I have when trying different things w. the "test mule:"

    1) If I REM out the subtraction and if I explode the 3D part of the object and look at the curtain part it is a solid addition (according to the OI box). If I ungroup the addition it is 3 parts: a large central panel and 2, smaller "sliver" ends. Their widths seem to correspond to the width of the "tail" I add to "wrap up" the curtain creation. This leads me to wonder if I'm creating the curve correctly.

    2) If I "unREM" the subtraction line, explode the PIO, and look at the resulting objects, I get 2: One is a solid addition that is in-essence the 3-part group mentioned above. The other is a solid subtraction that "contains" my extruded rectangle and the left-hand "sliver" of curtain.


    As a workaround, how can I "get at" just the central panel and subtract from that? The rest of my code dictates that my subtraction window will never get out as far as the 2 "sliver sections.


  2. Greetings!

    In a larger script (a point PIO), I am trying to subtract an extruded rectangle from a lofted surface, but am not having any luck. Below is a snippet of the code. Can one of you give me some direction?


    LftCurtHnd := CreateLoftSurfaces (PreLftCurtHnd, False, True, True);

    BeginXtrd (ScreenBottom-PIOZ,(ScreenBottom+ScreenHeight-PIOZ));

    Rect (-(ScreenWidth/2),6",(ScreenWidth/2),-6");


    ScrnRectHnd := LNewObj;

    SubStractOutcome := SubtractSolid (LftCurtHnd,ScrnRectHnd,FinalDrapeHnd);

  3. quote:

    Originally posted by mickey:

    I take it from the lack of response that either nobody knows what I'm talking about or it didn't get fixed.

    IMO, what is needed is a "mirror duplicate" tool - a tool that mirror-copies symbols, but places the copy "non-mirrored", instead of mirrored, as things are now. I regularly use a somewhat modified OLD version of just such a tool that came w. the Theatrical Lighting Toolkit a few years ago. Seeing that the code already sort-of exists, adding this tool to the current VW shouldn't be all that big of a deal...


  4. Are you having trouble opening the files in 12 - or are you having trouble, when in 12, importing the contents of the files through the Resource Browser? I've double-checked and have no problem opening the files in 12 (though, depending on VW settings, VW may want to append the name). If you're trying to do the latter, VW will not do that. Resources need to be in the same "whole-number" version of VW that you are running.

    In case you're still having difficulty, I've posted a VW12 file of the Pixelline symbols at www.landrudesign.com/public.

  5. Here is my approach:

    All of my project geometry exists on a single design layer.

    Drawings/plates are created using ViewPorts that reference the geometry/project elements.

    The ViewPorts "live" on Sheet Layers that contain title blocks and borders. The only difference between my different Sheet Layers are their intended final drawing size.

    I control ViewPort visibility using class visibilities and Saved Sheets.

    The title block is a symbol and the same for each instance (each Sheet Layer). Therefore, things like the project name and other details are the same, regardless of the sheet it is on.

    Within the title block symbol are text elements that "live" in different classes. Therefore, by changing class visibilities for different saved sheets, I am changing the specific drawing name (rigging, scenic, lighting, etc.), its plate number, and its scale - as shown in the title block. I have scripts that automate this a little, including getting the scale of specific ViewPorts.

    Forgive me if I've confused you - or muddied the waters more than you'd wanted. This is simply the way I've grown to like working. If you're interested, I have a sample template file posted at www.landrudesign.com/Downloads_Main.htm. It might give you a rough idea of what I've tried to describe...

  6. Good morning!

    I'm attempting to use a script to reference an already-existing arc to place a path PIO. I'm having a problem getting dimensions from the saved/referenced arc. I've tried GetSegPt1 and HCenter - and GetArc and Get2DPt. The problem is that the PIO is seeing the referenced object as a group and is returning the same values for both the starting point and the arc center - though the start and sweep angles are accurate. Doing the math means that the resulting radius is 0. Do arcs not remain arcs when used as profiles? How can I get the script to "see" the arc correctly?


    C. Andrew Dunning

    Landru Design


    Nashville, TN




  7. I have a script that is being turned into a Path PIO. It (in theory) uses these 2 polylines to produce a Loft surface (after grouping them).

    The catch is that the Loft surface is not being created. In a Path object, shouldn't this work? In a "one-shot" script that does the above w/o creating a PIO, things work just fine.

    Thanks for any tips...

  8. Back w. ideas...

    Though not something that I need every day having a curved curtain tool was interesting enough that I posted a question to the VectorScript mailing list. Thanks to some pretty big "get me started" help from one of the other "listers," Eric Torola, I now have a basic Curved Curtain tool. Of yet, there is no error trapping and it is a one-time Arc -> Curtain "transformer" that lets the user set the pleat depth, pleat segment length, and overall height.

    If you're interested, I've got what we've done so far posted at: http://www.landrudesign.com/public/CurvedCurtain.txt.

    The next step is figuring out how to make this thing into a PIO, with a few adjustable parameters. As w. a number of other things regarding this idea that I've had to learn, this will be part of my learning curve, as well. I'm open to any ideas...

    Regards -

  9. I'd echo the need from the original post.

    Drawing "squiggly lines" is doable, but to get something that actually LOOKS like (and, is easily recognizable as) a curtain takes a good bit of time.

    Using an extrusion of a curve is a quick solution, but doesn't look like a curtain in either 2D or 3D. Again, it needs to be easily recognizable (and not look like just another line).

    When I've needed a curved curtain, I've exploded a curtain object and taken the first couple of curved and done a lot of radial copying. It takes an eternity, but looks good...

  10. Hugo -

    Though VW won't do it, if this is something you are needing, let me know the dimensions of the ellipse and I'd be happy to generate the arcs for you. I've got an old script for GeneriCADD that converts ellipses to their "approximations" using either 4 or 8 arcs.

  11. Jonathan -

    > If you have an industry series product then you will have it, if you have the basic VectorWorks then you will not. <

    From what I can tell, "If you have an industry series product EXCEPT SPOTLIGHT then you will have it" might be more accurate. Before I posted my other reply to you I did a little checking on-line and in the WorkSpace editor dialog. Not to be found.

    If CS 2 does indeed fix what seems to me to be a bug, it strikes me as a little odd that that fix isn't part of the "vanilla" VW.

  12. BG -

    Ahhh...Generic CAD... Now, there are pleasent words from the past... ;-) When I switched to VW, there were (and, still are) lots of "But Generic did this..." moments. I still keep 6.5.1 loaded on my machines. There are still a few things once-in-a-while I need to do that I can only do in GC w. some of the old scripts.

  13. > Autocad users who are vectorwork converts are always asking for pt2pt copy... <

    And for good reason. Though it is not always easy to explain the "whys" of these 2 tools, once used they quickly get put on the "But of course that's the way to do it" list. I remain a but surprised that they aren't "stock" fare in VW - though w. the ease of adding/using these scripts it really doesn't matter...

  14. Mike -

    I've been using "Option B" (as in the example you sent). It is somewhat of a work-around, but:

    - It is seldom practical to split up drawing geometry like that. For many projects I need to be working on the actual geometry as a whole.

    - Though I do rotate VPs from time to time, I've had occasional difficulty getting consitent results - especially in being able to predict how text will react. (Perhaps a second wish of VPs being more "aware" of being rotated?)

    I have seen the VectorBits Plug-In but am pretty leery about a tool that changes the actual drawing geometry.

    I've grown to like the way the Working Plane palette works and could see my wish being implemented in a similar way (or, as part of that tool). That's why I used that as a reference in my original post. In fact, before posting, I did try using that to rotate my view. Didn't work so well...

  15. I find myself wishing for this one a lot: The ability to rotate (and store) a working view (similar to changing Working Planes).

    I often work on projects where, for whatever reason, either all or a portion of the drawing has to be drawn at an angle that makes drawing somewhat challenging. Being able to rotate the view (not the geometry itself) would be quite welcome.

    Changing the grid angle is somewhat of a work-around, but does not quite fill the need.

  16. Originally posted by Ethan:

    > What does it do? <

    It toggles the visibility of the crop border of selected VPs.

    > I'm also finding it very time-consuming to turn labels on and off in Spotlight for printing, since I now have to click on EVERY SINGLE viewport in all 3 of my plates <

    You would really appreicate the ViewPort Pack @ www.panmzercad.com. It includes a View Manager that lets you do all of this for all of your Saved Views and ViewPorts from one window.

  17. Originally posted by Ethan:

    > I used to like to set up my viewport crops into a class so I could easily turn them on and off. >

    Have you seen the script below, from Vector Depot?

    {Patrick B. McConnell}

    PROCEDURE toggle;

    PROCEDURE doit(h : handle);


    hVport : HANDLE;


    hVport := GetVPCropObject(h);

    IF GetLS(hVport) = 0 THEN SetLS(hVport, 2);

    IF GetLW(hVPort) <> 0 THEN BEGIN

    {alrtDialog('Not zero');}

    SetLW(hVport, 0);



    { alrtDialog('Zero');}

    SetLW(hVport, 12);




    ForEachObject(doit,((SEL=True) AND (T=122)));



  • Create New...