[pywin32-bugs] [ pywin32-Bugs-1170769 ] commctrl.PY_0U should be 0
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
|
From: SourceForge.net <no...@so...> - 2005-04-12 03:04:21
|
Bugs item #1170769, was opened at 2005-03-26 09:03 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1170769&group_id=78018 Category: win32 Group: None >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Adal Chiriliuc (adalx) Assigned to: Nobody/Anonymous (nobody) Summary: commctrl.PY_0U should be 0 Initial Comment: It took me 2 hours to track this down. It causes problems when comparing notification codes since the code returned by Windows is 0 based, but the ones in commctrl.py are based on PY_0U which is not 0 right now. The correct notifications are invoked for both the bad and the good values of this constant. Probably because Windows only considers the lower 16 bits of the value, which are identical in both forms. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2005-04-12 13:04 Message: Logged In: YES user_id=14198 Checking in commctrl.py; new revision: 1.6; previous revision: 1.5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1170769&group_id=78018 |