Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by WhoCanDo

  1. I think this will work 😃 Interestingly, JB mentioned the LT option but it's not in the Appendix "Attribute Criteria" and therefore I thought it was a typo when his eg. used PP again. Sorry.
  2. Hi Pat, When you get back, try this with a line that has Line Type "Circles" or anything but "Solid" or "Pattern". It won't work. procedure test; var Line_Index : longint; Procedure Do_This (h : handle); Begin SelectObj ((PP = Line_Index)); Message (GetLSN (h), ' ', Line_Index); End; begin ClrMessage; Line_Index := GetLSN (FSActLayer); Message (Line_Index); Wait (2); DSelectAll; ForEachObject (Do_This, ((T = Line) & (PP = Line_Index))); end; run (test);
  3. Thanks JB, This partly works. For SelectObj it works, but for ForEachObject it doesn't. I have had to use ForEachObject without PP and then check each "h" with "if (GetLSN (h) <> Line_Index) then" before running the code. I still think there is a bug with ForEachObject (Do_This, ((T = Line) & (PP = Line_Index))); not recognising the PP
  4. Hi, Can anyone explain why this is not working please? I want to use PP= with ForEachObject, but the test below indicates that (PP = Line_Style) doesn't work when the Line_Style is changed to a "Line Type" (Dotted, etc.) procedure test; var Line_Index : longint; begin ClrMessage; Line_Index := GetLSN (FSActLayer); Message (Line_Index); Wait (2); DSelectAll; SelectObj ((PP = Line_Index)); Message (GetLSN (FSActLayer), ' ', Line_Index); { ForEachObject (Do_This, ((T = Line) & (PP = Line_Index))); } end; run (test);
  5. Thanks, forgot about FSActLayer 😃
  6. Sorry, also the rectangle is a symbol with the name "A3 Border" Ok, just tested this. I need to use GetSymName, not GetName Thanks
  7. Just to be clear 😊, the rectangle has the class "Border" and name "A3 Border". I want GetName to tell me it's name is "A3 Border".
  8. Are you using the "DXF/DWG or DWF Import" or are you importing them directly into VW? We always convert the files using the above bulk converter rather than importing them directly.
  9. Hi, I have a rectangle on a layer with Class "Border" and Name "A3 Border" Can someone tell me why the following message does not return the name "A3 Border" please? procedure test; begin Layer ('Title Block'); DSelectAll; SelectObj ((L = 'Title Block') & (C = 'Border')); Message (GetName (FSObject (ActLayer))); end; run (test);
  10. When looking around the web regarding graphics cards for CAD, the recommendation is a Quadro. However, they then continue to refer to AutoCad, etc. If GTX is best for VW, I presume it's also OK for using the other CAD Viewers or Software for multi-tasking. I am guessing from all that I have read, that we should pick the GPU to suit our primary CAD software and secondary CAD software should work, but maybe at a slightly degraded performance. So, if we use VW 90% of the day, and AutoCad 10% then we pick a GTX, but if it were the other way around then we pick a Quadro. What's the opinion on this ?
  11. I am using VW with a black background to reduce eye strain. When I use VW to import a PDF vector drawing, the PDF has black lines and therefore, on the black background, I cannot see it. Is this an oversite/bug or can I change this somehow?
  12. If the PDF is vector, then you should be able to "File / Import PDF" from VW itself (I don't think Fundamentals does it). You can easily scale this down as you wish. However you will have to draw over the PDF objects if you want polygons to use in VW.
  13. It's not so much how many I open when working, but how many I need to open to print the fabrications drawings (could be 50). It's not reasonable to print as I go since they get lost in the communal printing pile. I like to print them in alpha-numeric order in one pile so the job doesn't separated and get lost. If VW doesn't allow more than 8, maybe a printing macro is what is needed.
  14. Thanks Julian, I can work with that 😊
  15. Thanks Julian, but that didn't work either ☹️ procedure test; var Response : boolean; begin Response := DeleteAllComponents (nil); Response := InsertNewComponentN (nil, 1, 5, 0, 10, 6, 0, 2); Response := InsertNewComponentN (nil, 2, 20, 0, 6, 10, Name2Index('Dash Style-2'), 0); SetTool (13); end; Run (test);
  16. Hi, I want to create a wall type with a dotted line cavity. In VW2018 this worked .. procedure test; var Response : boolean; begin Response := DeleteAllComponents (nil); Response := InsertNewComponentN (nil, 1, 5, 0, 10, 6, 0, 2); Response := InsertNewComponentN (nil, 2, 20, 0, 6, 10, -2, 0); SetTool (13); end; Run (test); However in VW2019, it doesn't. It seems that the -2 is the cause of the problem. -2 is the line type "Dash Style-2" from the standard pallet. If -2 is changed to 2 in this script, the wall looks like above with a solid cavity line. Can anyone suggest what changed between VW2018 & VW2019? Please note: that I was using InsertNewComponent in VW2018 but now I am forced to use InsertNewComponentN
  17. Finally. Fixed. Couldn't use ForEachObjectAt because a point is not and object for LOC, so I ended up finding all RoundWalls, calculating the center (of the wall not the CL), adding another 2mm straight wall at that location, so that LOC worked. Unfortunately, SetName did not work because LNewObj & LActLayer failed as usual, so I ended up finding all 2mm walls at the end and deleting them. A lot of fussing around when LOC says "Location is contained within boundary of a named object". Thanks all.
  18. Hi, Can anyone tell me how I can get this to work please? If T=Wall it works, but not if T=RoundWall. This is because the center point of the RoundWall is not within LOC. Procedure Check_for_Wall (hKP : handle); begin AlertDialog ('Here'); end; Procedure Check_Adjust (h : handle); begin SetName (h, 'Tmp'); ForEachObject (Check_for_Wall, ((Loc = 'Tmp') & ((T = Wall) or (T = RoundWall)))); DelName ('Tmp'); end; Begin Get the handle from bounding polygon and pass to Check_Adjust end;
  19. A bit late but why don't you create a folder in the root directory to access. This should be the same path for every PC/user.
  20. Sorry, can't help you. But I would like to know the answer too. So lets bump it to the top 😉
  21. Hi Julian, My VW2018 on Windows 7 creates the text file without error. Could it be the Windows version tightening up security?
  22. Nice to hear from you Hippocode, On my Tuesday post I requested ideas that did not include scripting. The reason being that thousands of VW users out there don't know how to script. Even so, if I were to write a script, I think the variables would be too great since sometimes I want to select an object with a record to change a field, but not all objects with that record (Digressed slightly). So, if I wanted to remove the records from half of my example, I would have the monotonous task of selecting some from many and then Kevin's idea will work, however annoying VW makes it.
  23. Thanks Kevin, No.2 sounds the go. I'll use that while everyone is waiting for the attached records to be put back into the OIP for quick and easy deletion. 🎉
  24. This is still hindering our drawing process enormously. Maybe I should approach this with some questions. If I have 230 objects on my layer (some lines, some walls, some polygons, etc., each with a different record attached, and half with the same record attached, how do I delete all the record attachments except for the common one? No scripting answers please 😉
  • Create New...