Jump to content

MullinRJ

Member
  • Content Count

    1,304
  • Joined

  • Last visited

Everything posted by MullinRJ

  1. Years ago I used to swap right and middle button functions with the Logitec Control Center (mouse driver). I think it stopped working for me because my Mouse got too old and I fell into a software/hardware/OS support gap. I would look for Mouse Drivers that support this if you can't get there inside VW.
  2. Hi Lupin, Yes, it can be made to BEEP in both directions, but the intention of the BEEP is to indicate which way the script has run. When you hear the BEEP, you know without looking the menu is set to SCREEN PLANE. When you don't hear the BEEP you know without looking the menu is set to LAYER PLANE. I think you got the direction of the beeping backwards, but that assumes you copied the script exactly as it is above. However, this is very unimportant. If you just want to know the script has run because you hear the BEEP, then change your script as follows: { This script will toggle the "Active Plane Menu" between "Screen Plane" and "Layer Plane", } { and BEEP each time the script is run. } { 20 June 2018 - Raymond J Mullin } SetPref(1099, not GetPref(1099)); SysBeep; Notice I removed the IF statement on the last line but left the SysBeep command. The script will now toggle the 1099 preference value to its opposite state, and then BEEP, every time. HTH, Raymond
  3. Well, that's the first time I've seen that ObjVar used, though a quick search shows it appeared in VW 2014's documentation. I learn something new every day, even when I don't want to ;-) However, it does say "for use with SDK objects ONLY". Have you tried with VS or Python PIOs? If SDK Only, then it's true, the VS engine can only handle one task at a time without interruption. I can live with that. Thanks, both, for the info. Raymond
  4. Dom, I think you can only get your approach to work if you split your code in two. Your first script will contain everything up to, and including, your RESET calls. When your first script ends, VW will then reset all of the objects you marked to be reset. Your second script can then execute the DMTBN( 'Export PDF') call. It's a very sequential process, but your "Export" call cannot begin until all of the PIOs get reset, and they will not reset until after your script ends. Therefore you need two scripts that you will will launch sequentially. Not entirely elegant, but easily accomplished. HTH, Raymond
  5. Here you go... Raymond aktuell_RBL_Haus Heinrich v2015.vwx
  6. IIRC, when you select ALWAYS ALLOW, it is only for that session of VW. After VW restarts you will be presented with the question again. It took me a little while to figure out the scope of these selections, but I kind of like this level of intrusion. I don't have to worry about leaving the back door open forever if I forget to close it. For files of my own creation, I click ALWAYS ALLOW and keep working. If I am going to work on a questionable file, I can restart VW and I am covered again. Not ideal, but very workable. Raymond
  7. SetFillBack() is the call to edit a single object's background color. There is no SetFBack call, it was a typo. These calls are all documented in the Script Function Reference. If this were still a book printed on paper, you'd carry it with you everywhere, Consider it the VW Programmer's Bible. HTH, Raymond PS - Pat, thank you for the compliment. Also, in your previous example you set the Fill BG color to WHITE. Shouldn't it be set to BLACK? SetFBack(h, 0, 0, 0);
  8. You must also be careful here, too. SetFPat { FILL Pattern } 0 = No Fill 1 = Solid Fill using the BACKGROUND color { VW uses this as the default for SOLID FILL } 2 = Solid Fill using the FOREGROUND color In contrast: SetLS { LINE STYLE, the equivalent of the Pen's Pattern } 0 = No Pen 1 = Solid PEN STYLE (pattern) using the BACKGROUND color 2 = Solid PEN STYLE (pattern) using the FOREGROUND color { VW uses this as the default for SOLID PEN } And then there is that negative value thing to contend with, too. Good luck with all of this, Raymond (Make it confusing once, and it stays confusing forever. I wish I knew who to thank for this 😉 )
  9. MullinRJ

    wall scripts

    murad, Since you are new to scripting, you should try what we all have done to learn by example – draw some objects of interest, then export a script to a text file. The Export options can be found under the File menu. In your case, draw some walls (30 cm thick), with your desired line weight (18 mils?), and add some hatches. After exporting this as a script, you can find the relevant code deep in the middle of the file. Look for the comment "Object Creation Code". That comment will appear several times in the script (at the beginning of object creation, before each layer in the file, and at the end of object creation), but it will get you close. This is a really good way to get your feet wet. Good luck, Raymond
  10. Pity. It's a feature I use all the time. Perhaps another PC user can offer advice to help you. Raymond
  11. Jainsworth, Welcome to the VW Forum. On the Mac, I uncheck the "Use Application Window" menu and I get individual windows for each file. I think you can also tear a TAB away and a new window will be created when you release the mouse button. I can only assume it is the same on the PC. Here's the menu as it is on my Mac. Each time I open a file it opens in a new window with "Use Application Window" unchecked. HTH, Raymond
  12. Gotta run, but I have 1 quick thought and no idea how it will affect viewports. Have you tried ResetObject()? This is a lot of what programming is about when you are learning, and after 30 years scripting with MC/VW I'm still learning. When in doubt, try something, anything, and take notes. Good luck, Raymond
  13. Martin, IFF [sic] you really want to GROK the whole VectorScript experience, you'll have to procure a copy of "Hitchhikers Guide to All Things VectorScript (and Python, too!)." However, it may be a bit easier to download a copy of the SDK from the VW site: http://www.vectorworks.net/support/custom/sdk/sdkdown and look for this file: .../SDK/SDKVW(build#)/SDKLib/Include/Kernel/MiniCadCallBacks.h In it you will find long sloppily typed lists of extremely esoteric and somewhat arcane factoids. When you find yourself standing precisely in Ra's shadow, notice the following illuminations: const short ovViewportXPosition = 1024; // double read only - the X coordinate of the viewport on the sheet layer - Public for VS const short ovViewportYPosition = 1025; // double read only - the Y coordinate of the viewport on the sheet layer - Public for VS That is how I know 😉 If this doesn't help, ... Raymond
  14. Martin, ObjVars 1024 & 1025 are marked as READ-ONLY. Try getting the Bounding Box to find out where it is, then use HMove() to move it to where you want. The difference between the desired point and the existing point is the amount you need to move it. HTH, Raymond
  15. halfcouple, This is an old issue, and I remember answering it before. What I didn't remember was how long ago I posted a response. See this post from 7.5 years ago. Since my post, I added another line to BEEP when the preference is set to TRUE. This lets you hear an audible BEEP when the "Active Plane Menu" gets set to "Screen Plane", and nothing when it gets set to "Layer Plane". Click reduction AND Glance reduction rolled into one. { This script will toggle the "Active Plane Menu" between "Screen Plane" and "Layer Plane", } { and BEEP when "Screen Plane" is active. } { 23 Apr 2011 - Raymond J Mullin } SetPref(1099, not GetPref(1099)); if GetPref(1099) then SysBeep; If the last option in the "Plane Mode" dialog is selected, "Screen Plane or Working Plane", then my script toggles the "Active Plane Menu" between "Screen Plane" and "Working Plane". If anyone needs help turning this into a Menu Command, please write back. HTISH, (Hope This Is Still Helpful), Raymond
  16. I found an old email (GBTML*) with a reference to the Developer Wiki on how to edit a VST to be event-enabled. http://developer.vectorworks.net/index.php?title=VS:vstGetEventInfo Thank Ryan and Conrad for writing this down. Raymond * God Bless the Mailing Lists 🙂
  17. I have run down that dead-end alley, too. Life would be so much more colorful if it did. Thanks, Raymond
  18. Josh, You've got my attention. Thanks. Somewhere I've got a recipe for "using" a Hex Editor. I'll post back when I dig it up. So, in your opinion which is harder, going down this route, or learning the SDK? :-) Raymond
  19. Julian, If you find one, I'd love one, too. Please share. Years ago, when I first looked for the same, I believe I was told it was only achievable with the SDK. I have several tools I have made that would benefit immensely from Mode Buttons. I hope you find an example. Raymond
  20. 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.
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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

 

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.

×
×
  • Create New...