On Mon, Jan 26, 2009 at 8:41 PM, Christiaan Hofman <[email protected]>wrote:
>
> On 26 Jan 2009, at 8:22 PM, Jonas Zimmermann wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> I just stumbled across some unexpected behaviour: I had the info
>> window of a publication open and wanted to add it to a keyword group
>> (just like you can add a publication by dragging from the list). I
>> grabbed it at its icon as I thought this icon represents this one
>> publication.
>>
>
> The icon of the publication window represents the linked file, if any, not
> one or more publications. Icons in the title bar /always/ represent a file
> (normally the corresponding document file).
>
Correction, the file icon does not seem to be the one for the linked file,
but for the .bib document file. This is not as intended, probably some OS
update has changed AppKit's behavior (I seem to recall that it worked even
after Leopard was released).
Anyway, as it now represents the main .bib file (which in fact is the
/normal/ behavior for Mac OSX), dargging it should be considered as dragging
this .bib file. And when you drop this file on a group, the content of the
file will be parsed and the new items will be added to the group. And this
is completely as expected.
So the real problem is that you did not realize that the icon represents a
/file/ rather than a publication. While this is standard behavior.
Apart from that, there's stil the unrecognized selector exception, whgich is
a real bug. However I don't see where it comes from and I can't reproduce
it.
Christiaan
> Wrong I was, as it added all my publications to this
>> keyword group, cause an error (a popup said "*** -[NSCFType dismiss:]:
>> unrecognized selector sent to instance 0x252e94c0") and finally
>> crashed BibDesk.
>> Is this intended behaviour (I mean the icon of the publication window
>> representing all publications)? If so, could it behave more graceful?
>>
>> Best,
>> Jonas
>>
>
> This is definitely not intended behavior, none of it. It's clearly a bug,
> though I don't see ATM where. Unfortunately the traces below just show
> generic event handling messages, not the relevant part about what event
> caused the problem and in what context. I also don't understand why it would
> add all items to a group, it's probably just be a side effect of the
> exception.
>
> Christiaan
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
