On Tue, Jun 11, 2013 at 2:00 PM, Jim Mooney wrote:
> On 11 June 2013 05:59, Steven D'Aprano wrote:
>
>> I'm afraid I don't understand what you mean. Second and subsequent inputs? I
>> only see one. Hide the input with dots?
>>
>> Can you copy and paste an example?
>
> That would be a graphic of t
I guess that would be hard on Ben Flinkelstein ;') But I guess I could
still have give_cake = True to be more understandable.
Or keep the program the way it is, use if '' in msg , and sell it to
Guantanamo.
Jim
On 11 June 2013 19:19, Steven D'Aprano wrote:
> On 12/06/13 03:53, Jim Mooney wro
On 12/06/13 03:53, Jim Mooney wrote:
But I do like the idea of using plain old words, like "bad" as a
switch, instead of some inscrutable program-switch ;')
I don't. Trust me on this, you will regret it. As the Zen of Python says, "Explicit
is better than implicit". It may seem like a good i
On Tue, Jun 11, 2013 at 2:33 PM, Jim Mooney wrote:
> On 11 June 2013 01:07, Alan Gauld wrote:
>
>> First you are effectively creating an entire Tkinter app
>> inside popup() each time.
>
> I partially mis-spoke myself. The error was not caused Just by
> creating the app every time, but very oddly
On 11 June 2013 01:07, Alan Gauld wrote:
> First you are effectively creating an entire Tkinter app
> inside popup() each time.
I partially mis-spoke myself. The error was not caused Just by
creating the app every time, but very oddly, by the Combination of
recreating the app and using triple qu
>> First you are effectively creating an entire Tkinter app
>> inside popup() each time.
Actually, that was the source of the error. When I put the app
creation above the function, the dots no longer appeared. As to why,
I'm not even going to try to figure that out ;')
--
Jim
Today is the day th
On 11 June 2013 01:07, Alan Gauld wrote:
>
> First you are effectively creating an entire Tkinter app
> inside popup() each time. That's a pretty heavyweight way
> to generate a messagebox. Have you used the Tkinter
> standard message dialogs?
>
Argh - dumb error. Thanks for pointing that out and
On Tue, Jun 11, 2013 at 2:17 AM, Jim Mooney wrote:
>
> But the Second and subsequent inputs, in Windows, hide the input with
> dots, while the first shows the input, and I can't figure out why. I
> don't change a thing between the first and subsequent calls to input
> except changing the input mes
