WhoCanDo

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 ?

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?

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.

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.

Thanks Julian, I can work with that 😊

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);

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

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.

Thanks JB, I will give that a go 😊

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;

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.

Sorry, can't help you. But I would like to know the answer too. So lets bump it to the top 😉

Hi Julian, My VW2018 on Windows 7 creates the text file without error. Could it be the Windows version tightening up security?

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.

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. 🎉

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 😉

Hi, I want to create layers that have names like H-1, H-2, etc. Once the layer is created, then I want the layer name to reflect in my title block (I am not using the VW Title Blocks, etc.) However, I don't want the whole layer name since my drawing title already has the prefix job number. I only want the 1, 2, etc. I was thinking a worksheet that had the formula =copy (ActLayer, Pos('-', ActLayer) + 1, Len(ActLayer-Pos('-',ActLayer))) I didn't want to use a macro since the title block is on a layer of it's own at 1:1 and the drawing layers maybe 1:25 or something else to the location of the layer number could change per layer. What thoughts do you have?

VW is changing in leaps and bounds but what about ScriptFunctionReference.html. It's always behind the times and doesn't offer explanations nor examples. Thanks Pat

Nice one Julian, This got me onto the right track. Regards

I thought this was easy but alas it's not. I want to x := Count ((Sel = True)); Message (x); However, if I have a group of 3 objects and only this group object selected then x := 4 Some of my selected objects will be polygons, rectangles & groups of them.

Hi Mike, nice to hear from you I like that idea. I may be able to use that elsewhere. However, a little off topic. All I am trying to say is that the change of pick priority regarding hierarchy is wrong. We liked VW2016 version which, as far as I remember, goes back 23 years to the day I first used MiniCad. I am trying to pick three objects using Alt-marquee and Shift-pick. The task is to pick two lines and a rectangle. The two lines are on two sides of a rectangle. The two lines are on a layer above the rectangle. I can't pick them all with a marquee because of other objects within the area. I would like to Alt-marquee over one line and the rectangle edge, then Shift-pick the other line. When I pick the second line, it results in deselecting the rectangle. This was capable in VW2016 because the line is on a higher hierarchy level and also possible when the line was on the same layer but at a higher hierarchy than the rectangle (the line was drawn second or bought forward at some time). If the line and rectangle are on the same layer then I will have to work with it because someone in the above posts says it's an innovation, but not for different layers

I just tried the "J" command again. If I have two rectangles on top of each other and select them both, then J-pick lists two rectangles. Correct but useless to know which one is which. If I have one rectangle and two lines on top of the rectangle (as in previous example) and select them all, J-pick lists one rectangle and one line. Does "J" really work like it should?

Hi Tom, our classes are allocated at the end of the process as a "Mark" number. Hi Alan, "J" allows me to select one on the list but I want the bottom line + the rectangle + the top line. As stated, other objects in the area doesn't allow for selecting all. Going back to VW2016, I could Alt-marquee the bottom line and rectangle, then I could shift-pick the top line. Now, I can Alt-marquee the bottom line and rectangle but when I shift-pick the top line, I deselect the rectangle. This shouldn't happen because the rectangle is on a layer below the line. I can understand the argument for this happening on the same layer (even though I hate it) but what's the point of having shift-select if it doesn't add to my selection. The old system had more rights than wrongs but the new system has more wrongs than rights. At the least, resurrect the hierarchy.

It's been a while trying to get a hand of this regression and it still doesn't work. If I have a drawing with two layers. I draw a rectangle on the bottom layer. I then draw a line, matching the top edge of the rectangle, on the top layer. Repeat this for the bottom edge of the rectangle. Very simply, this is what we are drawing in our process. Keeping in mind that there are other objects within the rectangles area so a rectangular marquee selection won't work without picking them too, how do you pick all three? Well it use to be as simple as alt and select overlap on the bottom edge picking up the line and rectangle, then shift select the top line. Now, using the above process, when I select the top line, the rectangle is deselected. 😒 I can understand the reason for this change on a single layer but surely the hierarchy should be a priority so I can choose something on the layer above without deselecting something below. Also, the new design doesn't always work. I am often drawing the line (as above) and then ctrl picking up the line to duplicate it to the bottom. Sometimes, however, I will draw the line and then ctrl pick it up, only to find that it picked up the rectangle instead of the line. Not happy so far.

Thanks Guys, so I was on the right track with .. GroupPanelCount := Count (Concat ('''Group-A''', '.', '''Mark''', '=''', Mark, '''')); except that I was over nesting it for VW. This works .. crit := Concat ('''Group-A''', '.', '''Mark''', '=''', Mark, ''''); GroupPanelCount := Count (crit); What was confusing me was that Message managed to handle (Concat ('''Group-A''', '.', '''Mark''', '=''', Mark, '''')); but Count couldn't. Regards to all.