freeze and selected status in lua
| Case number: | 845813-986981 |
| Topic: | Game: Tools |
| Opened by: | Crashguard303 |
| Status: | Done |
| Assigned: | admin |
| Priority: | 2 |
| Type: | Feature |
| Opened on: | Tuesday, November 3, 2009 - 00:41 |
| Last modified: | Monday, August 22, 2011 - 21:17 |
As we know, we can get several segment informations by the command get_segment_score_part("x",y),
whereas y is the # of the segment, and x the name (or attribute) of the value which should be returned.
So, for example get_segment_score_part("clashing",1) returns the clashing score of segment 1.
My question is, if there is a possibility to get an information, if segment x is locked or frozen.
So, an algorithm for example can store the information in a data array to use transparent masking (combining user selections with those of the script), restore the old selection after executing the script, or (and this is most important at the moment) to skip a frozen segment, because in lua, wiggling a frozen segment leads to a crash in contrast to the regular cookbook.
If not so, consider this as a suggestion.
Just one more question: What does the attribute "other" mean?
regards,
Alex
| Assigned: admin » themarquis |
"Regardless, the issue of the frozen segments crashing foldit in the new interface is a bigger problem that needs to be addressed ... is there a separate issue for this? Can "freeze" just be removed from the new interface? Select provides all the funcitonality of freeze."
So, no freeze-mouse-button?
I'm with you, especially because unfreeze ony unfreezes backbones, but no sidechains.
You have always to defreeze them manually (what a Friemels-Arbeit)
It would be enough, if you have made your selection, that there is a GUI button for freeze/unfreeze selection, and no mouse-button, so the "engine" can be unburdened.
A propos unburdening:
Does it have to be, that when running a script,
the buttons for "rebuild" and all "assign structure"-buttons keep appearing and disappearing?
It's not the primary problem to me that it is disturbing (I just ignore it).
But my scruples are, that this can also create some garbage (just guessing) and slows down the program.
| Assigned: themarquis » admin |
P.S.: I love the new interface, and if it will have full functionality, I would use it all the time.
P.P.S.: Editing posts, as far as there were no answers before editing, would be a nice thing, too.
I agree -- I'm starting to really enjoy the new interface, but it does have a few issues. I'm going to start a new issue for various issues with the new interface -- feel free to add to it.
P.S.:
Forget about the unfreezing sidechains/backbones problem.
It was my fault.
| Topic: Game: Other » Game: Tools |
| Status: Open » Done |
| Type: Question » Feature |
We have it in LUA v2. Done.
![](http://128.95.1.228:8000/tracking_pixel.gif?events=scAdd&f=1111&wdata={"x":12, "y":11}){kind=tracking}
it seems like this might be an issue conflicts between old vs. new interface -- lua scripts really are best run in the interface for a number of reasons, including crash while frozen but also because they use the select method. Running scripts in the old interface can work okay, but if the user needs to select segments before running the script (I addressed this in the newest lua tutorial b/c a lot of folks were confused by this) then it can't be done in the old interface and the script won't operate properly. Also, in the old interface, we can't see the progress of the script where it involves select ("fat" purple segments).
I almost think the lua scripting should be confined to the new interface, but I don't know if folks will agree with me. A lot of people either don't like it or haven't learned how to use it. But then again, most people hven't learned how to use scripts, either!
Regardless, the issue of the frozen segments crashing foldit in the new interface is a bigger problem that needs to be addressed ... is there a separate issue for this? Can "freeze" just be removed from the new interface? Select provides all the funcitonality of freeze.