Multithreading – busy cursor – why?

Can anyone give me a scene they think is reasonable? I think from the user's point of view, they are always a bad idea Clarification: with the busy cursor, I mean that when users can no longer interact with the application, they can only move their hourglass mouse pointer and whistle

Solution

I think you may be right: in a decent asynchronous application, you never need to display a busy cursor Even if the last operation is completed, the user can do something at any time

In other words, sometimes Java applications such as NetBeans or eclipse, or even visual studio, hang without busy cursors and no hope But in this case, busy cursors may not help much, but I think you're right: busy cursors come from the non multithreaded era of applications For example, in flex applications, everything is an automatic event driven callback, so setting a busy cursor would be meaningless (if possible)