Diego Vélez Torres wrote:
> Hi:
>
> I'm having issues with tkinter, COM servers and Python 3.4. I can't
> call tkinter inside a COM server. I tried many examples of tkinter,
> but every time I try to init a tkniter instance ( tk = tkinter.Tk()
> ) inside a running COM server, the same follow
Hi Tim:
I just fixed the issue by applying your advise. But (...and here comes a
big BUT !!!), why do I have to do this when calling tkinter inside a COM
server, meanwhile this is not necessarily when outside a COM? If my COM
Server were using tkinter directly I could rely on this trick. However
Diego Vélez Torres wrote:
>
> I just fixed the issue by applying your advise. But (...and here comes
> a big BUT !!!), why do I have to do this when calling tkinter inside a
> COM server, meanwhile this is not necessarily when outside a COM?
You shouldn't. I'm sure this is a bug, but it would tak
Hi Tim:
I finally was able to fix this issue in my code. Thanks for your advise.
Now I want to share with the community exactly what I did by posting the
whole "__init__" method of tkinter's "__init__.py" file:
def __init__(self, screenName=None, baseName=None, className='Tk',
Diego Vélez Torres wrote:
>
> I finally was able to fix this issue in my code. Thanks for your
> advise. Now I want to share with the community exactly what I did by
> posting the whole "__init__" method of tkinter's "__init__.py" file:
>
> def __init__(self, screenName=None, baseName=None, clas
Yes, I did. In normal situations the value is a string, but when I call from a
COM is bytes.
Sent from Samsung Mobile
Original message From: Tim Roberts
Date:05-18-2015 6:02 PM (GMT-05:00)
To: Python-Win32 List Subject:
Re: [python-win32] Issues with tkinter, COM servers
divelez69 wrote:
> Yes, I did. In normal situations the value is a string, but when I
> call from a COM is bytes.
I meant, what was the actual VALUE of the string? Was it a fake value,
or was it approximately correct?
If Python itself is generating os.path.basename, it's hard for me to
understan
