I have no qualms about sending you the code. The code by itself would not be executable though unless I provide several files. The critical ones are a jpg, which is used to fill the initial display area, and two others that have to do with color and making a movie. A minimum of two data files may be needed, but I suspect they could be skipped. If they are necessary, then it's a simple matter of creating an Events folder and putting them there. The py and extra files need to in the same folder. It runs in Py 2.5. I guess the data files would be useful in  the case where one might test the exit when data is viewed. I think I found the same results.

On 2/11/2010 2:27 PM, Peter Milliken wrote:
It does look strange, but with only the code you present we can only make some assumptions i.e. 

self.running = False

implies (to me :-)) that there are likely tasks running and this flag is being used to shut them down?

self.master is presumably the widget derived from the 'standard' line:

root = Tk()

that you normally find in a program? or is self.master some other widget?

Does the class that Quit is a method of inherit from something?

It is pretty hard to work out (on the surface) why this method won't work from the menu.

Peter

On Fri, Feb 12, 2010 at 8:18 AM, Wayne Watson <sierra_mtnv...@sbcglobal.net> wrote:
Just did now and the msg showed up.


On 2/11/2010 10:54 AM, Peter Milliken wrote:
Have you tried putting a print statement in the Quit method to determine if the correct quit is being called?

On Thu, Feb 11, 2010 at 10:14 AM, Wayne Watson <sierra_mtnv...@sbcglobal.net> wrote:
I'm looking a 1800+ line someone else wrote. It uses one large dialog for menus, and has a large area for images. A few menus open small dialogs, for example, to enter a file name. The File menu has an exit choice. The only other exit is the x in the upper right corner of the large dialog. I'm pretty sure that menu is coded to quit via a short def in the program.

def Quit(self)
  self.running = False
  self.master.quit()

I see no other code to quit. If I use Exit(menu item), the program does not quit. If I then use the x, it quits and the shell script is left open for a command. Any ideas why Quit doesn't work in the first case? It's accessible  via a
self.mainMenu.add_command(.. command=self.Quit)
I  had not turned the program loose by using a menu or touching any controls.

If I cause the program to print to the shell, and then use x to exit that it hangs the shell. Why? When I x the shell, it tells me  the prog is running." Do I want to kill it?" Yes, kills the shell  window.

The above seems abnormal to me. Comments?
--
"Crime is way down. War is declining. And that's far from the good news." -- Steven Pinker (and other sources) Why is this true, but yet the media says otherwise? The media knows very well how to manipulate us (see limbic, emotion, $$). -- WTW
_______________________________________________
Tkinter-discuss mailing list
Tkinter-discuss@python.org
http://mail.python.org/mailman/listinfo/tkinter-discuss


--
"Crime is way down. War is declining. And that's far from the good news." -- Steven Pinker (and other sources) Why is this true, but yet the media says otherwise? The media knows very well how to manipulate us (see limbic, emotion, $$). -- WTW


--
"Crime is way down. War is declining. And that's far from the good news." -- Steven Pinker (and other sources) Why is this true, but yet the media says otherwise? The media knows very well how to manipulate us (see limbic, emotion, $$). -- WTW
_______________________________________________
Tkinter-discuss mailing list
Tkinter-discuss@python.org
http://mail.python.org/mailman/listinfo/tkinter-discuss

Reply via email to