• Content count

  • Joined

  • Last visited

Community Reputation

30 Great


About MullinRJ

  • Rank
    1000 Club

Personal Information

  • Occupation
    Circuit Board Designer
  • Location
    Dallas, TX

Recent Profile Visitors

638 profile views
  1. There is also ResetBBox(handle2SymbolPlacedInYourPIO). I've used this successfully OUTSIDE a PIO to get updated text to display. No promises, but worth a try. Raymond
  2. PS - Also try setting the fill colors to something other than WHITE. It may make it easier to spot when it does get applied.
  3. Sam, Have you tried SetFPat()? This will override the document setting for Fill_Pattern. TextOrigin(0,0); CreateText(concat(distbase, CHR(39))); SetFPat(LNewObj, 1); { sets fill pattern to solid background, which uses the background fill color } or SetFPat(LNewObj, 2); { sets fill pattern to solid foreground, which uses the foreground fill color } HTH, Raymond
  4. Jim, I want to thank you personally for handling ALL of the advance Teasers, for being the Messenger, and the Dart Board. It is a job extremely well done. You are truly a multifaceted vortex of talent and responsibility. There is no way anybody will know what is on the table before them until AFTER they have supped. May you survive the meal until the dessert plates are cleared. VW 2018's design blended with current technology is a gift to any user who understands the value of a custom tool he or she helped influence, and though I haven't tried most of what is offered, I am thoroughly impressed with the Multiple View Panes, the Unicode implementation, and Plug-In Styles. Multiple View Panes is flashy and everybody will see it in action and understand it right out of the box. The Unicode handling is much more subtle. It will take people longer to appreciate it, but it will be one of the first things they will miss when they try to use older versions of VW. Plug-In Styles may be tricky for some to grasp at first, but it is an excellent way for VW to organize a huge volume of design differences for each manufacturer's library. This approach to managing resources revolutionizes how VW users will handle many large catalogs from an ever expanding source of suppliers. Congratulation to you and all your co-workers. It's time to take a deep breath and relax for 5 minutes. See you at the Summit, Raymond :-)
  5. I am not the expert you are looking for, but when I used the PL tool everything was good until I made a mistake. Trying to remove a vertex an add one back was so unintuitive (it was an Arc vertex) that I did better by drawing lines and arcs, composing them, then converting the polyline into a PL object. I'd like a lesson on how to enter and modify data for this tool, too. Raymond
  6. Now it's official. You two are bound by Script-ure. ;-)
  7. Oh, but it IS a "script order factory", and the chefs are lined up at their keyboards. You'd be amazed what you can get with a "please" and "thank you" around here. Right Pat? and Mike? and Wasn'tISam? This place isn't even the right place. If you want some real attention try posting questions in the VectorScript or Python fora. ;-) Raymond
  8. Gadzooks, With the Symbol Insertion tool selected, make sure your symbol insertion mode is set to "Insertion Point" (fourth button in its group). It can be toggled, intentionally or inadvertently, by pressing the "O" key when the Symbol Insertion tool is active. HTH, Raymond
  9. Sam, Can you post some sample code? This is not something I want to mock up from scratch to investigate. Off the top of my head, I don't know if it can be done. It's been a while since I built a List Box and I don't remember what it did or where it is. Maybe I'm suppressing some painful memory, or maybe I'm just getting old. Raymond
  10. You're welcome, That works, too. And, it's better written. I hope you'll keep trying your hand at scripting. It's a great tool and makes VW extremely powerful. If you get stuck with anything, post your questions here. This forum is incredibly helpful. Hope to see around. Raymond
  11. Hello Marc, There are two problems. First, you have an extra "END" in the middle of the program that needs to be removed. Second, when you make individual references to the handles in your array you need to add a subscript to indicate which one you want. Eg. where you have MyH := h; you should have MyH[index] := h;. I marked these below. Make these changes and it will work. HTH, Raymond PS - Your code may be indented on your computer, but the example above is not. If it isn't, doing so will help you see mismatched BEGIN/END's more easily. Procedure Individual_Scale; VAR x,y: REAL; h: HANDLE; i,j: INTEGER; MyH: DYNARRAY [] OF HANDLE; BEGIN x:=RealDialog ( 'Skalierungsfaktor','0.5'); y:=x; h:=ActLayer; j:=NumSObj(h); ALLOCATE MyH[1..j]; h:=FSActLayer; FOR i:=1 TO j DO BEGIN MyH[i]:=h; { need array reference [i] } h:=NextSObj(h); END; { END; <= this END shoud not be here. Remove it. } DselectAll; FOR i:=1 TO j DO BEGIN SetSelect(MyH[i]); { need array reference [i] } Scale(x,y); SetDSelect(MyH[i]); { need array reference [i] } END; FOR i:=1 TO j DO BEGIN SetSelect(MyH[i]); { need array reference [i] } END; END; RUN (Individual_Scale);
  12. Pat, I believe an extra blank line at the end is only needed when you are using $INCLUDE files, and the blank line ensures adjacent files don't create a syntax error when all the text is merged together. I pasted your code into a text file with the file terminating right after the last semicolon and it ran perfectly with menu item "Run Script..." and also with the "Text File... CMD-5" option in the VectorScript Editor. I can only assume @cberg copied a little too much, or little too little. Hard to tell w/o the error message. Raymond
  13. In the Mac's System Prefs > Accessibility > Zoom, check the "Use scroll gesture with modifier keys to zoom:" checkbox and choose one of the 3 modifier keys. When you hold that key down and roll the mouse wheel your screen will zoom about the cursor. I use the the Control Key, since VW uses the Option Key on the Mac for almost everything. This is a HUGE saver on aging eyesight and a lot cheaper than those fancy goggles. 8-) Raymond
  14. Mark, You could also script a tool that would place a symbol where you click, then move it in the vertical direction to a 100 mm elevation. Raymond
  15. Gentlemen, Here's a small file with a custom WS function that returns the active layer name to the cell it's placed into. It should simplify having to type the layer name in manually. If you change a layer's name, the function adjusts automatically when the WS is recalculated. If you're like me, and you sometimes use a worksheet to gather info without placing it on the drawing, then all you need to do is change the Active Layer, open the WS resource, and recalculate to get stats from the current active layer. You'll only need one WS resource for this kind of use. If you want to place a WS instance on multiple layers, then the way Michael set it up in his example file (with 1 WS resource for each layer) will work, but you if use the ActiveLyr function from my example you won't have to type the Layer Name into each WS resource. HTH, Raymond WS ActiveLyr.vwx