AlanW Posted January 9, 2016 Share Posted January 9, 2016 When DomC & Pat explained how Control Geometry worked it made me think about the resultant OIP and the sorting. It seems that if you want your named nodes to show up in the top of your list try sending the node to the back in the script. This appears to move them up the list. Not always sometimes they seem to swap each other but seems to get a semblance of order to your liking. Any others find a better way to order the list. Quote Link to comment
DomC Posted January 9, 2016 Share Posted January 9, 2016 The Order is 1. Back, 2. Top, first connection, left. Or something like this. I don't know exactly. But: A Number as a suffix, will overdrive the order. I tried this, but not sure if this works stable. Quote Link to comment
Jeremy Best Posted January 18, 2016 Share Posted January 18, 2016 In the - 6 they cover the following: If you put a numeral at the start of the name for the field or variable in the OIP, it will order be ordered according to that number. The number itself will - by design - be omitted. i.e. Naming (for example) a Real Integer node "1Width" will put it at the top of the OIP. It will appear as "Width" Is that what you were asking how to do? Quote Link to comment
Carles Olle Posted October 21, 2016 Share Posted October 21, 2016 after 9 the numbering seems to fail (the script produces errors) Quote Link to comment
Kevin McAllister Posted October 21, 2016 Share Posted October 21, 2016 In my experience its definitely not stable though I haven't tested it very much in VW2017. @MarissaFwas going to look into this and whether its officially supported as an approach to re-ordering OIP fields. It came up in another thread. Kevin Quote Link to comment
Marionette Maven Marissa Farrell Posted October 21, 2016 Marionette Maven Share Posted October 21, 2016 I haven't really gotten a final say on what state it is in, but as for the numbering not working past 9, try going through the alphabet instead of 10. so ... 7, 8, 9, A, B, C, ... Can't promise that will be the solution, but it may be the logic they've used on the back end secret to me. I still don't bother using it, and although I hate suggesting you don't as well, if you run into things like this the only thing we can do is wait to see if it gets accepted as a bug or not. Quote Link to comment
Kevin McAllister Posted October 21, 2016 Share Posted October 21, 2016 Thanks Marissa. I'm not using it either. Its a bit of a weird situation since as far as I am aware there still isn't real documentation for Marionette. The Introductory videos and the Marionette Monday videos are essentially filling that gap and this "feature" is included in them. (I couldn't actually confirm what the VW help says about Marionette since help doesn't work on a Mac with Safari 10 at the moment.) Kevin Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted October 21, 2016 Vectorworks, Inc Employee Share Posted October 21, 2016 16 minutes ago, Kevin McAllister said: (I couldn't actually confirm what the VW help says about Marionette since help doesn't work on a Mac with Safari 10 at the moment. Make sure to use Chrome or Firefox for the time being, it is unlikely Apple will be fixing that issue in a timely manner. Quote Link to comment
the frog Posted November 11, 2016 Share Posted November 11, 2016 hello all we had this topic a long time ago This is the way counts works "if you have a number in the name it can bug. If you pass 9 the next digit is A than B (=11) etc up to F. We are on an hexadecimal base." I never tried after F guess it should be 1A, that would put 16 infos in the box not counting textures options that are ordered immediately after the texture name hope it helps Quote Link to comment
Vectorworks, Inc Employee Stephan Moenninghoff Posted January 11, 2017 Vectorworks, Inc Employee Share Posted January 11, 2017 @the frog can you explain how you did this successfully? I cannot get this to work. I use 0 to 9 and then what? A? What about labels starting with A? How does Marionette know that my "A" is not part of a label? Thanks! Quote Link to comment
Vectorworks, Inc Employee Stephan Moenninghoff Posted January 15, 2017 Vectorworks, Inc Employee Share Posted January 15, 2017 OK, I got it. What you do is: 0_0 0_1 ... 0_9 1_0 1_1 ...etc. That's it. No Letters. @MarissaF@sbarrett not sure if this has been documented yet? This thread hasn't been updated in a while and I couldn't find this information anywhere. 1 Quote Link to comment
DomC Posted January 15, 2017 Share Posted January 15, 2017 Very nice, thanks for figuring out that ... Quote Link to comment
Marionette Maven Marissa Farrell Posted January 16, 2017 Marionette Maven Share Posted January 16, 2017 @Stephan Moenninghoff I believe we've been holding off on documenting it because in some cases we've encountered it not being very reliable. I'm sure if we keep seeing it not fail that we can get it into documentation - it's more of a 'hidden bonus feature' currently. Quote Link to comment
Nico Vindevogel Posted March 5, 2017 Share Posted March 5, 2017 Prefixing the imput nodes to sort oip does not work as it belongs for me. If you create a simple box with a width of 600. Then you insert the box into the drawing and change the width to 400. You copy paste a new insance of the box and you get a box of 600 wide again. While you want a box of 400. (600 is used when the network is wrapped) To sort the oip I use following method. First I place all my input fields in an ordered list, then i use immediately a list explode node. To wrap the network you have to right click on the list explode node and NOT on just a node you preffer. @Stephan Moenninghoff Can you post an example how to use te seperator? I see in the pic above you figured it out... Thx Quote Link to comment
Vectorworks, Inc Employee Stephan Moenninghoff Posted March 13, 2017 Vectorworks, Inc Employee Share Posted March 13, 2017 Hi @Nico VindevogelI'll post a new project when I have it ready, still working on it. In the mean time, do this: Just hook the separator up anywhere in the network, I don't think its position matters. I have wired it to a node near the end though so it does not get lost in the network. Combined with the right sorting (see above) you should pretty much get the result I had. HTH. Quote Link to comment
Nico Vindevogel Posted March 18, 2017 Share Posted March 18, 2017 Hello, @Stephan Moenninghoff Figured it out. See node attached. I use it in a ordered list to place it on the right spot. Seperator.vwx Quote Link to comment
DomC Posted October 5, 2017 Share Posted October 5, 2017 (edited) Hi 0_1, 0_2 ... seems not to work not the same in 2018. The Number after the unterscore is now part of the name. I made some test and best input-sorting-workflow for me seems to work with a three-digit number. Also seems to be an efficient workflow to use a worksheet for node (re)-naming. Edited October 5, 2017 by DomC Quote Link to comment
Vectorworks, Inc Employee Stephan Moenninghoff Posted October 5, 2017 Vectorworks, Inc Employee Share Posted October 5, 2017 Thanks, @DomCfor the heads up! This is some very interesting news. Sorry, from your screen shot I cannot really infer the logic of the new, revised sorting. Is it as simple as 001 to 999? Quote Link to comment
DomC Posted October 6, 2017 Share Posted October 6, 2017 @Stephan Moenninghoff Äh, yeah. In previous Versions numbers over 9 did not work. So we avoid by numbering with 1_1 1_2 3_3 or 7, 8, 9, A, B, C etc. Now for me it seems we can just take a Number to sort. It will be not so clever to sort like 1,2,3,4 ... 12,13,14,15. So I just sorted with 100 200 300 400 500 600 The Main-Positions or the seperators. And Sup-Positions with 110 120 130 140. And there is always enought space to push some new inputs between the existing inputs. Looks perfectly for my now. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.