Pat Stanford

I don't think so. I believe there is only one text size for all aspects of a single dimension object. You could make the note a separate text object with a different text size and then GROUP the dim and text together so they stay together if moved. You would have to edit the group if you need to make a change to the dimension.

Pulleys come in stock sizes, Belts come in standard lengths. In a 3 pulley setup as shown, at least one of the pulleys has to be adjustable so that you can loosen it to remove an old belt and put on a new belt. 2D version of Shrink Wrap would be the Lasso mode of the polygon tool. It will have to be redone when you change the pulley locations. Set the Tangent snap on and draw lines between your three pulleys. Select the Lasso mode of the Polygon tool and draw a "fence" completely around the three pulleys. You will get a new polygon created that is the interior portion of the pulleys and the lines. You can extract the perimeter from the OIP. I tried to use the Tangent constraints, put they don't seem to work properly when I move the pulleys. You could write a script that would do this. My rough estimate is that it would take me about 4 hours to write and debug this. 1. I don't have 4 extra hours in my life right now. 2. It would take someone without lots of scripting experience 2-10 times longer to write the script. 3. How many times are you really going to have to move the pulleys and how much time are you really going to save by having a "faster" way to do this?

Loc does not take a criteria, but rather the name of an object. I think it has to be the name that shows at the bottom of the OIP. I don't know if the SpaceName will work or not. Loc('OIP_Name_of_My_Space') should get you what you are looking for.

Three code changes to get it to compile and execute. SetLineStyleChoice -> SetLineTypeChoice GetLineStyleChoice -> GetLineTypeChoice SetWSCellOutlineBorder -> SetWSCellOutlineBN And one bad bug that prevents it from running. It appears that the GetWSSelection command is returning bad values for the subrows. The following very simple script gives the same runtime error as yours. Procedure Test; Var WSHand:Handle; currentCellRow,currentCellColumn,topRangeRow,leftRangeColumn,topRangeSubrow,bottomRangeRow,rightRangeColumn,bottomRangeSubrow:Integer; Begin WSHand:=GetTopVisibleWS; GetWSSelection(WSHand,currentCellRow,currentCellColumn,topRangeRow,leftRangeColumn,topRangeSubrow,bottomRangeRow,rightRangeColumn,bottomRangeSubrow); Message(currentCellRow,' ',currentCellColumn); End; Run(Test); Procedure Test; Var WSHand:Handle; currentCellRow,currentCellColumn,topRangeRow,leftRangeColumn,topRangeSubrow,bottomRangeRow,rightRangeColumn,bottomRangeSubrow:Integer; Begin WSHand:=GetTopVisibleWS; GetWSSelection(WSHand,currentCellRow,currentCellColumn,topRangeRow,leftRangeColumn,topRangeSubrow,bottomRangeRow,rightRangeColumn,bottomRangeSubrow); Message(currentCellRow,' ',currentCellColumn); End; Run(Test); Until VW fixes the bug in GetWSSelection, you are out of luck on this script. Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it? Brian Kernaghan"The Elements of Programming Style", 2nd edition, chapter 2.

Can you post a simple file with a couple of spaces and a few different symbols in each space. I will see if I can make it work so you can see exactly what is required in your file.

You got the best/only current way to do this. You might want to enter a wish list request for this feature. The more they see the request the more likely it is to happen.

I think the Sum Values is just how it works. If you check Sum Values for a column it will use the SUMmed values when doing calculations if you don't check Sum Value it will use just the single value for that cell. Since you have to use Sum Values for everything and you are trying to use a single value minus a summed value, I think you will have to get creative. If you post a simple file with some objects I will try it here, but I think the following will work. But it will only work if the available quantity is the same for every instance of the symbol. =Record.Available/Count-Count with Sum Values checked I THINK will get you what you want. Or not. I thought I got it to work once, but not can't replicate. The issue appears to be that you want to use something that is SumValues and something that is not SumValues in the same cell. Should be possible, but I have not cracked it yet.

Answered in the other thread. For those to lazy 😉 to check it out, the field is formatted as text instead as a number. Hard to do math on text.

'Lighting Device'.'Clamps' is formatted as a text field instead of a number field. Either change the field type to a number format or use a formula in column A of =Value('Lighting Device'.'Clamps') so you have numbers that can be summed.

Are your "2D" objects screen plane? The naming convention has not caught up with the progress yet. The 2D portion of a symbol is actually the Screen Plane portion of the symbol The 3D portion of a symbol contains everything else, including Layer Plane and Working Plane Objects. Or maybe I am talking through my hat. I know it used to be this way. I have not hat time to play with the new multi view hybrid objects in VW2019.

Set your drawing window to the aspect ration you need for the manual, Zoom In, and then Export PDF - Current View Only?

I was near the computer, but I have been on 7 conference calls and a lunch meeting today. Hard to script with all that background rigmarole going on 😉 Michaels explanation of the code block being in the forum was exactly what I meant.

I always try to past scripts into a "code" block (click on the <> icon above the edit window). That will ensure that everything is truly text and not some extended unicode text like object. It also keeps tab formatting correct rather than compressing everything to the left margin. My question would be what browser you are each using and what operating system. I know Michael is on Mac and it looks like Boh is on Windows. My guess is that whatever browser Boh is using is sticking some invisible characters into the text when copied that are then confusing the VS compiler.

Probably has to be a wish list item, but there might be some possible work arounds. 1. There is currently no way (that I know of) to have a record or field permanently linked to the symbol definition. As soon as you insert a symbol instance, it gets its own copy of the record and if forever after independent. 2. Potentially the easiest solution would be a script that when run would read all the data from the record attached to the symbol definition and write that to every symbol instance. Down side is that you have to remember to run the script. 3. If you don't need to be able to see the data in the OIP, another possibility would be to create a hidden record format and attach that. You could then edit the data with a worksheet or a script. Also, you would still need the script from Option 2 as changes would not propagate to each instance. 4. It might be possible to create a PIO that could act as a "container" around a symbol and have effectively the script Option 2 included in the PIO code so that when the PIO regenerates it "grabs" the current data from the symbol definition. But you still have to remember to regenerate the PIO. 5. It might be possible to create a "master" layer that would hold a single instance of each Symbol/Record/Field. Potentially a link to the correct "master" could be stored in a record attached to the instance. With the correct (probably a worksheet script) functions, it might be possible to extract the data from the "master" rather than the instance. I understand and can see the benefit of what you are asking. Can you better explain your exact use case/need right now so we can possible offer a better solution?

It sounds like you have the 4th mode "Active Layer Plane Origin Mode". This will use the origin as the rotation point. You probably want the first mode "View Center Mode", or the second mode "Interactive Origin Mode". The View Center will rotate around the current view. The Interactive Origin Mode will let you click to specify the point to rotate around.