|
From: SourceForge.net <no...@so...> - 2006-04-24 11:47:52
|
Bugs item #1475467, was opened at 2006-04-24 13:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1475467&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: win32ui: Internal error-existing object is not of same type? Initial Comment: I get rare reports with this error: "win32ui: Internal error - existing object is not of same type as requested new object" (the last was on a Win XP Prof; build 208 or build205 - not sure) it traces to a bare: tt=win32ui.CreateToolTipCtrl();tt.CreateWindow(parent,0) I don't even find the above error string in the pywin32 sources. Only "Internal error - existing object has type..." in win32assoc.cpp What error is this "existing object is not of same type as requested new object"? Most probably it has to do with (win32tooltip.cpp): return ui_assoc_object::make( PyCToolTipCtrl::type, pTTC ); Many of such ::make's in the win32ui sources have a "->GetGoodRet()" on the line. Some have not. What is the criteria? Is such ->GetGoodRet() maybe necessary in that win32tooltip.cpp location? Can a misbehaviour on such ::make's also cause crashes? (I have occasional mem. access crash reports also; mainly on dual core's) -robert ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1475467&group_id=78018 |
