Jump to content

C. Andrew Dunning

Member
  • Posts

    1,153
  • Joined

Posts posted by C. Andrew Dunning

  1. 24 minutes ago, Julian Carr said:

    Try GetLineWeightChoice() Andy. At least that's what I use.

     

    Thanks, Julian.

     

    What gets returned if "Class Thickness" is chosen (if that is even an option...w. CreateMarkerPopup the equivalent isn't in the list...at least, in the VS version)?

     

  2. Good morning!

     

    Might any of you be able to lend insight into getting data out of a pop-up created using "CreateLineWeightPopup?"  I did find "GetLineWeightChoice" but I'm not sure if that applies as "Class Thickness" is one of the options and that call simply retrieves the line weight in mils.

     

    Thanks!

  3. 2 minutes ago, scottmoore said:

    you are now discussing the functionality of this potential product, one on one, with the actual developer. It doesn’t get much better than that in the software development world. 

     

    !!!!!!!!!!!!!!

    • Like 1
  4. Interesting to see the direction this thread headed...

     

    A few comments regarding the "3rd-Party" part of the conversation:

    1)  I well understand Lec's concern about an apprarent need (to him) that is not being met by the stock VW packages.  I've been there so many times that I've lost count.

    2)  Sam is quite right about the breadth of disciplines VW covers.  VW leadership has to make daily decisions about where to apply resources and about which features (or, approaches to implenenting features) fit or don't fit defined conventions.  Along w. that, it CAN be quite frsutrating to see another industry getting love when one's own is seemingly getting ignored.  The evidence is that, using Spotlight as an example, users from that area aren't really "poorer stepchildren" when one considers all of the specific effort that has been applied, there, recently.  The catch is that, within the microcosm of Spotlight, the decisions I just mentioned have to be taken...

    3)  Echoing Sam, this is where the beauty of having 3 different options for developing proprietary or 3rd-Party solutions lies:
    · Very focused or customised commands and tools can be created.
    · Potential needs can be explored in a way that could be difficult under the corporate umbrella.
    · Likewise, other approaches/conventions can be explored in a way that could be challenging under the corporate umbrella.
    · Intimate interraction with developers is more possible for more users.
    · Many developers are creating solutions that they need in their own day-to-day "other" jobs - using approaches and conventions that "think" like they do...that fill sometimes difficult-to-articulate needs...approaches and needs that can be incredibly hard to understand if one is not really immersed in a given discipline.
    · Faster turn-around on enhancements and fixes is often possible.
    · Commands and tools are seldom tied to a specific VW package.

    4)  While this might sound self-serving for me to say, I'm with Sam in being quite surprised at the hesitation of a lot of users to take advantage of 3rd-Party commands and tools - some at little to no cost.  Yes, there is risk involved.  Is there any actual support?  Will the command or tool be available in a month?  Does the command or tool follow official conventions?  I've found so much value in 3rd-Party offerings that those risks are more than acceptable.  And, the more I invest in other developers, the more incentive they have to continue their work...

    • Like 1
  5. Steve -

     

    That error message means the tool is being asked to place a projector in a way that is impossible - such as a vertical offset that is more than 90°.  Try a smaller vertical shift amount or a different lens spec. and see if the issue gets corrected.

     

  6. We are happy to announce Vectorworks 2020® versions of our tools have been released!  In addition to getting things ready for Vectorworks 2020®, we've been working on the usual "under-the-hood" refinement and on adding some features several users have been requesting.  As evidenced by the Audio ToolSet tools' "Symbol" functionality released earlier this year, we really do listen to your requests!

     

    The most apparent improvements you'll see have to do with text display in the VideoScreen 4 tools.  You'll see things like the ability to generate 3D text blocks (discussed in one of the Facebook VW groups recently)...customize item labels...and, to display additional textual information.

     

    If you're one of our users and purchased one of the VideoScreen 4 licenses or a Producer's Pack 3 license since February 11, 2018, these updates are available to you free-of-charge.  If your license is older than that, we believe that you'll find our upgrade offers to continue to be quite generous.  If you hold a license to one of the other tools, your current link and password will allow you to download a version for Vectorworks 2020®.

     

    If you're not one of our users, yet, and would like more info, visit one of the links in my sig for more details, to download manuals, or to check out the upgrade offers.

     

    Happy Vectorworking!

    • Like 2
    • Love 1
  7. 3 hours ago, Chris_W said:

    While using this file with the screen tool, it seems the widest lens option available is .64, don't these lens' go down to .3? Do I need to just put it in as a custom value?

     

    For the current build of the Spotlight tools, yes, this is your best option.

     

    • Like 1
  8. 3 hours ago, markdd said:

    There's a fault with my projector data. You need to add "mm" to the measurements in the data records for these to work in imperial files.

     

    The same thing is true if your units are in Imperial and you want your projector(s) to work in Metric files.  Units markers need to be included.

     

    1 note:  Don't change the field formats in the Record from Text to Dimension.  They need to remain Text fields with units markers manually added.

     

    3 hours ago, markdd said:

    Also, I think Vectorworks have changed the necessity to look in library files for the symbols. As far as I can see, the tool now looks for any symbol in the file or library files with the correct record attached (__VS-ModData)

     

    The tools look in both places.  I simply suggested the external folder assuming the Symbols would be needed in files beyond the current model.

    • Like 1
  9. 24 minutes ago, Chris_W said:

    Are you able to put them in the screen tool or do you just drop them in as objects? What about adjusting for different screen sizes?

     

    If you're running Spotlight or are using the Landru Design version of the video tools, all you have to do is to add that file to the "...Libraries\Defaults\Video Screen\Projector Models" folder.  Then, when you use one of the projection tools, those projector models will be available to you.  The tools will handle screen sizing and projector placement for you.

     

    • Like 1
  10. Have you tried any of the Sharkstooth Textures that are included in the Landru Design version of the tool?  They are based on scans of Rosebrand Sharkstooth Scrim instead of code-generated Textures.

     

    See the link(s) in my sig...

    • Like 1
  11. On 12/15/2017 at 9:41 AM, Pat Stanford said:

    In 2018 this is handled in the database header row cell pull down menus. Select Summarize for the correct column. Then select Sum Values for the columns you want totaled.

     

    I've got a Worksheet listing instances of a given PIO, summarized by a selected field.  What is the syntax for displaying the count for each summary?

  12. 13 hours ago, michaelk said:

    This is mostly useless, but at least one person in the world asked for it and @C. Andrew Dunning is apparently barely making his flights on time.  🙂

     

    That streak that just passed you was me...trying to make that flight...  ;-)

     

    13 hours ago, michaelk said:

    This is mostly useless, but at least one person in the world asked for it and @C. Andrew Dunning is apparently barely making his flights on time.  🙂Attached is a plug-in that builds theater flats.  It's not super great.  It only does...

     

    It doesn't pass the @C. Andrew Dunning ROI test and probably never will, so it may never get better.  I mostly did it to learn how to turn scripts into tools.

    Post back here if you find any bugs or have any suggestions.

     

    1)  A big hat's off to you for jumping into the coding pool.  A lot of users have good ideas but never do what you have done.  Kudos for giving things a go.

     

    2)  Whether it ever makes you any $ or not, you now have a tool that a) meets a need you had and b) that you can tweak as your needs evolve.  I've got many that will never see the commercial light of day...that are "raw" at-best...but that are an integral part of my workflow.

     

    3)  Now that you've dipped your toes, be prepared to be frustrated when you find things in other developers' tools that you feel the impulse to "adjust" and can't...  ;-)

     

    13 hours ago, michaelk said:

    This is mostly useless, but at least one person in the world asked for it and @C. Andrew Dunning is apparently barely making his flights on time.  🙂Luckily I had a long enough flight to write the script and @Pat Stanford was kind enough to walk me through turning it into a tool late at night after rehearsal.  And then the rest of the scripting community set me straight on a bunch of other issues.

    Luckily I had a long enough flight to write the script and @Pat Stanford was kind enough to walk me through turning it into a tool late at night after rehearsal.  And then the rest of the scripting community set me straight on a bunch of other issues.

    Post back here if you find any bugs or have any suggestions.

    Post back here if you find any bugs or have any suggestions.

     

    For anyone reading this who is tempted to jump into creating Tools or Commands, you'll find the Scripting community to be incredibly gracious and generous with help...tips...hints...etc.  The list of people who have helped me over the years is longer than I could ever remember.

     

    13 hours ago, michaelk said:

    This is mostly useless, but at least one person in the world asked for it and @C. Andrew Dunning is apparently barely making his flights on time.  🙂Post back here if you find any bugs or have any suggestions.

    Post back here if you find any bugs or have any suggestions.

     

    If you're running VW in Developer Mode (VW Preferences dialog...), you'll get an "Integer" error on line 16.  The code is looking for a value that should be an Integer but it is being given a Real #.  The tools still works; you just get the error message.

     

     

  13. Cas

    12 minutes ago, Casey Taylor said:

    I cannot play or download the video on my Mac or PC, any suggestions?

     

    Not sure what to tell you.  Like the video, itself, the format is old but I was able to play it at my end.

     

    If you're a Service Select subscriber, the same video is available on this page:  https://serviceselect.vectorworks.net/training/webinars/tips-by-guest-presenters-and-vectorworks-power-users/2014/index/? .

     

  14. Casey -

     

    2 things:

     

    1)  I'd recommend your fixtures and truss being on the same Design Layer.  Use Classes to organize "what" things are and Design Layers to organize "where" things are.  Therefore, using your example, same "where" = same Design Layer.

     

    2)  Expanding on #1, a DLVP can't be raked unless it contains at least one Lighting Device.

     

    Here is a link to a Webinar from several years ago that includes a segment on raking DLVPs:  http://www.landrudesign.com/Webinar2014FollowUp.htm.  While the video is old, the approach still works well (I used the technique 6 times in a design, today).

     

    • Like 1
×
×
  • Create New...