[Meshlab-devel] problem with dynamic float parameter and filter scripts

[Oscar B. <Osc...@Tu...>]

Hey Paolo,

i have noticed that if a filter uses the dynamic float parameter and you
choose to preview that it adds all the previewed things to the
filterHistory.actionList which then basically makes the filtercript you
are trying to build useless.  I have coded a quick fix for this by
changing the executeFilter function in MainWindowInterface to have a
bool telling it whether to add to the filterHistory or not.  This seems
to me like the simplest way to solve the problem given the current
design.  However, maybe there is a design change that would also solve
the problem.  Let me know what you think or if i should check in this
simple fix.

Also, I am now done with my Select Face by Color filter.  I made a
change to it that allows the user to preview the selection and how it
changes when they adjust the variance from the color they want to match.
This requires that I save the selection to the MeshModelState.  I
created the key: MeshModel::MM_FACESELECT and added appropriate code to
the MeshModelState class.  Does this make sense or should i have used
one of the existing ones like MM_FACEMARK?

thanks again!

Oscar