A/UX 2.0: Double-Click Behavior and Locked Files

Sometimes A/UX fails to respond promptly to mouse clicks (presumably because the preemptive time slicer has
preempted the task running my Macintosh window and has given the CPU to someone else).

So, for example, when I'm trying to edit a file name by clicking the name under the icon, I often find myself launching the software instead, because the Macintosh "double-click detector" thinks I double-clicked, when in fact I only clicked twice in the text field of the icon. In other words, the definition of "double-click" seems to be variable under A/UX.
Although A/UX handles jobs based on a preemptive, time-slice basis, we can't reproduce the mouse double-clicking behavior that you described. In any case, here is the scenario of the mouse motion:

If the file is UNLOCKED and the mouse is pointed and single-clicked on the name of that file under the icon, the mouse symbol
SHOULD change from arrow pointer to I-beam which lets you change the name of the file (the name is then highlighted). Then, when the mouse is double-clicked on the name, the word in the name is selected and allowed to change that word. When the mouse pointer leaves the name area, it becomes an arrow point.

If the file is LOCKED and the mouse is pointed and a single-clicked on the name of that file under the icon, the mouse symbol remains an
arrow pointer which means the name of file can't be changed, because it was LOCKED. In this case, if the mouse is double-clicked on the name of the locked file, it will launch the program.

Check if the file to be renamed is LOCKED or UNLOCKED.
Published Date: Feb 20, 2012