Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by IanH

  1. Didn't realise that upgrade from Lion to Mountain Lion was so cheap so have gone with that initially. Still interested in Mavericks support though, but not so pressing an issue now.
  2. 30 years software development experience and also semi regular Vectorworks user and Vectorscript developer. UK based. As someone who has developed in Pascal commercially I can say that Pascal and Vectorscript are about as similar as apples and oranges.
  3. Is there any word on OSX 10.9 Mavericks support for VW in particular VW 2011? I am being forced by Apple developers program to move on from OSX 10.7 Lion to either released 10.8 Mountain Lion or upcoming 10.9 Mavericks but do not want to lose use of VW2011 that I occasionally need to use. As I see it, I either play safe and move soon to 10.8 that appears to be supported or wait/get develops preview for pending version. Would prefer to skip a generation especially this close to release of OSX 10.9 Mavericks. If anyone wants to reply in private, feel free to contact me without breaching developers terms as I'm also covered by the Apple developers NDA.
  4. Unfortunately I cannot provide much assistance but do empathise as I have seen it a number of times but never got to the bottom of it. I've got a feeling that there is/was a big bug in this area and it has been rehashed across different versions so the results/cause have never been consistent. I would also bet that the problem has not been fully resolved as I've also seen the problem in 2013. In early versions of viewport referencing, probably around vw2008/2009 early service packs, viewports would just move for apparently no reason. As service packs came out and versions were released, things got better and tbh, I don't see too many issues on 2011. But as I say, I've seen it on 2013 so the problem still exists. I cannot help with the 30 or so files, but can provide some advice on what to avoid to preventing it happening again. Things to try and avoid... Never move drawing origin. If you do, you will end up chasing your own tail. Try and keep drawing areas close to origin - not always easy. Make sure you have latest service packs installed Don't mix versions/service packs across workstations when editing - you may have a workstation on different sp causing the problem. When fixing the problem, save and immediately reopen and check for movement. Do this 2 or 3 times per drawing. Go through files methodically applying fixes one at a time. You may need to take files offline to prevent someone else editing and causing the problem al over.
  5. Have you thought about referenced viewports? Gets rid of the detritus of other people's working practices.
  6. Huh? I'll keep example in inches for simplicity... Assuming that you have a 1" x 1" image, at 10dpi it will be 10 'dots' x 10 'dots' in size, each 'dot' being 1/10th of an inch in size. Same 1" x 1" image at 300dpi, will be 300 'dots' by 300 'dots', each dot being 1/300th inch in size. The extra pixels come from the renderer resolving the model in greater detail. But both images are physically the same size at 1" x 1", but 10dpi version probably less bytes in size. Or have I misunderstood something in the question?
  7. Do you have Adobe Acrobat Pro or another PDF 'printer'? If so, you can print multiple sheets per page and output to PDF. You may need to combine the PDF's into a single PDF within Acrobat Pro if Vectorworks batch print does not send the output continuously enough for the PDF printer to be able to offer 4 up printing. This will give 4 sets of title blocks etc and you may have problems with maintaining 100% scaling without cropping. However, once set up, the following thereafter will be fully automated... How many is 'many'? Too many to create the A1 sheets necessary then copy the viewports from the A3's and paste 4 up on the A1 sheets? You will have one title block for all.
  8. Thanks. I've now devised my own algorithm. I had made it all a bit too complicated looking for a formula when a bit of logic and school boy maths have sufficed. Trying to do it programmatically without VW. Just used VW and road analogy as a quick example of what I was trying to achieve. However I have now learned that VW2011 offset tool does have a round corners option.
  9. Its not actually a road, but a track and can be considered flat with no speed issues. Basically I'm trying to draw two parallel lines of constant separation when I know the centre line - programatically without vectorworks. A road was best analogy I could come up with.
  10. Ignoring the tools built into VW, does anyone have a formula for calculating road widths? I know the centre line of a track, and want to draw the edge, of constant width 'w'. Unfortunately this is no ordinary track, and it is possible that some corners are quite acute. Image shows known centre line in blue and I want to plot the red lines and round the corners in black as VW Offset too creates lines non constant width when angles get quite acute. Thanks Ian
  11. How much memory does your PC have and what version or windows incl. 32/64 bit? That might give us a clue whether you have memory issues?
  12. Check that the contents (lines, fills etc) of the plant symbol are also in visible classes. They will not be the same classes as the class symbol. Also worth checking the import scale vs design layer scale. It may just be that the imported symbol is at 1:1 and you design layer is 1:100 etc thus your plant will be 100x too small. You can check this within the symbol and look at dimensions in oip.
  13. Thanks. I had thought that may be the case. No way to say export the resource to a file, hand edit it, then import it back in? Or even edit the original file?
  14. I have just added quite a bit of functionality to an old script of mine. Unfortunately, the numeric ordering of the resource strings is not as it should be and I would like to add a few string resources to the middle of the resource lists. A couple of the resource strings have been deleted so I have a few 'holes' in the consecutive numbering sequence. 1. Can I add strings back into these 'holes'? New strings simply get added to the end of the list. 2. Can I renumber some of the resource strings? Thanks Ian
  15. IanH

    Document prefs

    Decided to use GetPrimaryUnitInfo instead. Pref 171 didn't return what I had hoped. Pref 173 does though seem to be useful for preventing script from running if non metric.
  16. I want the get the document preferences for units and primary display precision. Just wanted to check that using GetPref and variants was the right thing to use. 170 and 171 respectively. Also, what is pref 173 for. My script is only designed to work in metric system and wonder if that will help me check that document is metric and display a warning if not. Thanks Ian
  17. Unfortunately, if you scale your title block, the DS doesn't. I use same title block for different sheet sizes and just rescale to visually match. As the DS does not rescale with the title block, I have to place it separately. Not a biggie for me as I don't normally produce more than one or two sheets per plan.
  18. Hi Matt Would Camera Match 2013 work on my VW2011? I had always assumed that the version of Camera Match needed to match the version of VW. Thanks
  19. Not sure if its what you are seeing but there is a bug whereby layers (classes?) added after an reference update if their layer (class?) name is more (less?) than a certain length. The fix I think was to change the length of the layer (class?). Sorry I've been vague and not remembering the exact circumstances.
  20. Most of its comments or checking for valid selection. The foreachobject at the bottom causes the convert procedure to be executed on all the selected stake objects. The setrfield in the convert procedure is the bit that populates the description with something (in the case above, the elevation in meters). The setrfield that follows then makes the stakeobject show the description field. Play around with the first setrfield will allow you to modify the results as you need. Simples. I'll be upset if you don't learn anything from it as you did ask me to share
  21. I quickly extracted this script from one of my routines. It works, but is not perfect and is only posted as an example. Use at your own risk! Its an example of handling the stake object in vectorscript. Basically, I scans the selected stake objects and replaces their description with the Z value in meters (I'm all metric based so don't need to worry about complex conversions) then sets the stake to use the description as its display value. Im not sure if you could put a newline in the value to allow a split Easting / Northing convention, but if convention allowed, it would be relatively easy to encode E/N onto a single line. { Sets description of stake object to Z value in meters { Stake object should be selected on entry { {(C) Ian Hutt 2008-2012 { { Nov 2012 - extracted and simplified code from set stake datum {} PROCEDURE setLevelMeters; LABEL 666; CONST stakeObject = 'Stake Object'; VAR datumObj : HANDLE; PROCEDURE convert( h : HANDLE ); VAR x, y, z : REAL; BEGIN GetSymLoc3D( h, x, y, z ); SetRField( h, stakeObject, 'Data', Concat( Num2str( 3, z / 1000 ), 'm' )); { Replace description with level in meters { You could try something like { Concat( 'E: ', Num2str( 3, x ), ' / N: ', Num2str( 3, y )) { to give a result such as E: 10.000 / N: 20.000 {} SetRField( h, stakeObject, 'Label Reference', 'Description' ); ResetObject( h ); END; BEGIN DSelectObj(INSYMBOL & INVIEWPORT & (PON<>'Stake Object')); datumObj := FSActLayer; IF ( datumObj = NIL ) THEN BEGIN AlrtDialog( 'No stake objects selected on active layer' ); DSelectAll; GOTO 666; END; ForEachObject( convert, (INSYMBOL & INVIEWPORT & (PON='Stake Object') & (SEL = TRUE))); ReDraw; 666: END; RUN( setLevelMeters ); As I say, it was lifted from a more complex function so is probably a bit more complex than need be in places. Some of the checks are redundant if run as a menu item as this handles object selection checking etc.
  22. My routines are built into more complex scripts but I will have a look to see if they would make sense if i quickly lifted the relevant subset of code out.
  23. I use stake object quite a lot. I have a number of scripts that manipulate the description field in various ways based upon stake object data values. This way I can cover most eventualities by displaying the description field, sometimes in conjunction with other standard fields.
  24. A client of mine found that pasting images into powerpoint (on Mac) resulted in lower quality images. This was with scanned hand drawn images rather than VW generated jpgs.
  • Create New...