Path: utzoo!utgpu!water!watmath!garfield!john13 From: john13@garfield.UUCP (John Russell) Newsgroups: comp.sys.amiga Subject: Re: RMBTRAP underused Message-ID: <4574@garfield.UUCP> Date: 8 Mar 88 05:41:03 GMT References: <8803050120.AA04518@cory.Berkeley.EDU> Reply-To: john13@irma.UUCP (John Russell) Organization: Memorial University of Newfoundland Lines: 41 [ this part is me ] >:If you write a windowing program with no menus, please use RMBTRAP and just >:ignore the MENUUP / MENUDOWN messages. Matt Dillon writes: > If you are in the habit of hitting the menu button in windows which >have no menus, then simply get out of the habit. If not, then it doesn't >happen anyway. I use ClickUpFront quite a bit so I'm stuck with clicking the RMB in all sorts of windows. And if there are a lot of windows overlapping the title bar the refreshing can be annoyingly slow. Plus when I let some Amiga-novice try out my computer, it doesn't make a good impression that he can grind the system to a halt by pressing one of the mouse buttons. I'd rather have minor irritating behaviour like this fixed (eg the click-in-the-window behaviour fixed by Heliosmouse) than have to remember (and explain to others) warning after warning of the type "don't do X in this or that situation, but do it in this other situation". And this isn't a system-wide thing, it can be fixed by adding a single word to a source file. Then programs which don't use menus will ignore the RMB. In the meantime, there are 3 different things that happen when you press: 1) menu pops down 2) nothing, since program has no menus 3) screen freezes, title bar goes blank but no menu That's the kind of unreliable / inconsistent behaviour I look for and criticize on other computers so in fairness I have to point out Amiga examples too. I've seen Atari demos where they say "OK, just sit back and don't touch the mouse!". My response? "Hey, what happens if you move the mouse? Boy, that sure screwed up the screen!" :-). Anyway, it's a pet peeve of mine. John