From: Ernst De R. <hnr...@in...> - 2003-02-19 20:19:37
|
On Wed, Feb 19, 2003 at 03:25:02PM +0000, John Pettigrew wrote: > In a previous message, Ernst De Ridder wrote: > > > I don't like losing my selections either, that's why I suggested c) > > restore the selection after applying the command to the file under the > > pointer. > > This would be OK, I guess, but it could be confusing. Also, it still has the You're absolutely right. After the responses here I thought about why I am expecting things to work differently than they do in ROX, and came to the conclusion that it is because I'm expecting [*] a windows style context menu instead of a RISC-OS style main menu on right click. Context menus mean bad usability so the proper solution is to make other programs use RISC-OS style menus and not to make ROX use context menus. [*] And I don't even use MS-Windows - The windows brainrot has reached me through unix programs which are infected with the MS way of doing things:-( > And that's the problem - single-click navigation is what introduces this > inconsistency. Normal GUI behaviour (and the RISC OS one, on which Rox > is based) is for double clicks to run files. If you think of single-click > navigation as emulating double clicks then the inconsistency disappears - > click on the file to select it, then run it (left click) or bring up a menu > (menu button). Yeah, but double clicking a file to activate it is again inconsistent with single clicking a button or toolbar icon to activate it. My problem was expecting the item under the pointer to have influence on the right button. By viewing the right button as something special the inconsistency disappears too, and without introducing new ones:) My conclusion: The ROX way is the way all programs should work and ROX shouldn't be changed. Ernst |