code-google-com / pymel

Automatically exported from code.google.com/p/pymel
0 stars 0 forks source link

pymel.core.general.Attribute.isFreeToChange() does not return bool. #269

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Describe the problem.
The pymel.core.general.Attribute.isFreeToChange() method returns a type of 
EnumValue.  The docs say it should return a Attribute.FreeToChangeState object. 
 These may be the same thing.  Is this done intentionally?  I would have 
expected a bool.  An enum value seems overly complex for an isSomething() kind 
of method.  This wouldn't be so bad if the freeToChangeState evaluated to True 
or False, but it doesn't.

What Version of Maya are you using?
2012 64bit

On what operating system? (be as specific as possible and include service
packs, 64bit vs 32bit, etc)
Windows 7 64bit

What Version of PyMEL are you using?
1.0.3

What is the expected output? What do you see instead?

If possible, provide a few lines of code to reproduce the problem. It helps
us if your code will reproduce the problem from a new scene.

myGroup = group()
myGroup.t.lock()

#Always evaluates to true.
if myGroup.t.isFreeToChange():
    print 'it is free'
else:
    print 'it is not free'

#This is how I actually need to access it right now.
#This is especially obtuse because 1) it does not support indexing and 2) the 
true-false values are reversed
if not myGroup.t.isFreeToChange().index:
    print 'it is free'
else:
    print 'it is not free'

Does maya.cmds exhibit the same problem?

Please provide any additional information below.
On a side note, is this the correct place to submit questions like this?  In 
this case it might be a mistake with the code base, or it could be a design 
decision that I don't understand.  I'd rather engage in a meaningful discussion 
with someone on the subject than send a bunch of informal issue reports.  
Especially if I've just misunderstood a concept.  I don't want to annoy anyone 
or over use my issue-submitting privileged.

Original issue reported on code.google.com by assumpti...@gmail.com on 8 Feb 2012 at 1:41