On Nov 20, 2005, at 3:27 PM, Bob Ippolito wrote:
>
> On Nov 20, 2005, at 2:47 PM, Jon Rosebaugh wrote:
>
>> On 11/20/05, Brian Lenihan <[EMAIL PROTECTED]> wrote:
>>> I'm not sure really why this happens. I work around it using
>>> something
>>> like this in the initialization code:
>>>
>>> if
On Nov 20, 2005, at 2:47 PM, Jon Rosebaugh wrote:
> On 11/20/05, Brian Lenihan <[EMAIL PROTECTED]> wrote:
>> I'm not sure really why this happens. I work around it using
>> something
>> like this in the initialization code:
>>
>> if hasattr(sys, 'frozen'):
>> app.top.tk.call('console'
On 11/20/05, Brian Lenihan <[EMAIL PROTECTED]> wrote:
> I'm not sure really why this happens. I work around it using something
> like this in the initialization code:
>
> if hasattr(sys, 'frozen'):
> app.top.tk.call('console', 'hide')
Thanks, that worked wonderfully.
On Nov 20, 2005, at 1:06 PM, Jon Rosebaugh wrote:
> When I build a .app version of my program, it runs just fine, but
> there's one little concern. When run, the .app version produces two
> windows: both the normal window it's supposed to produce, and a window
> labeled "Console", in which nothin
When I build a .app version of my program, it runs just fine, but
there's one little concern. When run, the .app version produces two
windows: both the normal window it's supposed to produce, and a window
labeled "Console", in which nothing ever seems to happen. How can I
keep this Console window f
