Jump to content

_c_

Member
  • Content Count

    981
  • Joined

  • Last visited

Everything posted by _c_

  1. _c_

    Until Next Time

    Dear @Jim W, I wish you all well. You have been the heart of VW, you'll be missed like no-one else before. VW lost his soul. Hugs, your very, very sorry _c_
  2. _c_

    Date format in current plot date

    No! It is THERE! Nikolay, wonderful! There was people here not using the old title block because the date format would be "strange"!
  3. _c_

    Post-Brexit support for UK VWX architects

    Oh, finally the strong elbowed freelancer residing in Kenya that I am sure every British office was waiting for, to replace the in-house European colleagues. So trustable. Are you spam or do you simply sound like it? One is wary of clicking on your link, just for you to know.
  4. Carl, jump back in! You'll love it! Vectorscript evolved quite a lot since then and it's lot of fun. We have the Developer wiki now, a little obsolete but still of great usage is also Vectorlab.info. And the community shifted more into this forum rather than the v-list. And if you are wiser than me, you'll do the jump into Phyton right now rather than later. _c_
  5. Ciao Carl, I am very pleased to see you here. I remember you very well from a rather remote past ... making something out of VW logs...the Time Clock! here it is. Welcome back! You won't remember me, it was many alias names away. I don't even remember myself which one I used then. _c_
  6. Nice, danke Patrick
  7. _c_

    Issue with "Extrude Along Path"

    Hello, by chance I stumbled upon this discussion. I know it's late but it might save a lot of searches later for others. You must "flatten" the path object, you can also use SetPlanarRefIDToGround. Example: RectangleN(x, y, 1, 0, w, h); pathObj := LNewObj; SetFPat(pathObj, 0); SetPlanarRefIDToGround(pathObj); { without this, your ExtrudeAlongPath will be extruded along any view you happen to be in } pathObj := ConvertToNURBS(pathObj, FALSE); obj := ExtrudeAlongPath(pathObj, profileObj); { profile object is a poly, rect, oval etc. }
  8. _c_

    Project sharing workflow

    Ciao Christiaan, I am of the opinion that live sections are just an edit tool. No need to have that also published, they also require a different set of attributes. BTW, only now, by the released SP3, am I able to use the sections as live tool, they were simply too crashy and had an ugly performance making them unusable.
  9. _c_

    Project sharing workflow

    Ciao Hans-Olav, I find it impossible to have a singular file. No idea how to archive and manage the obsolescence of the Viewports in that structure. The file size! We have this structure below, which is close to your one. It is very flexible and stable. We don't use project sharing where we issue (Sheet layers). What you call Target files. So the answer is: no, I'd advise you not to use PS in target files. Our structure: Folder 0 1 or more project files (.vwxp) containing everything excluding sheet layers 0 or more normal files (.vwx) containing 2D details, variants, etc. excluding sheet layers reference across these mainly old style, no automatic update Folder 1-5 (data collection, preliminary, project, permits, construction drawing) plot files, data etc. thematically sorted, all references old style to folder 0, no automatic update Archive of the issued files above: as soon as we issue a set, we archive the whole file. On top of the folders remains the last used file set Worgroup: 3 Workgroup folders for the office, project specific resources are never there. No problem with Project Sharing and referencing in this workflow, as far as I am aware.
  10. _c_

    Geometric Algorithms (a.o Voronoi)

    Indeed, what a strange link it generated. Here it is in a more old fashioned way: link Dave, there is nothing there that you won't know and probably already surpassed ages ago with your own algorithms. But it offers us a readable introduction to things which are otherwise far beyond our reach.
  11. Ciao, I'd like to share this awesome link for those interested: Geometric Algorithms
  12. _c_

    Mac to PC file sharing

    I had in the past problems with the paths used by the Callout and heavily with encoding (special EU chars). This last should be resolved with VW 2018.
  13. Hello, for those interested, I updated Orso's Test script for List Browsers which was by now really completely obsolete: here. It's purpose is to see what happens changing things. This is a more or less comprehensive script covering most list browser aspects and is connected with the h*u*g*e List Browser article on Vectorlab, which was also rather obsolete. I gave it a fast refresh now but it still needs work. If you copy that script, please revisit the page in a while, because it might have changed. Ciao A screenshot of the List Browser test script:
  14. _c_

    List Browser comprehensive example

    We have one, it was written by Charles Chandler (Charles, where are you?!?): http://www.vectorlab.info/index.php?title=Events you should complement it with the articles of Vlado on Dev: http://developer.vectorworks.net/index.php/Category:VectorScript
  15. _c_

    List Browser comprehensive example

    Speaking about LBs, the funny thing is that it seems that now the dichotomy edit/item display type is gone: whatever you edit, the other one will match. It could be one of these things that went on legacy and has been fixed in this fashion to preserve our scripts. Thank you!
  16. _c_

    List Browser comprehensive example

    Ciao Sam, do you want to link to this thread or to the original LB article on Vectorlab? That would be better, that's the one I will maintain: http://www.vectorlab.info/index.php?title=List_Browsers Ooops... edited the link
  17. _c_

    Curved Walls in Hidden Line

    It is a bug, unfortunately, but should the resolution be faster if it files as wish, please, let it be a wish! We collectively wish round walls not to leave lines around. I feel safe to speak for most here. Out of pure curiosity, who wishes that round walls don't join and show dismembered in viewports, renderings or any form of view -even in plans, under certain conditions- please raise a hand. Ciao _c_
  18. As I promised a while ago, here are the TextWrangler/BBEdit Vectorscript Keywords files for VW 2018. This is a zip file containing two vectorscript files: VectorScript Keywords_VW2018.px VectorScript Keywords_VW2018.vss Please expand the zip file place both resulting files in the "Custom Keywords" folders: /Users/[userName]/Library/Application Support/TextWrangler/Custom Keywords /Users/[userName]/Library/Application Support/BBEdit/Custom Keywords restart TextWrangler or BBEdit From now on any file whose suffix is .px or .vss will load those keywords for highlighting. If you need more informations please consult the Manual on Textwrangler or BBEdit. Ciao VectorScript Keywords_VW2018.zip
  19. Hello, for those who downloaded the plist file already, I uploaded now a new version: I forgot to change the internal version ID and it didn't display well.
  20. Ciao Sam, I added it now, VectorScript 2302-new.plist.zip but it is simpler to use the built-in vectorscript code adding the keywords. That resolves pretty well everything while my old plist file was rather slow, due to -I believe- some inefficiency in the grep for indenting the routines. In the attached file you'll see that the routines don't indent well in the menu. If you set now TW or BBE on "Vectorscript" or "automatic" it chooses the proper keyword file depending on the suffix, .px or .vss, and it behaves as the plist files! Look at the screenshots below and tell me if it works by you: I add here the instructions of TW 5.5, I found this change genially simple:
  21. _c_

    Curved Walls in Hidden Line

    Please Jim, this is really, really old. It can't be still there. _c_
  22. I attached one set for you to use, that includes ALL hidden functions that I could find, also stuff really buried in the resources. Look at the zipped file attached to my post.
  23. To fix the encoding error in VW 2018, something that I also had extensively, this worked very well for me: open all your vectorscript files in TextWrangler/BBedit In the bottom bar, set the encoding to "Unicode (UTF-8)" (see screenshot) save close Don't use "File > Re-open using encoding..." because that will mess things up for reasons that I fail to understand Ciao

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×