Hi Vaidotas,




thanks for the report, you're right here! :-) IMHO, this not a real bug, though clearly a behavior that could be improved. The reason is that every single mouse move your image receives while dragging something will trigger your list morph to check whether it can accept the dragged morph, so it will call #dropAccept: and open a debugger. This will happen again for every single of all the many MouseMoveEvents. You might want to use #haltOnce to spawn one debugger only.
However, for the feature after 5.3, I would be happy to make the debugger even more robust against this kind of debugger chains (which are not related to a known issue with process-faithful debugging). For example, we could simply count the number of debuggers that were opened in the last few seconds and show a prompt (#request:) if a certain threshold has been reached before opening further debuggers thereafter. This is just a vague idea and may need further discussion ...
Best,Christoph


Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Vaidotas Didžbalis <vaidasd at gmail.com>
Gesendet: Donnerstag, 27. Februar 2020, 21:04
An: Squeak-Dev
Betreff: [squeak-dev] bug in a ToolBuilder, Squeak5.3rc2

Hello, 
It seems there is a bug in the Morphic ToolBuilder lists, sorry if this is not right place reporting it. Say, we have:listSpec := builder pluggableListSpec new.listSpec 
      model: self;
     		list: #fields; 
       ...      dropAccept: #acceptThis:;
     		dropItem: #dropOn:at: .Image stalls if I put #halt in #acceptThis 
regards,Vaidotas


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200227/434e684d/attachment.html>