Jump to content

LarryO

Member
  • Posts

    428
  • Joined

  • Last visited

Everything posted by LarryO

  1. Does anyone know why my script chimes every time it is selected from the tool sets, every instance at placement and anytime I use one of the pop-up selections? I originally wrote this for VW2013 but other than the chiming it works fine in VW2019. PROCEDURE Wedgie_Anchor; VAR Bool1:BOOLEAN; TempI1:INTEGER; LongI1,LongI2:LONGINT; BoltLength,ShaftRadius,ShaftLength,ThreadLength,rSlot,rHeight,NutThickness,WasherThickness, DocUPI,SelectPtX1,SelectPtY1,SelectPtX2,SelectPtY2,RingThickness,rETBN:REAL; Units2Mark,UnitsMark,PIO_Name:STRING; PIO_Handle,PIO_Record,PIO_ParentWall,ObjHandle,hWasher,hNut:HANDLE; ar3BoltSize:ARRAY[1..3]OF CHAR; TempArray:ARRAY[1..16]OF CHAR; TempDynArray:DYNARRAY[]OF CHAR; BEGIN {Parameter Visibility} Bool1:=GetCustomObjectInfo(PIO_Name,PIO_Handle,PIO_Record,PIO_ParentWall); IF PAnchorSize='Custom' THEN BEGIN SetParameterVisibility(PIO_Handle,'BDiameter', TRUE); SetParameterVisibility(PIO_Handle,'OALength', TRUE); END ELSE BEGIN SetParameterVisibility(PIO_Handle,'BDiameter', FALSE); SetParameterVisibility(PIO_Handle,'OALength', FALSE); END; {PushAttrs;} GetUnits(LongI1,LongI2,TempI1,DocUPI,UnitsMark,Units2Mark); ar3BoltSize:=PAnchorSize; IF ('3/8'=ar3BoltSize) | ('1/2'=ar3BoltSize) THEN WasherThickness:=1.6mm {1.6mm = 3/8" & 1/2" Narrow washer thickness} ELSE WasherThickness:=2.5mm; {2.5mm = 5/8", 3/4" & 1" Narrow washer thickness} RingThickness:=((Str2Num(ar3BoltSize)*8)-1)*0.5mm; BoltLength:=POALength; {Extra Thread Beyound Nut - rETBN} rETBN:=WasherThickness+DocUPI*Str2Num(ar3BoltSize)*1.5; {BOLT DIAMETER formula is DocUPI*Str2Num(ar3BoltSize)} ShaftRadius:=DocUPI*Str2Num(ar3BoltSize)/2; TempArray:=PAnchorSize; TempDynArray:=TempArray; Delete(TempDynArray,1,6); TempI1:=Pos('"',TempDynArray); Delete(TempDynArray,TempI1,TempI1); BoltLength:=DocUPI*(Str2Num(Copy(TempDynArray,1,TempI1))); IF PAnchorSize='Custom' THEN BEGIN rETBN:=PBDiameter*1.5; ShaftRadius:=PBDiameter/2; BoltLength:=POALength; END; {formula for expansion portion is ratio from Ø3/8" anchor which is 1" Long to Ø5/8" anchor which is 1.5" Long} ThreadLength:=BoltLength-25.4mm-2*(ShaftRadius*2-9.525mm); ShaftLength:=Boltlength-ThreadLength; Locus(0,0); {Orgin indicator} {Threaded end} OpenPoly; BeginPoly; AddPoint((-ShaftRadius+0.53mm),3.175mm); AddPoint((-ShaftRadius+0.53mm),0.0); AddPoint(-ShaftRadius,0.0); AddPoint(-ShaftRadius,-ThreadLength+3.175mm); AddPoint((-ShaftRadius+1.95385mm),(-ThreadLength)); AddPoint((ShaftRadius-1.95385mm),(-ThreadLength)); AddPoint(ShaftRadius,-ThreadLength+3.175mm); AddPoint(ShaftRadius,0.0); AddPoint((ShaftRadius-0.53mm),0.0); AddPoint((ShaftRadius-0.53mm),3.175mm); EndPoly; ObjHandle:=LNewObj; HMove(ObjHandle,0.0,ThreadLength-rETBN); {Threads} MoveTo((-ShaftRadius+0.53mm),ThreadLength-rETBN); LineTo((ShaftRadius-0.53mm),ThreadLength-rETBN); MoveTo(-ShaftRadius,3.175mm-rETBN); LineTo(ShaftRadius,3.175mm-rETBN); {The following 2 lines are drawn as hidden lines} PushAttrs;LSByClass;LWByClass;PenColorByClass;NameClass('Pen_0.13-Hidden'); MoveTo(-ShaftRadius+1.06mm,4mm-rETBN-2.58375mm); LineTo(-ShaftRadius+1.06mm,ThreadLength-rETBN); MoveTo(ShaftRadius-1.06mm,4mm-rETBN-2.58375mm); LineTo(ShaftRadius-1.06mm,ThreadLength-rETBN); PopAttrs; {Tapered end} BeginPoly; AddPoint(-ShaftRadius+3/64",3.175mm); AddPoint(-ShaftRadius+1/64",BoltLength-(ThreadLength+1mm)); AddPoint(ShaftRadius-1/64",BoltLength-(ThreadLength+1mm)); AddPoint(ShaftRadius-3/64",3.175mm); EndPoly; ObjHandle:=LNewObj; HMove(ObjHandle,0.0,ThreadLength+RingThickness-rETBN); {Begin Expansion Collar} rSlot:=((ShaftRadius*16)-1)/64; {1/2 SLOT WIDTH} rHeight:=ShaftRadius+9.525mm; {Overall height of Collar} IF ShaftRadius<=4.7625mm THEN rHeight:=rHeight-3.175mm; {Bumps on Expansion Collar} ArcByCenter(ShaftRadius-3.175mm, rHeight/2+ThreadLength+RingThickness*2+3.175mm-rETBN, 3.969mm, 323.13, 73.74); ArcByCenter(-ShaftRadius+3.175mm, rHeight/2+ThreadLength+RingThickness*2+3.175mm-rETBN, 3.969mm, 143.13, 73.74); PushAttrs;FillPat(1); ClosePoly; BeginPoly; AddPoint(-ShaftRadius,0.0); AddPoint(-ShaftRadius,rHeight); AddPoint(-rSlot,rHeight); ArcTo(-rSlot,rHeight/2,0); AddPoint(0.0,rHeight/2); ArcTo(rSlot,rHeight/2,0); AddPoint(rSlot,rHeight); Addpoint(ShaftRadius,rHeight); Addpoint(ShaftRadius,0.0); AddPoint(rSlot,0.0); ArcTo(rSlot,rSlot,0); AddPoint(0.0,rSlot); ArcTo(-rSlot,rSlot,0); AddPoint(-rSlot,0.0); EndPoly; ObjHandle:=LNewObj; HMove(ObjHandle,0.0,ThreadLength+RingThickness*2+3.175mm-rETBN); PopAttrs; {End Expansion Collar} {Draw Expansion Stop Ring} Rect(-ShaftRadius,ThreadLength+3.175mm-rETBN,ShaftRadius,ThreadLength+3.175mm-rETBN+RingThickness); {Draw Washer} PushAttrs;FillPat(1); hWasher:=CreateCustomObjectN('Plain Washer (Inch)',0.0,-WasherThickness,0.0,FALSE); SetRField(hWasher,'Plain Washer (Inch)','series','Type B - Narrow'); {SetRField(hWasher,'Plain Washer (Inch)','size',ar3BoltSize);} SetRField(hWasher,'Plain Washer (Inch)','size', Num2Str(3,2*ShaftRadius/DocUPI)); SetRField(hWasher,'Plain Washer (Inch)','view','Front'); SetRField(hWasher,'Plain Washer (Inch)','showCL','FALSE'); PopAttrs; {End Washer} {Draw Nut} PushAttrs;FillPat(1); hNut:=CreateCustomObjectN('Nut (Inch)',0.0,WasherThickness,0.0,FALSE); SetRField(hNut,'Nut (Inch)','typeIndex','Hex Nut - Heavy'); SetRField(hNut,'Nut (Inch)','size',Num2Str(3,2*ShaftRadius/DocUPI)); SetRField(hNut,'Nut (Inch)','view','Front'); SetRField(hNut,'Nut (Inch)','showCL','FALSE'); Hrotate(hNut,0.0,0.0,180d); PopAttrs; {End Nut} {PopAttrs;} END; {Larry Osolin 2013, not for resale and or redistribution without credit and written approval please.} RUN(Wedgie_Anchor);
  2. I posted an issue that I continue to have with rendering 3d objects under the Trouble Shooting section. See Why are these lines rendering? Another user added their "me too" statement to which I responded with additional information. Now suddenly that forum indicates that the issue has been answered, which it has not. Am I expected to repost whenever someone comments instead of supplying an answer in an effort to have it recognized as an outstanding issue??? Larry
  3. There are a couple of other basic functionality issues with rendering that keep me from doing more 3d work in VW. Like OpenGL not rendering section viewports with shadows and grey tones. Not being able to figure out how to define a hatch to appear where an object is in section like cutting through a steel beam results in solid black, again a section viewport.
  4. The smoothing angle should be preventing both of these lines from rendering. They represent the end of the fillet arc between the flange and web on a W shape beam. The beam has pieces cut from and added to it. If changed from dashed hidden line rendering to hidden line rendering the dashed line will be removed. So this is two different functions that are not operating as expected. Both should should be r eacting to the smoothing angle setting.
  5. This may be of some help or not. By grouping a normal viewport you can copy and paste it to another file, but knowing that some attributes will not be carried over. for instance the layers it is linked to are not carried over. The latter I believe is because the viewport does not have the functionality to create any missing layers where as missing classes and their attributes will be created simply through the act of copying the objects into the file beforehand. So that said some functionality of a viewport must be setup/entered into the file for a view port to function correctly which is why I suspect the application is set up to prevent direct copying of viewports from file to file.
  6. @Ardillas Nuh You might get a more informed response by posting your question in its own thread, but I'll give it a try. My question is can we create this parametric object in vectorworks? Yes parametric objects can be created in VWs. Windows and doors already exist as parametric tools and can be placed into walls. These are 3d objects. If you require additional functionality that is not available in the current window or door tool, you can create your own parametric tool. Whether the effort is worth the investment depends upon the frequency your office intends to utilize the custom door or window. The best and most flexible parametric objects are created using code but simple scalable symbols (blocks) are also an option. And while dimensions can be linked to objects and utilized to reshape them, the functionality is not the same as Revit where dimensions are utilized as constraints to create reusable parametric models that are commonly exported as library files. Contact your local VW sales to get a 30 day trial and explore the options.
  7. The grid spacing is easy to determine or set by double clicking the snap to grid icon. This will the bring up the smart cursor options allowing you to read the current spacing and change the grid spacing.
  8. I eventually worked out the angles. I had a transition plate for a handicap ramp to a cross sloping city sidewalk that can't be altered. It required three folds in the metal, I ended up orienting the primary surface to the xy plane and rotating it until the fold line aligned with either the x or y axis after which it is possible to quickly rotate 90 degrees along the opposite axis to view the first axis perpendicular to the screen. Then an angle measure can be taken. then move onto the next plane. Tedious process prone to error if one is not careful in rotating the fold line to align with an axis. Fortunately I only had to acquire those three angles for the manufacturing process. Thanks
  9. Set the grid spacing and turn on snap to grid?
  10. Is there a tool will tell us the angle between two 3D surfaces or work planes?
  11. Better quality printing or publish/printing direct from VW and more control of page layout. Although there have been issues with publish/printing when page sizes are different, possibly specific to particular output devices. Acrobat and web browsers frequently hide or ignore what appear to be system default printer settings and will scale originals to fit pages. The latter can be a blessing for originals that are larger than the sheet sizes available but its a nuisance when it scales down an original that matches the output paper size, especially when it fails to handle portrait to landscape differences. Unexpectedly printing in colour. Printing subsequent pages of multi-page documents based upon first page in set.
  12. A few things you may notice when migrating to VW on the Win10 from MacOS is text input functionality. 1. With caps lock on, holding shift key will drop to lower case for the western alphabet on Win10. 2. Keyboard sequences for entering certain accents, Greek and mathematical characters are now relegated to "Alt" based index calls to the active font table. 3. Win10 has not licensed complete fonts sets like the MacOS. So in Ariel font for instance you cannot call up the checkmark and others. Finding pi can be difficult etc. 4. After changing a class or entering a value into a text field via the info palette control is not transferred back to the main drawing window. This blocks the single character shortcut keys. So you will frequently find yourself having to press escape or clicking on the drawing window before you can initiate another tool or function via the keyboard. 5. Many keyboards developed for Win10 have extra keys between the control and alt keys that get in the way of one handed shortcuts. Those with smaller fingers can experience painful stretching exercises to active certain sequences. I am always hitting the contextual menu button with my left hand's thumb when trying to group or ungroup items. VW may not respond quickly enough to shut down requests from the WinOS resulting in stalled shut downs. My switch over to PC from a similar arrangement MacPro circa 2011 as yours resulted in greatly improved rendering times and screen redraws of 3d and pdf objects. No more having to go get a coffee while waiting for viewports to regenerate. I occasionally get artifacts in the printing process that are not there on screen like a diagonal line across the face of a rectangular steel tubing. We have been purchasing HP Z8 workstations with Xeon processors. This is not to say that these are better than other product configurations though. They were simply recommended by an IT consultant of business systems that we hired who installs and resells HP and Microsoft systems.
  13. There was a time back in the late 90's early 21st century that MiniCad/Vectorworks would respond to the AppleEvent "Do Script" among others. With the development of the Windows version of VW's was/is there a similar means to send and do a script sent from another application? Will this continue in light of the deprecation of Apple Events in newer Macintosh operating systems? I was able to trigger menu items using AutoHotKey on the Windows platform but one had to make all the scripts part of the active VW menu. In both PC & Mac I utilized the function keys to trigger or send scripts that set multiple attributes and introduce office standard classes into imported files. We referred to them as Pen keys because it was like switching drawing pens (when no objects were selected).
  14. I find that VW prevents the operating system from shutting down by not responding to the system request. I also find that closing down VW in general will frequently trigger the application is not responding notice before eventually closing. I'm running this on a new HP Z4 Xeon workstation. I'm also experiencing many more crash to desktop incidents than I ever had on the old (and slower 3d regen) Mac, plus occasional screen flashes to black when regenerating viewports showing 3d objects in OpenGL mode.
  15. Is it normal on the Win10 platform to always be using the escape key to leave the attribute palette and the object info palette before one can use the 'X' shortcut to cancel the active function and return to the pick cursor? This was not the case on my old Mac platform. I am becoming very frustrated after editing the last object I created and then pressing X or another single key shortcut, that when I go to select or create something new I find that the previous function (lines, dimensions, circles, etc.) is still active.
  16. This could be a paired plugin exercise with a placement script in Vectorscript. The plugin on one sheet would know the name of the plugin on the other sheet and vise a versa. The plugin itself could store the name/number of the sheet upon which it resides for the other to extract or the plugin could simply search for the parent of the of the other named plugin and extract the name/number from the parental sheet. When dropping one of these plugins on a sheet via a placement script, the script could automatically drop another plugin on the sister sheet that the user selects at that time. They would need to be event enabled to update whenever printing occurs and have a manual means to trigger the plugin to be executed for other situations.
  17. Yes, but is that a virtual core at 100% and the physical core only running at 50% capacity? I which case is it possible to acquire the whole processing power of a physical core (25% of the CPU) by disabling virtual core pairing to each processor?
  18. Has anyone investigated if it is possible to disable hyper-threading? I have this higher end Xeon processor with 4 cores each split into 2 threads. This results in only 12.5% of the overall CPU processing power being available to do everyday basic hidden line rendering. I was thinking that if hyper-threading could be disabled then maybe a whole core would become available to do work. Getting 25% of our computer expenditure working for us! And then I wouldn't have time to write these posts and speculate on how to get VW2019 operating faster. Smile.
  19. The concept of making changes and not keeping track of all the viewports that are affected is like cooking dinner and leaving the pots and pans for someone else to clean up after you. The technique of drawing, doing annotaion and page layout in the design space is the old school technique that was required prior to the introduction of sheets and viewports into drawing applications. the old school method often had the technician redrawing information multiple times; once for each level of detail required. Building plans often did not jive with room plans which did not jive with envelope details because when ever one was changed the others would not get updated "for efficiency and speed reasons". Moving annotation and dimensioning to the viewport annotation results in fewer instances of unreadable blobs of text that were not intended for 1:100 drawings and cut-off witness lines not intended for the detail views and giant sized grid bubbles, etc. all related to differences in scale between the design space and the layout sheet or viewport's scale. When developing a drawing in the design environment the notes and references I place there are not usually intended for the construction drawings. They are site measures, design constraints, source references (CCNs SIs details, email instructions etc.) These annotations are grouped into their own classes and are rarely turned on in the viewports. Details can be laid out over building plans and sections at their relevant locations and simply grouped or symbolized with a class attached to control their visibility. If you are using viewports and switching things around on the fly you are still going to need to go through all the relevant viewports and realign them, so there really is no excuse for forgetting to realign the annotation and dimensions too when you move the crop. There is no one true way of doing these things but some methods just make it more difficult for the junior drafters to keep your drawings error free after you adjust them. After all that is what office standards are really about. I think that was more like ten cents than two.
  20. 1. If you do any rendering of 3d objects what so ever you will need the machine that has an independent GPU with some dedicated video memory. Even wireframe only files (no walls, slabs, roofs or other 3d objects) benefit from an independent GPU because the responsiveness of the mouse, zooming and snap point selection can be sluggish without one. (Will the installer even proceed to install VW2019 without one?) 2. Launch, load and save times improve noticeably with SSDs and faster processors.
  21. With hatches you can go to the resources palette and without any objects selected in the drawing environment right click to bring up the contextual and select apply. Henceforth that would become the hatch that would first appear when you switch from one of the other setting like solid or none to hatch. For some reason this doesn't seem to work for linetypes. At least not on the PC version of VW2013, but what does work is at the beginning of a project or when setting up an office template you draw your line. Leave it selected and change it to dashed, then change the dash style to the one you wish to be the default. Open the resources palette and delete the linetype that first appeared leaving only the one you intend to be the default. Now you can add any number of additional linetypes including the one just deleted and the intended default will "stick". At least until it is deleted from the file. I believe ISO-02 becomes the default dash type due to alphabetical sorting of the linetypes in the library file that comes with VW and is typically buried in a system folder. That library file is what gives you linetypes to choose from when there are none embedded in you working file.
  22. This is from rusty memory of when I was working with both platforms, over seven years ago. When having trouble with curved shapes, you can start by exporting the objects from a clean file. A clean file has no drawing objects, symbols, hatches, linestyles, etc; it has been purged of everything that the purge command will remove. The only layer should be renamed 0 (that's zero). Set the units to inches or millimeters as applicable and scale at 1:1. Accuracy should be set to at least six decimal places for imperial units. If accuracy is set too low there is the potential for division by zero errors resulting in points that fly off into Autocad outer space. Make sure your polyline has a width other than zero. Copy your object(s) from a working file and paste into clean file. Export to DWG Autocad version 14 or 12. Then check the result by importing back into another clean file. See if your polyline has retained it's curve points or were they converted to other points. There used to be one type of curve that was not supported by Autocad. The translation process would approximate the curve using other types of points, usually hundreds of straight line segments. You might also include a straight line for the rotation axis (or two loci). Autocad supports solids. You should be able to do the sweep yourself and have it export cleanly. You may have to give the final object a solid fill.
  23. I didn't realize that it was even possible to completely collapse all the columns. Thank you Thank you Thank you How it got that way doesn't matter now that I know that it's possible and the technique to return them to normal.
  24. Just a stab in the dark here, but have you tried ReDraw or ReDrawAll? Or applying attributes to the rectangle before ending the floor statement (and then to the parent floor as you do already)?
×
×
  • Create New...