Pat Stanford

  • Content count

  • Joined

  • Last visited

Community Reputation

174 Spectacular


About Pat Stanford

  • Rank
    Vectorworks Addict

Personal Information

  • Homepage
  • Location
    El Segundo, CA, USA

Recent Profile Visitors

939 profile views
  1. There is nothing in the scripting (not SDK) documentation that talks about alpha channels. How would you do what you are asking for manually in VW? If you can tell us that perhaps we can figure out how to script it.
  2. Certainly sounds do able. The biggest problem will be with finding enough time to do it right. I am pretty much a hack. I program quick and dirty to accomplish specific tasks. I would think that for Marionette nodes you would want to do much more error checking to prevent bad inputs/outputs than I normally do. I think the best option for creating new nodes is to not do it. Instead find the node that is closest to what you want (either in terms of function or number/type of IO) and use that as the base and just change the code inside that needs to be changed. @DomCmight be a better person to work with on Nodes. I know he has already done some. What are you thinking of as a first test?
  3. There are only two true Functions for getting info on Spaces. These can be accessed from the Insert:Function menu item. For spaces these are GetSpaceNameForObj and GetSpaceNumberForObj. There are many more options for Spaces (and most other Plugin Objects [PIOs]) based on the Record.Field data. For the ceiling height try ='Space'.'11_Net Height' Be careful with the quotes since the filed name has a space in it they are required. To get a list of all of the fields of a PIO, place a single instance in a drawing and run the script at the bottom of the following thread. It will create a worksheet showing all of the possible fields for that type of PIO. Remember that the internal names do not always match what is displayed in the PIO or the Setting Dialog box. Also, especially for spaces, there are sometimes similar fields but one is a text field and the other a numeric value. If you want to do calculations you have to use the numeric field.
  4. If this is important and worth money, check out TouchCad.
  5. If this is just a periodic need, edit your workspace to include the Custom Visibility menu command. It is probably hiding in the Legacy Items category. This menu command will let you turn individual items invisible. Or just create two simple single line scripts. Hide(Sel=TRUE); and Show(All); Select an item and run the first script and it will be invisible. Run the second script an anything you had turned invisible will again be visible. Let me know if you need more help.
  6. Restart VW? Restart Computer? Check the permissions on the Preferences file. If you can't save the change perhaps it won't take.
  7. There is no way I know of to take a manually produced object and add parameters to it. You would need to create all of the objects in the Marionette object to be able to assign them popups or allow data to be entered from the Object Info Palette (OIP)
  8. Have you restarted the computer? Updated the video driver? Reinstalled VW? Those in that order would be my next recommendations. What operating system are you running? Do you have the latest service pack for 2016? I believe SP6 was released in December of 2016.
  9. You need to make a Plugin Object to have that kind of control. The simplest way to make a plugin is to use Marionette, the graphical scripting language. Check the Marionette and Resource Share - Marionette forums for some basic information and a starting place. Ask again if you have more questions.
  10. What happens if you use Fast Renderworks or Custom Renderworks?
  11. What happens if you unplug the keyboard but leave the mouse plugged in. Is there anything strange happening in any of your other programs? Have you restarted the computer?
  12. Yeah. I get the same thing. It has to be a regular viewport in an elevation view. I guess I knew that at one time. :-(
  13. You can create a section viewport from a section viewport. It is a standard method draw a section line outside of a building to generate an elevation. If you then create another section viewport horizontally across the elevation, you can get a "plan" view with a user settable cut height.
  14. It might help to go back to the pre-history of viewports and Sheet Layers. Before Sheet Layers were released, the name used for them was Presentation Layers (this snuck through is some of the documentation). If you think about Sheet Layer as being for the presentation of information, then by default, the opposite would be for the creation of information. i.e. modeling. Two great things about Design Layer Viewports. 1. They can reference information from another file, so if you are doing a project with multiple buildings you can put each in a separate file and then reference them in to the site plan to generate sections and elevations. 2. They can work kind of like "Super Symbols" that can be placed multiple times, but will also allow data to be on multiple layers. A symbol can only have objects on a single layer but many classes. Before the inclusion of viewports, all work had to be done on Layers (now called Design Layers). You could use Layer Links to give multiple views of an object, but since Design Layers "Render to Infinitiy" only one could be rendered at a time (and had to be at the bottom of the stacking order) as the render would hide anything below it in the stacking order. The places I hear about most in the use of design layer viewports are in multi-family residential where you will have the same unit type repeated multiple times. The other use is in Spotlight where you can use Design Layer Viewports to take a vertical set of lights and lay they out horizontally to be able to label them, but still have them show properly in the model. Hopefully someone who uses them more than I do will step in with their opinion.
  15. If it is the Data Stamp tool, look in the Legacy folder.