IS there any lscript programmer here that can help me out please

mis

New member
Hey guys n girls

Ime looking for someone here who is into lscripting
for a small script, so if anyone have the time and want to help
i would like to hear from you

BEst regards

Mis
 

mis

New member
well ime not a programmer and ive been doing some searching but my brain seems not to be helping :/

when i model especialy with subpatching i use Connect alot
connect between points and edges and polygons

the problem is if i select points and then connect, the points is still selected so i need to deselect them
after i have connected each time, Very anoying
same goes for polygons.
edges deselect fine

so ime thinking if someone could make a small lscript or somthing
that could call the two internal modeler commands
so first Connect and after that deselect some how
so i can put that on a shortcut insted of the standart connect.

Making any sense ?
 

evenflcw

Code Muppet
Do file a feature request anyway (NT seldom consider workflow issues actual bugs if past reports are anything to go by). That selection remains for such an operation goes against what I would claim to be the standard behaviour/workflow in Modeler. And I can't figure out a good motivation why it this should be different from the norm.
 
Last edited:

evenflcw

Code Muppet
The only thing one might add to the script is to figure out what selection mode one is in, so you don't clear selection for the mode you are not in*. Some workflows do include storing a selection in one mode for later use, while performing edits in another mode. Which is another workflow issue some kungfu tools have - when you undo them, they don't restore the initial selection.

*This is not readily possible in lscript as there are no statechecks available for selection mode... but you should be able to determine this by checking point/polycount under different modes. Probably lots of gotchas doing that though.
 
Last edited:

mis

New member
Well thing is right now as a hobbyist i dont have the money to update to lw 11 :(
so if i filed it and they made it i wouldnt get it but for future
and for helping others yes it might be a good ideer.

Ime though not experienced in filing stuff
What do i do to do so ?
 

probiner

Fȯrum Mole
evenflcw what about "Drop Current Selection" command? It doesn't mess with the selection in other modes, just the current one.

Though if tools start to evolve by defining axis and origins with secondary selections there it is again.
 
Last edited:

evenflcw

Code Muppet
Can't find "Drop Current Selection" in list of callable commands, unfortunately. I think some guy on the forum might have provided an lscript library (c compiled using sdk) that provides the state of the current selection mode. The drawback is that, being c compiled, this library is not platform independent, as the lscript is. But with python now available and shaped after the sdk, the current selmode should be possible to query from platform independent non-compiled code. So either one codes the whole thing in python, or just the query part (execute the python script from lscript which write selmode status to file and then read it from the lscript). Not as neat as a proper lscript library, but it is possible without compiling anything.

Don't quote me on this... I'm only assuming it's possible to check selection mode in python, as it is from c-sdk, and the former takes after the later. It might not have been implemented yet, for all I know.
 

evenflcw

Code Muppet
Erikals... the problem is that connect works in both point and polygon selection mode and from lscript there is no direct or easy way to determine what mode you are in. You want to call either selpolygon(CLEAR) or selpoint(CLEAR), not both, depending on what the selection mode is. For the most part (probably 95%) Nickdigitals script is fine though and few will be bothered by both being called. I'm perhaps just nitpicking (about his script, not about the original tools behaviour).
 
Last edited:

nickdigital

New member
@evenflcw

I thought about the selection check as I did see that this would bork what someone has selected in another mode. Unfortunately I doubt I'll get to it. I'm better with Layout in lscript than Modeler and free time is a rarity right now If someone wants to take it and run with it then by all means go for it.

Trying to address mis' challenge was a 10 minute lscript challenge for me. :)
 

nickdigital

New member
A hack workaround would be to clone the script and remove the code that clears the specific selection. Then you can have one for points and one for polygons. But then you have multiple tools when ideally it should just be one.
 

mis

New member
well i can see how to some the deselecting of all selections could be hmmmm
but to me its really not a problem as it is now
however making it in python would only make it lw 11 compatible right
then all other lw versions wouldnt have any use of the script
wich would be sad
 

mis

New member
OKay i used it for a project today and its really great though theres one tricky bit with it
cause it release both points an polys, and by doing that
it shifts to polys each time its used
also if ime in point mode
so i need to change back to point mode each time hmmmm
 
Top Bottom