well, one approach could be to have the button attached to a single callback that checks state and calls one of three functions based on the state:

Python Syntax (Toggle Plain Text)

 
def callback(self):
 
  commands = [self.myfunc1, self.myfunc2, self.myfunc3]
  commands[self.mydata]()

def callback(self): commands = [self.myfunc1, self.myfunc2, self.myfunc3] commands[self.mydata]()

commands is then a jump table that gets you to the right function.

You could lambda-ize that solution as well, like this:

Python Syntax (Toggle Plain Text)

self.commands = [self.myfunc1, self.myfunc2, self.myfunc3]
 
self.b = Button(self, ..., command=lambda :self.commands[self.mydata]())

self.commands = [self.myfunc1, self.myfunc2, self.myfunc3] self.b = Button(self, ..., command=lambda :self.commands[self.mydata]())

But that latter solution won't work if the callback has to extract info from self in order to find out which function to call.

Jeff

I have addressed this problem sometime ago; I have either misplaced, misunderstood, or never received a response to this issue so therefore I am again attempting to deal with a Python issue:

I am towards the end of a build, and I am dealing with button commands, something that was not necessary to finalize in the program until this point. I need to either:

• Code one button widget to allow multiple command arguments, that is, the same button is capable of issuing unique event commands at different points
• Or, I need to be able to destroy or delete the said button so I am able to reload and redisplay it bound to a single, unique command (example: only one button is seemingly displayed from the user's point-of-view, but it is actually 3, seperate "buttons" that perform 3, unique command events.) This does not seem to be the method to use, but unless I can determine a cleaner method such as one button with multiple command references allowed, I see no other way at this point.

~Thank-you in advance for any responses\ ideas

sharky_machine

I believe that what is happening is that btn1 is being set to the first instance of Button, which is then packed (I prefer 'grid', BTW). Then btn1 is set to the second instance of Button, which is also packed. The reference to the first Button is then lost; your code has no way of accessing it, even though Tk continues to maintain a reference to it on its parent frame.

I don't know why pack.forget() doesn't fix that problem.

But if I understand your intent correctly, you want to switch out the button text and image, but not the button itself, yes?

One possibility is to use a textvariable for the Button rather than static text. It might also be possible to change the image on the fly.

See http://infohost.nmt.edu/tcc/help/pubs/tkinter.pdf for info on using textvariable.

Sorry for the partial solution; hope it helps.
Jeff

The game sounds really cool. See if this is what you're after:

[php]
from Tkinter import *
import random

class MyFrame(Frame):

def __init__(self, master):
Frame.__init__(self, master)
self.buttons = [Button(self, text="1", command=self.switch), \
Button(self, text="2", command=self.switch), \
Button(self, text="3", command=self.switch)]
self.b = random.choice(self.buttons)
self.b.grid()
self.grid()

def switch(self):
self.b.grid_remove()
self.b = random.choice(self.buttons)
self.b.grid()

mainw = Tk()
mainw.frame = MyFrame(mainw)
mainw.mainloop()
[/php]
This allows the user to randomly switch amongst three different buttons. Yours wouldn't be random, of course.

So about the game: if the user hits the button, he gets three cards automatically? I was at first picturing the user hitting the 'Hit' button as many times as he might want, until he busts or wins. But from your description, I'm not sure.

Jeff

I have addressed this problem sometime ago; I have either misplaced, misunderstood, or never received a response to this issue so therefore I am again attempting to deal with a Python issue:

I am towards the end of a build, and I am dealing with button commands, something that was not necessary to finalize in the program until this point. I need to either:

• Code one button widget to allow multiple command arguments, that is, the same button is capable of issuing unique event commands at different points
• Or, I need to be able to destroy or delete the said button so I am able to reload and redisplay it bound to a single, unique command (example: only one button is seemingly displayed from the user's point-of-view, but it is actually 3, seperate "buttons" that perform 3, unique command events.) This does not seem to be the method to use, but unless I can determine a cleaner method such as one button with multiple command references allowed, I see no other way at this point.

~Thank-you in advance for any responses\ ideas

sharky_machine