[Bf-python] nmesh.getMode() nmesh.setMode : inconsistent !

[Gert De Roost]

There seems to be a blatant inconsistency in the
format of the nmesh.getMode() and nmesh.setMode()
methods.

The first returns an OR'ed flag while the second takes
multiple strings as an argument.

When, for example, you want to turn off Optimal mode
if it is turned on,  you need to read the OR'ed flag,
check for the Optimal flag, read every other bit, see
if it's turned on, assign the corresponding string (to
feed into setMode()) to a string variable (which you
need to put back to "" every time you call this
subroutine) and then feed all those strings into
setMode().  

This really should be: getMode() OR'ed flag, put
Optimal bit to 0, feed new flag into setMode().

or:

getMode() modes-list-consisting-of-strings, pop the
optimal string if it's there, feed new list into
setMode().

So both methods should either use lists of strings or
OR'ed flags for consistency.

Please do sacrifice backward-compatibility to correct
this.

.gert.




		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com