VectorGeek

Is there any way to suppress the "Properties" dialog box when a plug-in object is first inserted in a file? V-G.

Looks like this is not possible with Control Points as the parameter name is not editable... Any tricks? V-G.

Brilliant! Many thanks Josh. V-G.

So, SetParameterVisibility() works great, however the first time an object is placed, when the "Object Properties" opens, all of the hidden parameters are visible. Not a deal-breaker, but I'd prefer they were hidden always. Is there a way to do this? Thanks! V-G.

Ray, Miguel, Kevin: Thanks for the feedback. I think Kevin has it - it's related to Developer Mode. Of course that's how we do all our testing, but the users never turn it on. That's why I was seeing inconsistent results! Cheers. V-G.

Thanks Hippo. So "IsNewCustomObject" is really useless then, because the second time, the object isn't new? V-G.

Hi friends: I just realized while debugging a script that this procedure generates both a message and an alert dialog. In other words, IsNewCustomObject is not working because the code appears to execute twice during object placement. So the first time, IsNewCustomObject is TRUE, then it's FALSE, all during a single placement of a PIO. I recall Miguel posting something about this, but I'm at a loss to understand is this is truly what is happening. If this is true (running code twice), is the IsNewCustomObject procedure of any use? Thanks!!! V_G. IF IsNewCustomObject(myName) = true THEN BEGIN iullength := pullength; iulthick := pulthick; cp01X := itotalrun + iullength; cp01Y := itotalrise - iulthick; SetRField(myHand,myName,'CONTROLPOINT01X',Num2StrF(cp01X)); SetRField(myHand,myName,'CONTROLPOINT01Y',Num2StrF(cp01Y)); Message('I'm New'); END ELSE BEGIN cp01X := itotalrun + iullength; cp01Y := itotalrise - iulthick; SetRField(myHand,myName,'CONTROLPOINT01X',Num2StrF(cp01X)); SetRField(myHand,myName,'CONTROLPOINT01Y',Num2StrF(cp01Y)); alrtdialog('1234'); END;

IMO, there is a high level problem with the GSG and that is, quite simply, it's not teaching or training, it's "follow the bouncing ball". In other words - you need to add context. "How to do it" is not nearly as important as "Why am I doing it?". Think of the best teacher you ever had - I would contend that he/she made the information you were expected to learn pertinent, and that they gave relevant, contextual background. That's how one learns. For example: You can make a video and have the viewer add some classes, however if they don't understand classes conceptually, they are just repeating steps. By simply explaining (in short form) how VectorWorks uses classes (and how that might compare with other software paradigms), the viewer gains insight rather that just learning how to do something, but not know why they are doing it. If the context is discipline-specific, even better. Not an easy task, but there are many training options for other software that succeed in this sense. Namasté, V-G.

Dexie: There is a way, but it requires an extra cell. Assuming you have the value 2.29803 (or any value between 0-10) Create a cell with the formula: =ROUND(D8*100)/100 That will round the value to two decimal places Now base your calculations on the value in this new cell. Math is fun, english is funner! V-G.

Dexie: This is happening because of rounding. You are rounding cell D27 to two decimal places, so 2.29803 is becoming 2.30. Vectorworks is using the actual number (2.29803) and calculating the correct answer: 43692 / 2.29803 = 19012.81 (rounded to 19013). In your example above, you are truncating the value to 2.30 and getting a (slightly) different result, which is expected. Hope that helps, The Geek.

Bumping this in case anyone knows how to do this. In essence, I have files with numerous referenced design layer viewports. I'm trying to find a way to control layer visibility within multiple viewports using VS. Help!!!!! Thx. V-G

Hey Y'all: Digging 2016 so far but have one problem. My customized .VSO and .VSM files are showing up as expected in the Plug-in Manager under the "Custom Plug-ins" tab. However my custom .VST files are under the "Third-party Plug-ins" tab, and the Properties cannot be edited (all greyed out). Anyone else seeing this - and know of a fix? Thanks!

Anybody running VW 2013 on El Capitane? Problems? Issues? Unexpected results? Many thanks and blessings from the 4th dimension, VectorGeek -------------------- iMac i7 VW2013 1976 AMC Gremlin, tinted windows, fuzzy dice, pure V8 power

Thanks Kevin. That would be great if you could get the peoper layer name syntax back to me. The curious thing is, the line: SetVPLayerVisibility(h,GetLayerByName('green layer'),-1); is returning TRUE. If the layer name was wrong , would you not expect that function to return FALSE? V-G.

Just wanted to take a quick moment to pass on some kudos to Jim Wilson for the great efforts he makes to support users through this community board. I think I speak for all of us (particularly the longer-time VW users) who appreciate his timely and thoughtful responses, and his general helpfulness to beginners and experts alike. It speaks volumes for NVW as a company to have someone of Jim's abilities dedicated to providing direct connection with the user base. Well done Jim! V-G (for the record, not related to Jim whatsoever)

Hey Kevin, Thanks for pointing this out. I did some further testing and determined that where it fails is if the design layer viewport is referenced from an external file. Handle attachment works fine, but the layer/class controls (SetVPLayerVisibility, for example) cease to function properly. To test, just "Save As..." the file I posted and create a new DLVP that is referenced. V-G.

Hey Kevin, Thanks for the quick reponse. It should work as you say, but it doesn't. Sheet Layer Viewports work fine and return 122. Design Layer Viewports return 86 (PIO). Attached is a sample file that you can see the behaviour in. I know 86 is wrong because there are no PIOs in the file, just colored rectangles. Please advise if this is a bug or if there is a workaround. Thanks. V-G.

Does anybody have a clue as to why Design Layer Viewports return a type of "86" (Plug-in Object)? I am looking for a way to control the layer and class visibility inside design layer viewports using VS. But since they don't return a correct type, the following functions won't work: GetVPLayerVisibility SetVPLayerVisibility GetVPClassVisibility SetVPClassVisibility etc. etc. Any tricks? Thanks! V-G.

Hey Benson: We use Jing (www.techsmith.com/jing.html). Works all day long and should do what you need. V-G. President VectorGeek Enterprises "average is our middle name, even though we don't have a middle name."

So Josh, when you were tracing over the referenced CAD file, were you snapping to the given objects, or were you freehand drawing? If the latter, it's pretty much impossible (without a grid constraint on) to get anything other than what you got. You would be far better to work with a grid snap of 1/4" (or whatever your preferred tolerance abased on the form of construction was), or else draw over top by moving object empirically and/or using data input, using the referenced file as a base. I'll often do this, by greying out the background info and working without snap to other layers on. I hate dirty data, and as you found out, so do consultants. HTH, VG.

I agree with Jim. The report was intended to either incite a heated discussion/flame war, or to educate us. I hope it's that latter. So fill us in. And I have done my Revit homework, thoroughly. So no BS.

Just checked here Kevin and it seems to be working. I tried as is, then updated Adobe Air to 4.0.0.1390 and all works as expected. Cheers. V-G

Doesn't the new colour management system in the Attributes Palette provide this (similar) functionality? V-G.

Been that way since I started (MC+4, circa 1993). For sure an annoyance, and something that should be a doc pref. I like to start jobs by setting my Page Setup and then laying out with page boundary on in design layers. Helps determine extent without having to make VPs and sheet layers right away. Once I know the right combo of scale and sheet size, I turn it off from then on. V-G MiniCAD 2013, 2014 Mac OS Ex

And to add: VW2014 is an upgrade, not an update. In other words, you have to pay for it. V-G --------------------------- VW2013, VW2014 Mac OS X With a big "shout out" to the NSA who is likely reading this forum.