Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

40 Great


About MullinRJ

  • Rank
    1000 Club

Personal Information

  • Occupation
    Circuit Board Designer
  • Location
    Dallas, TX

Recent Profile Visitors

934 profile views
  1. How to convert old MiniCAD .mcd files

    Steve, Good news. On a whim I tried a later version of VW to see what would happen and VW 8.5.2 opened the file. In you email you ask if I can export as a DWG file. I can, but I may not pick the settings you'd like. That kind of translation is somewhat "personal" and is often done several times before it exports to your liking. What version of VW do you have? I was able to bring it up to VW 2018, but that won't do you any good if you don't have it. Making progress, Raymond PS - if you add a signature to your Forum Profile, and include your version of VW and your OS it will help others answer your questions more accurately.
  2. How to convert old MiniCAD .mcd files

    Hi Steve, You will need to contact Vectorworks Support for this file. It appears to be a MC 7 file, but it was created by a BETA version of the software and the file format is not the same as released versions. Unless you open it with the right beta version it is not readable. Hopefully the engineers in the Mother Ship can help you. I tried to paste a picture of the warning but my file upload failed. You can send me another or all of the files and I can tell you if they are BETA files, or if they will open. All the best, Raymond
  3. How to convert old MiniCAD .mcd files

    Hello Steve, How many files and how big? If it's not too many files I could convert them for you, assuming you are free to send them to me. As to the byte sequences - YES - modern VW files have a header you can read with a text editor. Older MiniCAD files, not so much. I'm not sure when the header became human readable. My suggestion, open a file in a text editor and see if you can make anything out. If not, no harm done. Just don't save it with the text editor! If you'd like me to update your files, you can email me at mullinrj AT aol.com. HTH, Raymond
  4. Converting file

    Hello Victor, No, you will need VW 2018 to open it. If the file is not confidential, I'd be happy to convert it for you and send you back a VW 2015 file. You can email the file to my AOL address. Use MullinRJ AT aol.com. I hope that's not 2 cryptic. ;-) Raymond
  5. Arcs to circles.

    I downloaded the file in the first post on Mar 17th, but only now played with it. Like Kevin, I reduced the network to take advantage of the vs.SetArc() command. This has the advantage of preserving the graphic attributes of the original ARCs and their stacking order on the page. I, too, noticed UNDO was broken for my network, while it works for the original network. I believe this is due to the different ways these networks run. Rob's network runs like an object PIO, and Kevin's and my networks run like a Menu Command. Rob's network uses ARCs as input and creates a group of CIRCLEs from them, then it deletes the ARCs; while Kevin's and my networks modify the original ARCs and create no output object. A typical Marionette network creates an output. When a network is rerun, the existing output object is deleted and a new object is created. UNDO works for this scenario. In my network, no new object is created. The existing ARCs are modified to CIRCLEs. UNDO does not work to restore them. See attached file. Marissa, I hope this gets you pointed in the right direction. Raymond arcs to circles (RM).vwx
  6. Geometric Algorithms (a.o Voronoi)

    Dave, I clicked "Open image in New Tab" and the entire PDF opened there. I wasn't expecting it to open that way, but it did. I just did it again and it still works. Raymond
  7. Clearing Dialog pull down menu

    Sam, After reading Julian's comment I looked at your code and mine again; there is a difference. I always remove the 0th element (the element at the front of the list). Julian's way removes the last element every time. You are removing the element at the index counter, which is a moving target. Eventually, the list gets shorter than the index counter and you will receive a runtime error. You need to pick one of our two methods and you should be okay to proceed. Raymond
  8. Clearing Dialog pull down menu

    Sam, It looks like your code should work. Have you verified that "fieldCount" is > 0? If it is, are your "Dialog" ID, and your "kTargetData2BOList" constant correct? I use something similar in Reshaper, where GetChoiceCnt is a custom function that returns the menu size from GetChoiceCount(), just like yours. for I := 0 to GetChoiceCnt(dlogID, MenuItem)-1 do RemoveChoice(dlogID, MenuItem, 0); HTH, Raymond
  9. Symbols in PIOs...turn off 2D?

    Control the visibility of the parts with classes. Raymond
  10. Quitting & Closing the VW Program by Red Dot

    If you use individual drawing windows, like in the good old days – Red Dot. If you use the "Application Window" – no Red Dot. Toggle the "Use Application Window" menu item to see the differences. Of course, I'm only speaking about the Mac. HTH, Raymond
  11. Layers with Python

    Martin, A basic Plug-In object is a SINGLE object and it must reside on one layer. It can contain multiple parts, like a symbol or a group, but it is treated as ONE object. You can put the pieces in multiple classes, but not on multiple layers. It is possible to "cast off" objects to other layers as your Plugin code runs, but that is definitely not standard practice. You could run your code as a Menu Command and draw on separate layers. That is more akin to running code from a script palette. Write back if you need more direction. Raymond
  12. Layers with Python

    Martin, Try this script: import vs; vs.Layer('Screen - Panels') vs.Rect(0, 0, 1, 1) vs.DSelectAll() vs.Layer('Screen - Data') vs.ArcByCenter(1, 1, 0.5, -90, 270) vs.DSelectAll() It creates a layer and draws a Rectangle on it (and deselect it), then creates another layer and draws an Arc on it (and deselect it). How does this differ from your script? Raymond
  13. screen plane only

    Gentlemen, I posted this as a bug on January 1st. I was informed it is (or will be fixed) in a future release, but I don't know which one. Hopefully the next one. I was able to determine through testing that the bug only affects files saved in VW 2018, as files saved in VW 2017 open correctly in both VW 2017 and VW 2018. If you use a particular template file often, you could export it to VW 2017, resave it as a template file in VW 2017, then move the .sta file to your VW 2018 User Folder under the "Vectorworks/2018/Libraries/Defaults/Templates/" directory. Save your VW 2018 version of the .sta file in another folder. Of course if you already have a template file in VW 2017, you can drag a copy of it to your 2018 User Folder. As soon as the bug fix is released you can replace your template file to the VW 2018 version again. This won't correct the problem when you save and reopen regular files, but at least you'll start a new file correctly. HTH, Raymond
  14. 2D Symbols always insert at the drawing origin.

    Obviously not known by everyone. Are there any "known" workarounds? Thanks, Raymond
  15. 2D Symbols always insert at the drawing origin.

    Sorry Michael, no new ideas here. Questions, but no ideas. Does this happen in all files? Files created from a VW 2018 template? Blank VW file? Files converted from earlier VW version(s)? PageBased, or WorldBased symbols? Can you post a problem file here? Raymond


    • 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.