Jump to content

Pat Stanford

Moderator
  • Posts

    12,626
  • Joined

  • Last visited

Everything posted by Pat Stanford

  1. If you right click on the a database subrow (3.1, 3.2, etc) you get an option to Select Object that will show you the object selected in that row in the drawing. Sort of like Force Select. I don't think it works for subrows that contain SUMmarized multiple objects.
  2. Any particular reason you are not running 2020SP5 which is the latest?
  3. Do you have Adjust Flipped Text checked in the Document Preference?
  4. It looks like the object is rotated in all three axis. I would probably start in a Top view and use the Rotate tool to make it square with the axis. Then switch to a side view and use the Rotate tool to make it parallel to the layer plane. Then move it up or down to meet the plane you want. Could you use a Viewport instead of physically moving the object? Either model the object flat and then use a Design Layer Viewport to move it where you need it in the overall model or model it in place and create a viewport to get the plan layout?
  5. From the Window menu you can Undock Current Document to have a separate window you can put beside or on a different screen. Drag the title bar of the window back to the tab bar of VW to redock.
  6. I know this feature exists in VW2020 and VW2021. I think it was in VW2019 also, but am not positive. Look in help for Multiple View Panes. You can set up as many panes as you can stand and each can be in a different view or rendering mode. Once you have multiple panes you can right click on the pane label and Create Floating View Pane that you can put next to your drawing or on a different monitor.
  7. I think it is Hashlib that is adding the space, not the SetVSVar. Try printing myhash from Python and see what you get.
  8. 1. If you apply the record to the Symbol Definition in the Resource Manager before you insert the symbol, the inserted symbol will get the record and data from the symbol definition. But after that the link on the record is broken. If you change the data attached to the symbol definition, the data attached to the symbol instances will not change. Custom Modification (and/or worksheets) is your friend if you need to change the data associated with multiple instances of a symbol. If you attach a record to a symbol definition after there are already symbols in the drawing, the already inserted symbol instances will not be assigned the record as you have noticed. The underlying reason for all of the above is so that data associated with already inserted symbols is not overwritten by changes to the symbol definition. If you had table numbers manually inserted into the record for inserted symbols, you would not want them all to change when you change the default attached to the symbol definition. There have been many requests over the years for a field type in records that would be consistent across all instances of the record, but that functionality does not exist yet. 2. You are probably better off using a single record format, but attaching it to the symbol definitions before you insert the symbols rather than after. That way you can edit the data attached to each symbol definition and have that data transferred to the symbol instance. Ask again if you need more help.
  9. The curtain wall is a replacement for a regular wall. Just leave a gap in the regular walls and use the Curtain Wall mode and it will all join up.
  10. I think the extra space is being added on the GetVSVar and then being propagated through the rest of the functions. Can you come up with a version that does not use GetVSVar that shows SetVSVar including an extra space?
  11. I am not seeing a problem with SetVSVar here. What do you get when you run the following script? PROCEDURE Example; VAR strName : String; BEGIN strName := ''; PythonBeginContext; PythonExecute( 'import vs' ); PythonExecute( 'vs.SetVSVar("strName", "python")' ); PythonEndContext; AlrtDialog( Concat( 'VectorScript received: *', strName, '*' ) ); END; RUN(Example);
  12. There have been many scripts posted over the years. Until fairly recently I usually posted them in the Archive:Resource Share:Vectorscript forum. More recently I usually put them into the Customization:Vectorscript forum. Maybe the best advice I can offer is to do a Google search using a site:forum.vectorworks.net tag as part of the search criteria. Try some different key words of things you might be interested in. I currently have over 200 files on my computer with some sort of script in them. I don't remember what they all do.
  13. Two suggestions. 1. Try again, but set the view to Front before you import. 2. Group the objects, go to a side view, Rotate the object 90/270 degrees as required to get the UP pointing up. And an extra one for ducks. 3. Always import into a new blank file so something like this does not corrupt a lot of work in an existing drawing and then reference or copy/paste into the file you need the data in. HTH
  14. Here is the basic algorithm. It needs some work to simplify the fractional part (0.5 shows as 4/8 instead of 1/2), and to round up to the next whole number if the fraction is equal to 1. Procedure Test; Const Base=8; Var Original, DecPart: Real; IntPart, FracPart: LONGINT; RetValue: String; Begin Original:=RealDialog('Enter Decimal Number', '0.0'); IntPart:=TRUNC(Original); DecPart:=Original-IntPart; FracPart:= Round(DecPart * Base); RetValue:=Concat(IntPart, ' ',FracPart, '/',Base,'"'); Message(Date(2,2),' ', RetValue); End; Run(Test);
  15. Unfortunately, I can't point to any video sources. I think @michaelk did a webinar a while ago. It might be up on Vectorworks University. @Jonathan Pickup almost certain has some on his (paid) site also. I am much more of a text guy than a video guy. Sorry.
  16. Are you saying there is a bug in SetVSVar as well as the one I already submitted on the GetVSVar?
  17. The Message command "stopped working" a few versions ago in that it does not operate during a Vectorscript, but only at the end of the script. At least that is my memory. You can either use AlrtDialog, and require the user to hit enter to proceed. (this is my go to for debugging) Or you can try AlertInform and set it to be a minor alert. The problem with that is the second time you call AlertInform it ignores the Minor and pops up a dialog box instead of just putting the information into the message bar. If you really feel you need a progress indicator you might be better off in Python and use Python objects instead of VW objects. +1 to @JBenghiat ;-)
  18. All walls have to have some "affiliation" They can either be Story Bounded or Fixed Height. Fixed Height Walls insert at the level of the Layer they are on. If you don't care a lot about the specifics, use Fixed Height walls and convert them to Unstyled so you can move them as you see fit.
  19. Yep, we had than discussion at the September LA VWUsers Group meeting. in the default workspaces the toggles are Command-I for OIP, and Command-Shft-N for the Nav Palette. Turn one off and the other goes to full height. Turn both off and you get a few extra inches of drawing space. I think it was @Sam Jones who taught us this.
  20. What do you mean? That you want the roof to cover a different area than the walls? Then just draw a polygon of the roof outline and use that rather than the walls to generate the roof.
  21. Interesting. We just talked about this yesterday at the Los Angeles users group. The Number of Duplicates is the 4th mode group. So hit Shft-M for the Move by points tool, then hit P for the 4th mode group and enter your number. Not quite as easy as Shft-MM, but your muscle memory will catch on quickly. ;-)
  22. The old drawing label is still available to be added to your workspace. In the workspace Editor look in the Legacy section of the tools and add it to your workspace. Just because you were not complaining about the old version does not mean that no one else what. There has been a long and persistent request for the back referencing option that was added to the new drawing label.
  23. It has been a really long time since I messed with dot matrix printers. ;-) Compression in the Y direction is probably an issue with the printer driver rather than VW. For the long length, I would recommend creating a custom paper size of 8.5' wide x however long the LX350 will handle (or you need) and use the One Printer Page page setup option. Paper sizes are normally settable in Printer Setup from the Page Setup dialog box.
  24. It is a reasonable request. If you really want it to do that then you should post in the Wish List forum. I was just trying to give you some options since you preference is not currently available.
×
×
  • Create New...