Jump to content

ccroft

Member
  • Posts

    522
  • Joined

  • Last visited

Posts posted by ccroft

  1. There's almost nothing in print.

    Older versions had a printed Language Guide. Maybe you know somebody who has one.

    I might consider printing the pdf, but at best it's a guide.

    I found an old text on Pascal that helped me with some of it. They're similar. It's Programming in Pascal by Nell Dale. Of course there's no mention of any of the 'built-in' Vectorscript functions, but it might help with understanding Procedures, Functions, Variables, Scope, Data Types and other constructs which the two share. It helped me...somewhat.

    It won't help much with understanding things specific to Vectorworks such as parametric objects, working with objects in a drawing, or criteria specific to our program.

    As I've said before, there's no substitute for bone-headed determination and experimentation. An obsessive personality is powerful engine in this pursuit.

    Keep trying.

  2. I'm having the same prob on 2 machines. One runs 10.5.6 and the other the next previous version.

    I clicked check for updates in About Vectorworks and went from there to:

    You need to update!

    Your version: Vectorworks 2009 Service Pack 1 (Build 96841)

    Current version: Vectorworks 2009 Service Pack 2 (Build 99197)

    From download page I got the disc image: Update to Vectorworks2009SP2

    My serial number starts with A.

    I do have SP1 applied. Build is 96841

    My file is called: Vectorworks 2009.app. I didn't rename it.

    It's in the Vectorworks 2009 folder which is in Applications (everybody found it OK)

    The installer took to me to the brink of goodness then spit this back:

    "Your version of Vectorworks was checked against the most current version and no updates are needed at this time"

    What can it be?

    {edit} I had thought for a minute that maybe it was something to do with 10.5.6, a very new OS update, but I've since seen in other posts that this works for some.

  3. Presumably there's something else going on here...

    Choice box with pre-defined strings perhaps?

    Symbol with linked text from attached record maybe? (no scripting required)

    Can't really remember how this works but it's in help. I think it lets you type in Object Info Data pane and have it show up in the symbol in the drawing. The symbol could contain a text box.

  4. Thanks for the heads up Lyndsey.

    We've known it was coming and nobody looks forward to re-write, but 2 years is a timetable I can work with.

    For anyone who's not familiar with it, I've found DialogBuilder to be an excellent resource for learning and creating ModernDialog. It has a translate, or import function that sometimes works to update a Classic dialog.

    Support>Customization>VectorScript>Tools

  5. A fine fettle indeed Raymond. Hope your fettle is good as well.

    Haven't been scripting much lately though, aside from updating a few things in the transition to 2009 from 11.

    Yeah, I like the minimal aspect. This inline expresion is very similar to using a function as a parameter instead of introducing another variable, assigning value and using that.

    And thanks for iiiiif as well. Could be a huge IfThen killer for me. I have some that seem to go on forever.

    Winter's coming on and that's the coding season for me.

    Maybe I'll dream up a new tool that needs a list box of some sort.

    See you around I hope.

    Keep on lurking.

  6. Thanks for posting Ray. An opportunity to learn.

    What do you call (MenuChoice=1)..."boolean expression" or somesuch...

    At any rate I like the logic and will use it.

    Never thought of doing that directly in a function.

  7. Not really sure, but it seems you'd have something somewhere that said:

    If (pull-down choice) = (this or that) Then SetItem(check box identifier,True);

    I'm guessing you have a Case Statement in a Dialog? This would be after the item number of the pull-down. The part where you reap the users choice and do something with it. Not that I've ever used a choice box myself...

    You might have to post some code to get more help. Maybe even from someone who knows list boxes!

    Charles

  8. Hi Folks,

    What I alluded to only works with menu command plug-ins, and it worked for me in 11 and 2009. It's the same as reading and writing to any record.

    After re-visiting this post though, I think that a menu command might not be the best choice for a script to draw something. In that case command parameter records are useless.

    For a pallette script, I suppose you could (thru script) attach a record to the object being produced, and read and write the values from the dialog to that.

    Not sure how you manipulate defaults with an Object tho...

    Later

    Charles

  9. If you're interested in the code that makes this happen, option-double-click (Alt?...don't know windows) 'Rotate' in the palette.

    Most of this is about the dialog. The code that makes the animation is towards the end, after the row of =====, starting with BEGIN: {Maine}

    'recordH :=' etc is about retrieving the last used setting of the slider. This value is written to the record 'Gear Record' before the second to last 'END' with SetRField(etc).

    REPEAT (and so-forth) UNTIL (and so-on) actually makes the animation happen..

    If you already know all this, please forgive me for stating the bloody obvious.

    Doing the same in 3D might be slightly more complicated. I don't know since I haven't written much that operates on 3D objects.

    Charles

  10. Assuming a menu command, you create parameters in script editor.

    Then use SetRField and GetRField to read and write to the parameter record. You get a handle to the parameter record by calling GetPluginInfo(menuName,hRec).

    It's a storage area that remains in the document.

    It's in VectorScript language guide in Help...somewhere.

    Hope that helps,

    Charles

  11. So Mike....do you know which one of those controls the color/opacity of the area inside the bounding box of a selected group? It seems i can adjust the border but not the background.

    I fiddled with almost every one of those before posting. (that's why I used the name of the button for the subject :-)

    I think maybe Pat's right. It appears to be pretty much the same color that shows the page outside of the printable area on a sheet layer, and that's probably not adjustable.

    No big, but I'd change it if I could.

  12. Just wanted to add a few thoughts. Users have beens asking for better documentation and a simpler interface for years. Not to let Nemetscheck off the hook on this, bit that is not a trivial undertaking.

    I think one of the main problems is how flexible they are. For EG this thread started with Terry's drawing structure of different wall types on different layers, and separate reports to deal with them. And that's what he got. He might have started with a structure that has everything on one layer, and he would have a completely different worksheet set-up.

    There are many ways that a data-base row can distinguish one object from another: Class, Line-Weight, Name and info in attached records to name a few that I use a lot. A user needs to think deeply about what data they need to extract and how they want to manipulate that data before setting out on this journey.

    Personally I don't want a worksheet that relies so heavily on actual drawing structure. I want to be free to draw anything anywhere, and do the data work when I'm happy with the drawing.

    One possible strategy might involve attaching a record to each pour. The record format could have fields to identify the different kinds, and the costs involved with each, including forming labour, clean-up costs and so on. A data-base can find objects based on records attached and fields within, and can grab any info that is contained in the those fields.

    Or you might have a few record formats: one for each type of pour. The cost fields could have their default values pre-set for each situation. Then it's pretty much a one click operation to attach the right record, and feed the data to the worksheet. If you have a one-of-a-kind situation and need to make an adjustment to one particular pour you just tweak a number in the record.

    My main point is that to truly explain and instruct on this subject you'd need a very robust book. Something like FilemakerPro for Dummies...if there is such a thing.

    I think there's no end to what you can do with worksheets once you get started.

    Thanks for listening,

    Charles

  13. Hey Wyle,

    Might be something wrong with your help files. I have a section called "worksheet rows". Not sure about windows installation, but you might want to go into vWorks folder>VWHelp and try opening index.html. There are also user guides pdf's in here inside Additional Documentation.

    As for learning how to get the most out of this feature, I have 2 words for you: Bone-headed Determination. That's how I (and probably Pat) learned.

    If you want to learn total control, I suggest you forgo Create Report and build your own from scratch...like from a blank worksheet. Start simply and go step-wise, adding columns and formula as you go and experimenting along the way. For what you're trying to do, you'll need to know how to add some custom columns and you'll need to learn how to write and edit criteria, functions and formulae. The basic information is in the help files.

    It's a lot like learning a language.The few words you've learned so far is a great start, and now you need to understand the syntax, grammar and structure. I think Create Report is a kind of short-cut through this learning curve that serves most people pretty well. But it wasn't created with concrete contractors (or cabinet makers) in mind...we have to learn how to create the "options in the worksheet" that we need to get the job done.

    After you start to get it, you should investigate how attached records interact with database worksheets.This can bring another level of control. You'll want to have a look at the section on records in the user guide at that point.

    Give yourself some time and just keep at it. When you reach the goal you'll have an extemely powerful tool, and you can say good-bye to manual calculation.

    What you want is totally do-able, and learnable from the documentation.I know this for a fact. I do all the material take-offs, shopping lists, labor estimates and so on for a 7 man cabinet shop with worksheets I built some 8 years ago.

    Best o' luck,

    Charles

  14. Thanks Atari,I'll have a look at that one too.

    Pat:One of the things that keeps me in 2d is the script I wrote for sizing my 2d groups. Just input the new height and width and the components are moved/stretched appropriately. Able to edit multiples too.

    Manually editing these is too time consuming, given the number of times I have to tweak cabinet sizes in a day.

    I did make a couple of 3d cab PIO's that almost work the way I want, and was planning on a full suite....but then I saw InteriorCad. I think this'll be my final solution to custom 3d cabinet design. Until then...homebrew tools and 2d for the most part. And some further tinkering in Architect to see what's feasible.

    Thanks all

    Charles

  15. Thanks for the replies.

    Pat...hmmm decisions decisions. I set up a drawing using views and that's more like how I'm used to working. But I have a feeling that if I set up sheets/viewports that I might find new and better ways. Guess I'll just have to try it for a while. At this point I'm not sure if I can see the advantages of one over the other. Either way this'll all be in a template so it's more about workflow than setup.

    gmm... I'll be looking at working with the PIO's. Seems like the main problem is changing sizes and keeping the details in place. I'm also thinking of using a combination of cab PIO's and 2d detailing.

    Back to drawing organization. If there are people out there doing this kind of thing I hope they'll share their ideas!

    Thanks

    Charles

  16. Hi folks,

    Haven't been around much lately, but I'm evaluating an upgrade from Fundamentals 11.5 to Architect 2008 and have a couple questions.

    I'm a long time user. I run a cabinet shop and produce drawings for approval and construction. These are in the form of an A4 booklet, usually with about 10 pages: plan,elevations, details, site dimensions,specs and so forth. All old-school 2d.

    We're thinking Architect mostly for the productivity tools. Chief among these is batch printing and pdf output. Til now it's been print to pdf one (design) layer at a time, and a third party app to combine into one doc.

    It appears there's no batch printing or pdf'ing of design layers. Is this true or am I missing something?

    If it is true, it looks like I'll be building a template with a design layer for each page (like i use now), with each of these VP'd to corresponding sheet layers. Then I'll draw as I always have, but with the sheets happening in the background until it comes time to output. Looks pretty workable to me at this point.

    Anyone have a better way?

    So far things are going well. All my custom stuff works as before. Rotate plan, 2 way worksheets and nav palette are worth the price of admission.

    I'm also looking at the cabinet pio's for simple perspectives. Unfortunately these don't have the level of detail I need to be able to rely on 3D alone. Maybe one day we'll get InteriorCad, but that's a ways off.

    Thanks for any input,

    Charles

  17. A script could do this, but are you aware that if you configure a plug-in, then make a symbol out of it with 'convert to plug-in' selected under options, it will insert with that same config and remain an editable object?

    You can build a library of common configs. You can probably then use the replace symbol function to switch configs in a drawing.

    Powerful and sometimes overlooked feature.

  18. As to the original question, I've found that plugins are the best answer. That's how Vectorworks itself handles it, and that's how I've been doing it for years.

    Having the latest and greatest version of your scripts available at all times and on all machines (if you use more than one) is a great benefit. If you change something in a script in one installation, you just drop the new plugin into the other plugin folders without any need for workspace editing.

    You get the added advantages of keyboard shortcuts for menu commands, and palettes for tools. Also, in many cases a plugin behaves differently when it's run from a palette, and VSO doesn't work at all that way. So as your customization grows you may find yourself maintaining workspaces anyway in order to use these types of scripts. If you start now with the plugin scheme you'll have a strong framework in place to handle everything down the road.

    If you do start making plugins, be sure to use categories. That makes it a lot easier to maintain your workspaces.

    Syncing only 2 workspaces on the same machine isn't a lot of work as far as I'm concerned, and like everything else the more you do it the easier it gets.

    c

×
×
  • Create New...