cmdseq or method for "Expand Selection"?

[zuzzabuzz]

Hi folks,

I'm trying to add an option to "Select Sides" for this greeble lscript I'm trying to make. I basically want to perform a bevel, and be able to select the newly created sides. The easiest way I can think of is to "Select Tops" (the poly's I'd already beveled) and then execute an "Expand Selection" command to get the beveled sides. Not sure how to do this with lscript though.
Thanks.

[evenflcw]

Maybe you could do this instead. The newly created polygons were the last created polygons, hence their indeces (numbers ranging from 1 and up in order of creation) are also the highest. All you would need to do then is compare the global polycount before and after the bevel operation. The newly created polygons will be "in the difference" of those polycounts. Just create an array with those indeces (first polycount -> second polycount) and use selpolygon() to select.

[zuzzabuzz]

Not a bad idea! I'll test it to see how reliable it is.
I had a second thought last night that I could also change the surface before extrusion to something unique "999 !$! Surface", then select by surface to add to selection array, and change surface back to something "normal" Then, maybe I can delete the surface.

thanks.

[MentalFish]

Sorry to resurrect yet another old thread, but I though it would be useful to post a solution to this problem for others to find. These works:

cmdseq("Select Expand");
cmdseq("Select Contract");

I was about to write my own LScript to do this but did some last minute testing of various names. Swapping "Selection" and "Expand", with or without space between them and so on. And viola, it actually exist :)

Edit: Is there a place where we can get documentation on any (preferably all) cmdseq-able plugins and their options we can feed them?
I.E. the OBJ exporter can be given a path to export to:
cmdseq("ExportOBJ","path/to/test.obj");
While others don't accept any input parameters, such as the FBX exporter (which just opens the requester when called through cmdseq)
Time to sort this stuff out? :)

[evenflcw]

The best place too see what is callable (a meshdataedit/commandsequence plugin) and by what name to call them is in the LWEXT*.cfg file. It contains a list of all installed plugins. The infotags seem to correspond to the server/info-tags listed in the server.html sdk docs. Perhaps some of them reveal possible arguments, but I doubt it.

[MentalFish]

Thanks, that will help! Don't need to guesstimate so much.