Yuku free message boards

Fonte Boa wrote:

---

<<Tweak Slide would not work correctly for single edges and would not work at all for selections of two unconnected vertices. Now fixed.>>

Optigon, it seems the problem isnt all solved.
A single edge can be slide along edge loops and it stops at neighbour edge:
but if you add another edge to the anterior one and slide again, it crosses the neighbour edges and goes beyond it,
with impredicable results...

Okay I fixed this also optimized the code a bit.

GetaVe wrote:

---

I am curious how you know by these crash dumps where the crash occurred, or how to fix it even.

From what I can make out, in FB second crash;

It happened in the geometry window, because of an after effect from a function (I am presuming that is what function_clause means? the clause of the function?) Hmmm, other than that, those stack traces don't really say much (to me), though I guess if I knew what gb_trees, update_1 referred to I would have a better grasp on the situation. gb = geometry.. base? geo-build? trees referring to its actualy 'structure'?

man I am probably way off.

Anyhow! Don't worry about actually answering this question, I am merely thinking out loud.

gb_trees means General Balanced Trees.. and yes, trees are data structures. The balanced part means data made into a gb_tree will be distributed evenly as the tree forks. This means that data from any part of the tree can be looked up in optimal time.

Looking at crash dumps takes a bit of practise, but basically they try and tell you the reason for the crash and the location. Function Clause means that the argument passed into a particular function was not expected (it did not match what should be given as an argument to that function).

The Stack Trace tells us the series of functions that led up to the crash. This info is useful when used together with the description of what led to the crash. So if we look back along the stack trace we can see that something when wrong in the wings_subdiv module in the inc_smooth/4 function. All the tuples in the stack trace are in the form {module,function,arguments}.

So in this case, Wings is crashing when arguments fail to match, and it traces back to {wings_subdiv,inc_smooth,4} while folding over a list {lists,foldl,3} and updating a gb_tree.