karstenwolfGL

Our workflow is entirely Layer plane based so I have very limited experience with screen plane workflows. An issue I'm getting stuck on right now seems to involve the screen plane. I have a plugin that has 2D text and Polylines as well as 3d geometry using vs.BeginXtrd, vs.Symbol, and vs.SymbolToGroup. This works great, Text and 2D polylines show only in Top/Plan and 3D geometry only shows in 3D. I'm now going through and removing the need for the symbols by trying to model them instead. Once I add the following lines all my 2D objects become screen planar and show in 3D views; as well as all my 3D objects show in top/plan. vs.Oval(-12,12,12,-12) vs.CreateTaperedExtrude(vs.LNewObj(), 15, 9) vs.SetPlanarRef(vs.LNewObj(), -1) If I try the same lines with vs.CreatTaperedExtrd2, the 2D objects don't become Screen Planar, but the newly created tapered extrude is visible in 2D top/plan without vs.SetPlanarRef. Any guidance on what's going on and how to work around it without needing to effectively use/test vs.SetPlanarRef on every 3D object?

Thanks exactly the information I needed, this is working now.

I have a linear Object Plug-in which effectively draws a nurbs curve at the length. What I'm not able to figure out is that I want to be able to pass a calculated value back into the OIP as a StaticText(?) which updates when a parameter is changed or the line control points are dragged. Basically a functioning version of this: vs.vsoAppendParamWidget(13, 1000, "Value: ", VARIABLE) I'm at a little bit of a loss as to how to do that and I'm missing something about how the OIP works. It seems like the guide I need to copy and then the vague steps are below? Is that the right direction? I don't think I need to make the calculated variable a parameter, just updating the text should be fine since it's just as a user reference. https://developer.vectorworks.net/index.php/User:CBM-c-/Plug-in_with_widget_basic_example 1. Set the OIP to be customizable 2. Draw all the 'default' fields 3. Add a widget with the new calculated value. 4. The above link's code handles the 'listening for changes' part and 'redraws' the OIP on changes.

I think there's room for improvement in the video screen tool, specifically in the PJLens parameter. Currently it's a drop down with an incomplete assortment of lens ranges with no reference to manufacturer or other lens specs (specifically missing any ultra short lensing). On smaller screens this list is too long to ever be useful. At 1080p you need to scroll to get to 'custom' at the bottom. I think a nice feature would be to have a manufacturer tag and a lens series tag somewhere in the projector model's symbol so that when you select a Christie M series, it only lists lenses which exist for that model. You could even work with manufacturers to get some of their lens calculator functionality to throw up errors when you're outside of the focus range, etc. You'd also have a check mark options to 'use generic lens' or 'enable manufacturer lens only'. Maybe even add support for mirror lensing? Great. Second but related request, please make the PJlens list user editable within the plugin manager. I want to be able to add/remove so the list is just lensing that I use and THEN use the custom as needed. Right now my default workflow when I'm setting it to be based on lens instead of distance is to use custom after scrolling all then way at the bottom and skipping the list entirely.

It would be helpful to be able to pull images or PDF pages out of a file in it's original format. I reuse old files and being able to edit or convert image/PDF assets that have been dropped into old files would be helpful.