win32gui bug: where to report it?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • George van den Driessche
    #1

    win32gui bug: where to report it?

    It's taken me ages to find out why my window, built out of win32all, wasn't
    receiving any messages. Eventually I found the answer here:

    429 Too Many Requests
    http://mail.python.org/pipermail/python-list/2001-October/069451.html


    The important point being:[color=blue]
    > IIRC you have to pass the return value of the RegisterClass() call (which
    > is an atom) to the CreateWindowEx( ) function as the second parameter
    > (lpClassName).[/color]
    .... in other words, you can pass the name of your window class as the second
    parameter, but it will silently fail to work. (This holds for CreateWindow
    too.)

    This is a bug for which it is pretty much impossible to work out the
    workaround without being told it, so I'd like to put the workaround in a
    more easily-found place. But where? win32all doesn't seem to have much
    documentation, much less a bug database.

    In case anyone else needs to find this message by searching, some keywords
    are: win32all, win32gui, WNDCLASS, RegisterClass, CreateWindow,
    CreateWindowEx

    George


    Tags: None
    • Roger Upole
      #2
      Re: win32gui bug: where to report it?

      Win32all is called Pywin32 now, and resides on SourceForge:
      http://sourceforge.net/projects/pywin32/

      Roger


      "George van den Driessche" <no-one@nowhere.com > wrote in message
      news:cusofn$f0n $1$8302bc10@new s.demon.co.uk.. .[color=blue]
      > It's taken me ages to find out why my window, built out of win32all,
      > wasn't
      > receiving any messages. Eventually I found the answer here:
      >
      > http://mail.python.org/pipermail/pyt...er/069451.html
      >
      > The important point being:[color=green]
      >> IIRC you have to pass the return value of the RegisterClass() call (which
      >> is an atom) to the CreateWindowEx( ) function as the second parameter
      >> (lpClassName).[/color]
      > ... in other words, you can pass the name of your window class as the
      > second
      > parameter, but it will silently fail to work. (This holds for CreateWindow
      > too.)
      >
      > This is a bug for which it is pretty much impossible to work out the
      > workaround without being told it, so I'd like to put the workaround in a
      > more easily-found place. But where? win32all doesn't seem to have much
      > documentation, much less a bug database.
      >
      > In case anyone else needs to find this message by searching, some keywords
      > are: win32all, win32gui, WNDCLASS, RegisterClass, CreateWindow,
      > CreateWindowEx
      >
      > George
      >
      >[/color]




      ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
      http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
      ---= East/West-Coast Server Farms - Total Privacy via Encryption =---

        Comment

        • Peter Hansen
          #3
          Re: win32gui bug: where to report it?

          George van den Driessche wrote:[color=blue]
          > This is a bug for which it is pretty much impossible to work out the
          > workaround without being told it, so I'd like to put the workaround in a
          > more easily-found place. But where? win32all doesn't seem to have much
          > documentation, much less a bug database.[/color]

          http://sourceforge.net/projects/pywin32/

            Comment

            Previous template Next
            Working...