Hi all,

I believe any artificial waits unless they are well below any perception threshold are really bad.

Is there a particular reason why one does not make halos go away the way one made them appear, i.e., by an alt-click on them?
Maybe I want to invoke the world menu without the halos going away.

I am not following the 2.9 updates but I noticed with Squeak 2.8 and even VisualWorks that one sometimes has to wait for the UI to catch up with one's mouse clicks, i.e., you have got to keep the mouse button down for some ever so slight extended period of time or it is missed.

As bad as Windows is in other aspects it has become very responsive and I suspect one will never just work with Squeak alone but always with a heterogeneous set of tools Squeak being just one in the set, albeit hopefully the most prominent and useful one.

Therefore, I think one should strive to make it as responsive as the other GUIs we know and artificial delays are leading in the wrong direction.

BTW, dragging with mouse-buttons down is a suboptimal gesture, IMHO.
In the Eiffel environment the right button was used to start dragging with one click and stop dragging with another terminating click. If you dropped, e.g., a class name into the pane where it appeared, the pane showed the class definition, i.e., dragging with source location=target location became a double click.
Although it took me a little while to get used to the increased number of clicks, the benefit of not being forced to press *and* move anymore was certainly large.
The right mouse button in Squeak should be reserved for context sensitive menus but it may be worth a try to initiate dragging with a 'your key'-click and terminate it with a normal click.

Regards,

    Thomas

--
Dr. Thomas Kuehne
0178 4314387, http://www-agce.informatik.uni-kl.de/~kuehne
The difficulty in doing research is to find the right questions
so that all the answers come easily. -- TK