Set attribute in callback, with lambda

Question

Trying to figure out how to set a object attribute using a lambda function.

i got a case where i need to set the attribute with a UI callBack, that requires a function object.

was trying something like this but it dosnt work, and gives me a syntax error.

pm.button(command=lambda *args: uvOpts.grid = True)

I think value assignment of a variable inside lambda scope is not possible. Try this link: stackoverflow.com/questions/6282042/… — dpatro
– dpatro, Commented Dec 29, 2013 at 15:41

Community · Accepted Answer · 2017-05-23 11:43:27Z

3

this solves the syntax error (you cannot have a second "=" in pm.button) and works if uvOpts is in the scope.

pm.button(command=lambda *args: setattr(uvOpts, 'grid', True))

to set the object's attribute I'm using setattr, in order to avoid the use of a = symbol in lambda function definition.

I would like to add that if you need to make uvOpts visible inside the lambda scope you may eventually need to make it global, at least at module level (e.g. read the answers in Using global variables in a function other than the one that created them).

edited May 23, 2017 at 11:43

CommunityBot

11 silver badge

answered Dec 29, 2013 at 16:02

furins

5,0581 gold badge42 silver badges58 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

martineau Over a year ago

*args isn't needed, so a simple pm.button(command=lambda: setattr(uvOpts, 'grid', True)) would suffice.

furins Over a year ago

@martineau You are right, but since I don't know if args may be needed for any other reason (the OP may have just simplified his/her question), and in order to let cmcPasserby to identify the minimum change needed to solve the error I kept it. If unneeded, the arguments may be removed. Thanks for highlighting this aspect!

martineau Over a year ago

I would suggest answering questions based solely on their content rather than second-guessing what details the OP might be leaving out.

furins Over a year ago

@martineau I prefer to keep it because I do not want to let the "distract reader" to think that *args is part of the problem. It's just unneeded in the context, but it does not cause harm as well. I should have mentioned in my answer that the argument is unnecessary, you are right, but now there is your comment to state this additional aspect (and this is why I voted up your comment) :).

Collectives™ on Stack Overflow

Set attribute in callback, with lambda

1 Answer 1

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related