Hi Ken

> Perhaps this is an unrelated problem and is instead a general 
> drag and drop problem.  

This is a problem that has always been there and it is in that sense
unrelated to the fix I posted. This fix only solves the bug introduced
in the changeset KCP-0220. 

> When you click and drag something 
> shouldn't it be selected before dragging starts?

This would be a way to solve this. I'm quite busy right now and so I'm
focusing on fixing the bugs I introduced myself right now ;-). I'll try
to have a look at this general problem as soon as I have a bit of time.

Nathanael


> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] On 
> Behalf Of ken at kencausey.com
> Sent: Montag, 10. Mai 2004 20:58
> To: squeak-dev at lists.squeakfoundation.org; n.schaerli at gmx.net
> Subject: [BUG][FIX] Drag a class for changing category ( 
> [sm][et] incompletefix? )
> 
> 
> 
> This is a relatively simple fix.  I've tested it and it does 
> fix at least part of the problem but there is still a problem.
> 
> It is possible to grab a class that you don't have selected 
> and drag it.  The dragged object is labelled 'nil' and when 
> you drop it on a category you get a debugger.
> 
> Perhaps this is an unrelated problem and is instead a general 
> drag and drop problem.  When you click and drag something 
> shouldn't it be selected before dragging starts?
> 
> Ken
> 
>