Re: Gorm brokeness

[Fred Kiefer]

Just to keep you informed on my current finding. I could follow a mouse
down event that should start a drag into the method [XGDragView
dragImage:at:offset:event:pasteboard:source:slideBack:] there the call
to mimeTypeForPasteboardType() seems to fail, when doing manual calls in
gdb I get

(gdb) po pboard
<NSPasteboard: 0x11b68e0>
(gdb) p [pboard types]
$14 = (class NSArray *) 0x109a610
(gdb) po [pboard types]
<NSDistantObject fee2c0>
(gdb) p [[pboard types] count]
$15 = (void *(*)()) 0x7fffef701000
(gdb) p (int)[[pboard types] count]
$16 = -277884928
(gdb) p (long)[[pboard types] count]
$17 = 140737210454016

Now this may not the the root of the problem, but it looks strange to
me. But why wont the function mimeTypeForPasteboardType return?
After adding a breakpoint in [NSException raise] I get:

(gdb) bt
#0  -[NSException raise] (self=0x1056940, _cmd=0x7ffff6c03ab0) at
NSException.m:899
#1  0x00007ffff6818300 in -[NSConnection(GNUstepExtensions)
forwardInvocation:forProxy:] (self=0xfba420,
    _cmd=0x7ffff6c105c0, inv=0x1062840, object=0x11a81a0) at
NSConnection.m:2090
#2  0x00007ffff6928507 in GSFFIInvocationCallback (cif=<value optimized
out>, retp=0x7fffffffc670,
    args=<value optimized out>, user=<value optimized out>) at
GSFFIInvocation.m:636
#3  0x00007ffff47d9729 in ffi_closure_unix64_inner (closure=<value
optimized out>,
    rvalue=<value optimized out>, reg_args=0x7ffff5d04d3a,
argp=0x7fffffffc690 "@#�")
    at src/x86/ffi64.c:620
#4  0x00007ffff47da0b0 in ffi_closure_unix64 () at src/x86/unix64.S:228
#5  0x00007ffff31f799a in mimeTypeForPasteboardType (types=<value
optimized out>,
    zone=<value optimized out>, xDisplay=<value optimized out>) at
XGDragView.m:140
#6  -[XGDragView dragImage:at:offset:event:pasteboard:source:slideBack:]
(types=<value optimized out>,
    zone=<value optimized out>, xDisplay=<value optimized out>) at
XGDragView.m:217
#7  0x00007ffff7b3895d in -[GormPaletteView mouseDown:] (self=0xcdd460,
_cmd=<value optimized out>,
    theEvent=0xf8cd00) at GormPalettesManager.m:236
#8  0x00007ffff6ff7393 in -[NSWindow sendEvent:] (self=0xc32340,
_cmd=<value optimized out>,
    theEvent=0xf8cd00) at NSWindow.m:3666
#9  0x00007ffff6e94af4 in -[NSApplication run] (self=<value optimized
out>, _cmd=<value optimized out>)
    at NSApplication.m:1530
#10 0x00007ffff6e7612e in NSApplicationMain (argc=<value optimized out>,
argv=<value optimized out>)
    at Functions.m:74
#11 0x00007ffff5ca5a7d in __libc_start_main () from /lib64/libc.so.6
#12 0x0000000000401ac9 in _start () at ../sysdeps/x86_64/elf/start.S:113

(gdb) po self
<NSException: 0x1056940> NAME:NSInvalidArgumentException REASON:subclass
GSMutableArray(instance) should override count


Looks like this method go lost in recent rewrites of base :-)
I will fix this and also change all the parameters in GSArray.m to
NSUInteger that are now changed in the super class NSArray.

Fred

Am 07.03.2010 18:46, schrieb Fred Kiefer:
> The non-working palettes are at least something I am able to reproduce
> on my system. This doesn't seem to be relate to the selected backend.
> It might either be a Gorm or a gui problem. I will look into this.
> 
> Am 07.03.2010 17:20, schrieb Gregory Casamento:
>> I can confirm that I can't drag anything from the palettes.  It
>> appears that recent changes in GUI may have broken something.
>>
>> GC
>>
>> On Sun, Mar 7, 2010 at 9:09 AM,  <address@hidden> wrote:
>>> Hi, all!
>>>
>>> Because of my ongoing issues with current GNUstep from svn today I decided
>>> to do a fresh start and removed all GNUstep installation related files from
>>> my hardrive. After that I did a svn update and did a fresh build of core and
>>> gorm. Looks like Gorm is as of now rather broken. I can open an existing
>>> document of mine, I can create a new document, but the palettes do not work.
>>> I can select a palette, but I am unable to actually select an item, like a
>>> button, and drag it into a window. Also the inspector seems broken, it does
>>> not display stuff like RadioButtons or button icons. I attached two
>>> screenshots. Looks like the NSTabView issues are just syntoms of the same
>>> underlying problem. NSTabView does display correctly if it is told to
>>> display it's "item bar" at the bottom, screenshots are attached.