Re: [Pyobjc-dev] Re: interface builder queries

[Michael H. <mw...@py...>]

On Tuesday, Aug 26, 2003, at 22:20 Europe/London, Ronald Oussoren wrote:

>
> On dinsdag, 26 augustus 2003, at 23:04PM, b.bum wrote:
>
>> On Aug 26, 2003, at 10:19 AM, Michael Hudson wrote:
>>> I had stumbled towards the fact that I might want to do that, but I
>>> have *no* idea where to even start... I don't suppse anyone has an
>>> example knocking around?  Even one in ObjC would be helpful, I guess.
>>
>> - have a look at the example palette(s) provided in 
>> /Developer/Examples/
>>
>> - create an Interface Builder palette project (punt on the whole 
>> PyObjC thing for the moment -- straight ObjC will be more 
>> straightforward for now)
> Python should also work, as long as IB is single threaded,
                                            ^^^^^^
This might be a problem.  After some idiocies on my part (and finding 
that palettes refer to some things in the Info.plist file, but 
generally seem to find a "palette.table" file more significant), 
loading my palette into IB crashes it, like so:

Date/Time:  2003-08-28 00:19:28 +0100
OS Version: 10.2.6 (Build 6L60)
Host:       Michael-Hudsons-Computer.local.

Command:    Interface Builder
PID:        2359

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0xffffb918

Thread 0 Crashed:
  #0   0xa0d4a538 in characterSet.0
  #1   0xa0d4a538 in characterSet.0

Thread 1:
  #0   0x90014c68 in syscall_thread_switch
  #1   0x97e03ef4 in +[NSThread sleepUntilDate:]
  #2   0x93081cac in -[NSUIHeartBeat _heartBeatThread:]
  #3   0x97e2cc50 in forkThreadForFunction
  #4   0x90020c88 in _pthread_body

PPC Thread State:
   srr0: 0xa0d4a538 srr1: 0x0000f030                vrsave: 0x00000000
    xer: 0x00000000   lr: 0xa0d4a538  ctr: 0x9005e258   mq: 0x00000000
     r0: 0x020522a0   r1: 0xbfffa9e0   r2: 0x4804424b   r3: 0x01f9d890
     r4: 0x00000000   r5: 0x0000012e   r6: 0xbfff98e4   r7: 0xa1b1c1d3
     r8: 0x0012c010   r9: 0xa30a0978  r10: 0x01f8a010  r11: 0xa0d4a538
    r12: 0x9005e258  r13: 0x0149275c  r14: 0x01fd00f0  r15: 0x1010278c
    r16: 0x00000000  r17: 0x00000000  r18: 0x10072ae8  r19: 0x0206b9f4
    r20: 0x00000000  r21: 0x1007278c  r22: 0x015d6f60  r23: 0x0206b9f4
    r24: 0x100f3624  r25: 0xa7e04ef4  r26: 0xa30a1d28  r27: 0xa7e02c14
    r28: 0xa309d8e8  r29: 0xa309e278  r30: 0xa30a0d08  r31: 0xa7e030f4

I think thread 0 could technically be described as being in 
'never-never land'.  Control is making it to Python, FWIW, it's just 
dying horribly on the import of AppKit (or Foundation or PyObjCTools 
but not, say, sys or time or objc).

This is the point where running away terribly fast starts to look a 
good option.  Doing any significant digging will require my own 
framework build of Python and my own build of PyObjC, things which take 
a little while to acquire on this iBook... (hey, Jack, what about an 
"install source" option to PackMan <wink>?).

Cheers,
mwh