ahedley

Does anybody know up to what Revit version Vectorworks 2018 will import? A client sent a Revit file from his client, when I tried to import I got an error message saying that the version of revit was not supported. I'm not a revit user although I have revit LT 2018, so I thought I could just open it up and save at a lower version only to find out you can not do that. I suspect the file was Revit 2018. I was able to export from revit as an ifc and import into vectorworks. The import was good however I lost a lot of functionality in vectorworks like the create interior elevation viewports which needs walls to work with. I really needed that vectorworks command to work. It would be really appreciated if we could know upon release of a new version what versions can be imported. Perhaps a wish list item - if vectorworks can export its native objects to ifc it would be great to see ifc objects converted to vectorworks objects.

My apologies, I meant plug-in tools.

From what I understand GetPt( ) is used in vectorscript when you are trying to create a tool plugin object which may require multiple user points. GetPt( ) and GetPtL( ) are procedures that are used in conjunction. I have noticed in vectorscript it is relatively easy to use these procedures. However in pythonscript it is very challenging, for instance, vs.GetPt( ) using a callback function will work only once. Trying to get multiple vs.GetPt( ) calls thus far for me has proved futile. I have tried without success to use vs.GetPtL( ) which generally uses as its first point the point you select via. vs.GetPt. Has anybody had success creating tool plugin objects requiring user interaction using these procedures or is there another recommended way of creating tools? Most of my experimentation has been developing plugin objects, I want to broaden to tool objects.

Ryan, import vs vs.GetPt(lambda pt: vs.Message(str(pt))). Crashes vectorworks 2017 windows. Adrian

Thanks Dieter

Raymond thanks I've done a lot of those sin , cos gizmos over the years to appreciate their simplicity Thanks Dieter for your solution I'll try both and see what I come up with.

Thanks Dieter for the suggestion. pt is still trapped in the callback function. user_point = None creates the locus at 0,0 even before you have an oppportunity to select your user point. Even if you make user_point a global variable within the callback function which should theoretically change user_point = None it still does not work.

I spent a lot of time trying to get vs.GetPt() to work. I understand the callback function will extract the 2d point e.g def Callback(pt): vs.Locus(pt) vs.Message(pt[0],' ',pt[1]) vs.ReDraw() vs.GetPt(Callback) However I have not found a way to use pt outside the callback function. I can draw the locus using pt inside the callback function but not outside. I really want to create the locus using pt after vs.GetPt(Callback). Any suggestions ?

Thanks for the reply. I figured as much. Is there a way (simple) to use distance angle in python ?

Has anybody tried to use vs.AngleVar(). I tried to convert the example from the function reference into python to no avail.

Alan, I agree with Kevin. For Python, PEP 8 has emerged as the style guide that most projects adhere to. For classes and functions the convention is to use CamelCase for classes and lower_case_with_underscores for functions and methods. For variables, the first character must be one of the letters a through z, A through Z, or an underscore character(_). After the first character you may use the letters a through z or A through Z, the digits 0 through 9, or underscores. Vectorscript has its own set of naming conventions, which I have grown accustomed to. I noticed the practice of using the underscore after the variable being used by vectorworks, hence I just followed a similar practice. However, I definitely have to reconsider its usage in scripts I develop, it is apparent my eye has difficulty detecting its absence leading to very embarrassing errors. I have gone through each node and I believe I have made the necessary changes. I have attached the modified files. Something I should mention especially if you start to code your own scripts. When you use the script editor to write vectorscript scripts and your compile is successful you are generally confident the script will work. However in python, particularly creating nodes, your compile may be successful however your code may still have errors. Thanks again Alan, if you notice any further problems please let me know. Regards Adrian

Allan brought to my attention that two nodes in the 2d Objects category contained typo errors namely RRectangle and RRectangleN Nodes. Attached are the corrected nodes. Regards Adrian

Miguel, Thanks for your feedback. I believe you express the sentiments of most people who have read this post thus far. "Lesson Learnt" I should mention I have also made the Marionette Network Arches available as a free download, both are available in the Resource Share – Marionette section of the forum. Regards Adrian

Thanks Allan for trying out the nodes and pointing out the typo errors. Also thanks Kevin for taking the time to make the fix. If there are anymore problem nodes please let me know. Adrian.