Jump to content

VectorGeek

Member
  • Posts

    233
  • Joined

  • Last visited

Everything posted by VectorGeek

  1. Read the section on plug-in menu commands here: http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=93218 Hope that helps. V-G. Ray beat me by 2 minutes... :-)
  2. Hi VWLP, There is a VectorScript routine for recalling saved views: VRestore('VIEWNAME'); Technically, you could created a plug-in command (a one-liner using the routine above, replacing VIEWNAME with the name of your saved view) and place it in a menu, then add a keyboard shortcut. The issue is that if a view name changes (or you create additional ones), you'd have to edit the plug-in and/or create a new one each time. Cumbersome to say the least. You do realize that you can open a floating script palette with all saved views, and that you can access saved views from the pop-up menu in the mode bar? Both of these methods provide quick ways to choose a saved view. Using a KB shortcut may not be much faster.... Hope that helps. V-G.
  3. Hi Ron, Have a look at the Visibility Tool. In the tool prefs, there is an option to have all layers become visible on a double click. That gets you half the way there. Returning back to the previous layer visibility settings could be done with a saved view, or by using the undo command (assuming no other actions have been performed). Sincerely, VectorGeek ----------------------------------------- VW 2011, SP5 Mac OS X 10.7.4 1962 Plymouth Valiant -----------------------------------------
  4. Thanks Miguel, Not working at all for me. The DLVPs are referenced from an external source and as such, the layers do not appear in the main document layer list. This may be the problem. I am thinking that SetVPLayerVisibility() was intended to work with Sheet Layer Viewports only. V-G
  5. Raymond, My apologies for a slow response, however I have been holidaying and catching up on my celery consumption over the past week. Thanks for this additional information. The fact that it came from Petri means that I will forever add the following line of code in any routine where I use it: {the following routine graciously offered by Petri Sakinnen, giver of all that is good and vanguard of all things Finnish} Namaste, VectorGeek
  6. Hi all, I need a quick way to set various layer visibilities in a file containing 160 referenced Design Layer Viewports. I tried using SetVPLayerVisibility(), however it did not seem to work as advertised (it does nothing). I am wondering if that's because I can't get a handle to a layer inside a DLVP (since it's encapsulated in the DLVP and doesn't appear in the file's main layer list). So I tried adding the layers that are encapsulated inside the DLVPs to the main file layer list. The SetVPLayerVisibility() routine now reports TRUE but no changes are affected. Anyone have any success doing this?
  7. That's GOLD Raymond. Thanks for posting. I figured it was something to do with the cumulative angles, however this definitely fast tracks me to finishing up my object. Thanks a million! V-G Olympic Couch Surfing Champion.
  8. For both OffsetPoly() and OffsetPolyN(), the offset varies from one side of the control line to the other, based on the "sense" of the poly. As the VSFR states: "When offsetting an open polygon or polyline, the direction of the offset will depend on the overall sense of the poly. From start to end, if the poly turns right more than left, the offset will be to the left, if offsetDistance is positive." What I need is a way to determine which direction the polygon is offsetting. I have played with various shapes, and can't seem to figure out what NVW means by the "sense" of the polygon, or what is meant by "turns right more than left". Any ideas? V-G
  9. Thanks Raymond and Andrew for looking at this. After more playing around, I think that OffsetPoly() is just plain broken. OffsetPolyN() does result in the object being deslected after regen, however by adding a line in the PIO code to select: SetSelect(parmHand); that seems to fix it. Many thanks. V-G. Purveyor of fine cigars and whiskey.
  10. Anyone?? NVW? I could use some help on this one. V-G.
  11. Hi all, This line of code: newpolyh := OffsetPoly(oldpolyh,irailoffset,1,TRUE,TRUE,16,1); results in a successful poly, offset from the source poly as expected. However, at every outside corner, there are two additional vertices (one in each direction from the corner point), offset by the irailoffset parameter. Not sure if I understand the parameters correctly. Can anyone suggest what I may be doing wrong? I would use OffsetPolyN, however when used in a PIO, it forces the object to be deselected after every regen. A bug dating way back that hasn't been fixed in VW 2011 SP5 (have not tried VW 2012). Thanks! V-G.
  12. 1 out of 7 machines in our office has this problem - "XX" on the keyboard doesn't deselect as expected. - VW2011 SP5 - iMac i7 - Mac OS X 10.7.4 - all workstations run identical workspace Time for a reinstall I suppose? Anyone else seen this problem? V-G.
  13. I give up. Procedures that we used to use have been deprecated, but I don't see a replacement. V-G VW 2011, SP5 Mac OS 10.7.4 iMac i7 iPhone iPad iCarumba!
  14. Hi there, We're utilizing a a server-side workgroup folder for all plug-ins, libraries etc. I have a few custom plug-ins that grab symbols from library files and bring them into the local file using CopySymbol(). For obvious reasons, I need to use GetFolderPath to do this, however it doesn't seem to support workgroup folders. Anyone know a workaround? V-G ---------------------------------------------------------------------- VW2011 SP5 Mac OSX 10.6.6 iMac i7 27" with defibrillator Wireless Herman Miller office chair ----------------------------------------------------------------------
  15. Hey Christiaan, That elevation looks great. Is their a requirement to "dumb" it down by removing the shading, or am I missing something? V-G.
  16. If you're not now you will be. No worries. I have a feeling we'll continue to be very profitable despite. I don't see any evidence of this. In any case how could you make this judgement without knowing who you're talking about? Paul Morrell, the UK Government Chief Construction Advisor, is hardly such a person. We see it all the time Christiaan. The last time was when a certain government agency REQUIRED us to use AutoCAD. We politely told them "Seller sets the terms", and provided .DWG files at the end. The person who created the policy turned out to be an accountant. I hope that was in jest. :-) Come on, there are sensible people everywhere, including over here in North America. In fact one of the LEAST sensible people I have ever come across is from Finland. ;-) We're well and truly past this debate. BIM is being driven by all sorts of industry players, including architects and engineers. As far as I'm concerned it pains me to know that we have such a backward inefficient industry that hasn't made this switch earlier. You might be past it. As a decision maker, I am not, and will continue to educate clients on the fact that WE as architects know what technology is best. Whether it's BIM, Non-BIM, 2D, 3D, or whatever the flavor of the day is.
  17. We may be in the minority, but our firm of half a dozen principals and staff, doing primarily developer-driven multi-family residential work (towers, condos, townhomes) has absolutely no need for BIM. First of all, clients won't pay for it. They want the maximum amount of information for the minimal amount of fees. Secondly, we already produce automated door schedules, window schedules and finish schedules using VW worksheets. The process is simple, but could benefit from more Excel-like features in the worksheet. That's what I am talking about. NVW should be bettering what's already there rather than continually adding features. Remember, to a huge degree, marketing drives the software industry. Companies cannot allow customers to become complacent or else they won't upgrade. New features mean sales because we are told we MUST have these things, and many believe. We typically skip every two or three versions of VW to avoid jumping on this unneccesary bandwagon. We produce highly accurate, graphically rich drawings, using the 2D and data management features of VW. 3D is simply there to add context (and only on certain projects), but it is done at our expense. Governements or for that matter anyone who "demands" BIM is likely misguided. Someone in a back office who has no idea what they are talking about is simply responding to industry buzzwords. As professionals, it's our duty to drive the process and technology. We take the liability and our reputation is on the line. Why let software companies tell us what we need? Morning without coffee rant complete..... V-G
  18. Well Christiaan, we make our money from 2D presentations and 2D drawings. We use 3D in a parallel process only, but can't justify drawing buildings in 3D from the start. For the type of work we do, there is absolutely no point. We have no need to "morph" shapes. Personally, I would way rather NVW spend time improving performance, better WG referencing, better plug-in design and functionality, than more useless 3D features that we don't get paid to use. Just my 2 cents. V-G
  19. Thanks Christiaan. I hear what you are saying. Unfortunately, most of our projects will be active for a couple of years from today. It's just a big pain to have users run two different flavours of VW for that long. Interesting about 2012. This yearly schedule of NVW upgrades makes things even more difficult. By the time we get everything switched over (be it 2010, 2011, or 2012), 2013's release will be imminent. :-/ V-G.
  20. Hi all, Looking for some feedback from experienced users: We are currently using VW12.5.3 on Mac OS X. No issues at all, most stable version of VW we have used (been around since the early days of MC). We are about to do a system-wide update to get more current with VW. We own multiple licenses for 2010 and 2011. Wondering which version we should standardize on, given the following: - ideally, we'd like to be able to move all current VW12.5.3 files to the new version we choose, therefore backward compatibility is of UTMOST importance. If we encounter problems in this respect, we're in trouble. - we don't use 3D other than as a separate stream for presentations. We are a production-oriented firm, doing large-scale multi-family, institutional, and commercial architecture. - Current hardware is new 27" iMacs running 10.6.7, soon to be running Lion. - We use symbols (often nested several deep), tons of walls, over 75 customized plug-ins (all of which have been tested with newer versions and are fine), and worksheets/databases extensively. We don't rely too much on workgroup referencing. I'd be curious to hear of anyone's thoughts and advice. Particularly, with respect to the issue of backward compatibility in moving from VW12 to 2010 or 2011. Respectfully submitted, VectorGeek
  21. You can't simply copy/paste Viewports across files (alert with error), but there is a trick: group them, then copy and paste them. Then remember to give them a name, because they are unnamed after this process, which isn't a good thing. This is valid for Sheet Layer Viewports. orso Thanks orso (I forgot to mention that part of the method). Also, when you use this procedure, the links to the source layers are gone. No fear, just use the Eyedropper Tool and pick up/put down attributes (including Viewport Attributes). Works like a charm and has personally saved me many hours. V-G
  22. Hi Charles, Once you have imported the layers and classes, you could cut and paste viewports from one file to another. VectorGeek -------------------------------------------------------------------------------------------------- VW12.5.3, 2010, 2011, depending on the moon phase Mac OS 10.6.6, iMac 27", 8GB Vast collection of Pez dispensers
  23. Call me a non-believer, for the type of projects we do, I'm not convinced we could be any faster using BIM. The four most important features that have allowed us to take maximum advantage of our investment in VW are (in no particular order): Parametric objects, especially the ability to create our own Viewports Built-in database/spreadsheets Workgroup referencing Those, coupled with VW's excellent 2D tool set, layer and class paradigm, and ease of use, are the reason we stay with it. You could take the rest away and we would continue to perform at the same level.
  24. Try this. You'll need to make a new palette and script, then paste this code into it and run it). Have not tested thoroughly, feel free anyone to improve. {----------------------------------------------------------------------------------------------------------------------------} Procedure unlocker; VAR h : HANDLE; Procedure unlockme(h : HANDLE); BEGIN SetSelect(h); UnLckObjs; END; BEGIN ForEachObject(unlockme,(INSYMBOL & INOBJECT & INVIEWPORT & (ALL))); DSelectObj(ALL); END; Run(unlocker); {----------------------------------------------------------------------------------------------------------------------------}
×
×
  • Create New...