On Monday, September 10, 2007, at 01:15PM, "Justin C. Walker" <[EMAIL 
PROTECTED]> wrote:
>Hi, all,
>
>Just downloaded FileVewTest from Adam's website.
>
>On Sep 10, 2007, at 10:11 , Adam R. Maxwell wrote:
>> On Monday, September 10, 2007, at 09:52AM, "Christiaan Hofman"  
>> <[EMAIL PROTECTED]> wrote:

>FWIW, I see the dashed line only when the window is empty.  If I drop  
>an icon on the window, the line and text disappears; when I remove  
>all the icons, they reappear.

You must have downloaded after I fixed that :).

>>> But you can drop an icon next to itself, duplicating it. That
>>> shouldn't happen.
>>
>> Yeah, thanks for pointing that out; it's a consequence of  
>> rearranging not being implemented yet.  Insertions are handled the  
>> same regardless of their source.  I rewrote most of the drop  
>> handling code yesterday to handle inserting and guard against some  
>> assumptions left over my first prototype (which assumed single  
>> selection).
>
>I'm not sure how this relates, but:
>  - if I rearrange, I get a dup of the thing I drag (I think
>    that is what you mean, but I'm not sure).

Yes.  It should move, but instead it copies (nothing is changed on disk, 
though).  Making this work correctly is next on my to do list.

>  - if I drop an icon on itself, the icon becomes selected but
>    I see no dup

I just fixed that...it was broken in my last rewrite.  Dropping an icon on 
itself is a no-op, but shouldn't be allowed.

>  - if I drop an icon on a different one, it appears to replace
>    the existing one

That's by design.  I may end up removing that, though, since it rarely makes 
sense due to rewrites along the way.  This is the time to change stuff like 
that, so thanks for the comments.

>  - In both cases, the new icon is just sitting on top of the
>    existing one.  Dragging that icon will reveal the previous one.

That's not supposed to happen, and it doesn't happen for me.  There's no 
layering; this is more like iPhoto than Finder.  Are you sure that happens?

>>> For me it crashes consistently.
>>
>> Huh...not a Tiger bug after all, but it does appear to be an Apple  
>> bug.  I copied a fixed version to the same location that shouldn't  
>> have this problem.
>
>I have seen no crashes (PowerPC, 2x2.7GHz G5, 10.4.10) in any of the  
>versions I've tried.

Good.

>--------
>When LuteFisk is outlawed,
>Only outlaws will have LuteFisk
>--------

Mmmm...lutefisk!

-- 
Adam

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users

Reply via email to