Since CGSRegisterCursorWithImages is a private function and it is not called directly form Pd, one could say it's a bug in CG per se - because the function that calls it from inside CG shall not pass on any illegal calls.
Andras
yeah had a few min today to take some more look at this.
been reading up on the whole tk-cocoa thing too...
as far as I can tell, there are not multiple issues but one larger one
narrowed down to:
Oct 27 15:01:49 megrimm-mbp.local Pd-0.43.1-extended-20111027[15460]
<Error>: kCGErrorIllegalArgument: CGSRegisterCursorWithImages: Invalid
hot spot (outside of size)
which occurs specifically when switching with the mouse between the PD
console window and the canvas/patch window.
also I was totally wrong here:
>>> You can resize on the left, right, and bottom left now? I guess that's a
>>> Lion thing.
>>
>> No I actually CAN NOT with the autobuild ONLY with my special tk/cocoa
>> build....
windows CAN be resized on lion from any corner (Any Corner Resizing)
although again, on my tk-cocoa build PD will crash when trying to
resize from the bottom right or left. This is NOT true of the PD
console window though which can be resized without a problem from any
corner.
my question is: whats the difference between the code for the PD
console window that allows for resizing at any corner and the PD
canvas windows that do not? I think this may be the heart of the prob
with the crashes and weird error (CGSRegisterCursorWithImages) ....
maybe.
other thing i am noticing is the mouse pointer keeping weird states
(double pointer, etc) without reverting back to a pointer. I also get
no "hand2" in edit mode. not sure if this is related to the windowing
problem though...
> I know that feeling all to well, it's nice to have some company in it.
i think im just starting to get old
m
On Wed, Oct 26, 2011 at 10:51 PM, Hans-Christoph Steiner <hans@at.or.at> wrote:
>
> On Oct 25, 2011, at 6:37 PM, m.e.grimm wrote:
>
>>> from that. Can you run Pd-extended 0.43 and trigger that crash, and post
>>> the crash log to a pastebin.com?
>>
>> you mean with the autobuilds? I can not trigger that crash with those.
>> those are fine...
>>
>> but maybe more importantly:
>
> Duh, sorry, the point was to test Pd without the included Tcl/Tk and to use
> Mac OS X's Tk/Cocoa.
>
>
>>> You can resize on the left, right, and bottom left now? I guess that's a
>>> Lion thing.
>>
>> No I actually CAN NOT with the autobuild ONLY with my special tk/cocoa
>> build....
>>
>> my eyes are bleeding so more from me will have to wait until tomorrow.
>
> I know that feeling all to well, it's nice to have some company in it.
>
> .hc
>
>
>> On Tue, Oct 25, 2011 at 4:02 PM, Hans-Christoph Steiner <hans@at.or.at>
>> wrote:
>>>
>>> On Oct 25, 2011, at 3:51 PM, m.e.grimm wrote:
>>>
>>>> well commenting out lines 84 -> 86 in pdwindow.tcl stops the message:
>>>>
>>>> -----------
>>>> UNHANDLED ERROR: can't find package tkdnd
>>>> while executing
>>>> "package require tkdnd"
>>>> ("uplevel" body line 1)
>>>> invoked from within
>>>> "uplevel #0 $tclcode"
>>>> FAILED TO LOAD /Library/Pd/tkdnd-plugin.tcl
>>>> -----------
>>>>
>>>>
>>>> from appearing in the pd window.
>>>>
>>>> maybe thats something. IDK.
>>>
>>> That's a red herring, you really want those lines in pdwindow.tcl since
>>> they
>>> show you Tcl errors. The UNHANDLED ERROR that you are seeing is caused
>>> by
>>> the file /Library/Pd/tkdnd-plugin.tcl. Remove that file and it will go
>>> away.
>>>
>>>
>>>> i will have to mess with i more when i get time. I also wanted to
>>>> mention that I get spinning beachball and prog crash when I try to
>>>> resize a new doc only starting from the bottom right. all other window
>>>> resizing (upper left and right, bottom left) work fine. does that mean
>>>> anything to you?
>>>
>>> You can resize on the left, right, and bottom left now? I guess that's a
>>> Lion thing.
>>>
>>>
>>>> anyway here is the crash report:
>>>
>>> That seems to show stuff deep in Tcl, so its hard to know what's going on
>>> from that. Can you run Pd-extended 0.43 and trigger that crash, and post
>>> the crash log to a pastebin.com? It should have more info since its
>>> built
>>> with debug symbols.
>>>
>>> .hc
>>>