Re: [TCLCORE] Purpose of mmObjType vs pixelObjType

[Pat T. <pat...@us...>]

"Alexandre Ferrieux" <ale...@gm...> writes:

>>>==== + winDialog-1.1 hanging (bgerror window saying :
>>>
>>>    while executing
>>>"testwinevent $::tk_dialog $button WM_LBUTTONDOWN 1 0x000a000b"
>>>    (procedure "Click" line 2)
>>>
>>>Yes, the error string is _empty_).
>>>
>>>Am I alone to witness all this ?
>>>I hesitate to fiddle with the coordinate system with such a background...
>>
>> I get some text widget failures and 2 canvas fails. I certainly dont
>> see the winDialog one. Is that always happening for you? If so are you
>> using a non-English version of windows or something other than XP
>> maybe?
>
>Yes, it is deterministic :-(
>Yes, I'm using a French version of Windows, but is it an excuse ?
>As I said, it is Windows XP SP2...

Its not an excuse but an additional data point. Its possible, although
not likely, that the resource ID used for that button on that dialog
is different for non-English versions of windows. If so then a
constraint needs to be added.
However, checking the resources in comdlg32.dll - the Annuler button
has the same ID (2) as the Cancel button in the English locale. In
fact OK and Cancel are standard ids - I cant think of any reason why
winDialog-1.1 should fail for you and not for me. You probably should
raise a bug, Very strange.

-- 
Pat Thoyts                            http://www.patthoyts.tk/
PGP fingerprint 2C 6E 98 07 2C 59 C8 97  10 CE 11 E6 04 E0 B9 DD