[python-win32] python and Windows Resource Files.

[Johri, Mayank (GTI)]

Tim,

Thanks for the information, I know the pain ;) it is causing me. 
The reason why I went to use RC was that the over head on my final
package size was minimal. But now I think trying wxPython or Tkinker
will be a better solution in long run.

Thanks and Regards,
Mayank Johri
Merrill Lynch & Co.
Ph: 212.647.3076



-----Original Message-----
From: python-win32-bounces at python.org
[mailto:python-win32-bounces at python.org] On Behalf Of Tim Roberts
Sent: Monday, December 17, 2007 12:59 PM
To: Python-Win32 List
Subject: Re: [python-win32] python and Windows Resource Files.


Johri, Mayank (GTI) wrote:
> Tim,
>
> I am using the win32rcparser and win32gui to display the dialog on the
> screen. I have used the example win32rcparser.py for this.
>   

Well, win32rcparser.py reads the RC file, but it doesn't display it on
the screen.

What you're doing is working at the lowest possible level.  If you want
to create a Windows GUI using the raw API, then you might as well write
it in C++.  You're just going to battle the Python/C boundary over and
over.  It is possible to call GetDlgItem to fetch window handles for the
controls in your dialog, and then send Windows messages to fetch their
contents, but it's a lot of work for no particularly good reason.

It would be much better in the long term for you to investigate wxPython
or tkinter or one of the other GUI wrappers, to let you create and
manage your GUI with something approaching Python's class philosophy.

-- 
Tim Roberts, timr at probo.com
Providenza & Boekelheide, Inc.

_______________________________________________
python-win32 mailing list
python-win32 at python.org
http://mail.python.org/mailman/listinfo/python-win32
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------