Re: Problem with some clicks not registering in 10.3.6?
Re: Problem with some clicks not registering in 10.3.6?
- Subject: Re: Problem with some clicks not registering in 10.3.6?
- From: Wade Tregaskis <email@hidden>
- Date: Fri, 19 Nov 2004 11:55:35 +1100
Has anyone else has problems with mouseclicks (or drags) not
registering sometimes in OS 10.3.6 (I also had the problem in 10.3.4,
and maybe before that - don't remember).
I haven't had the exact problem you specify, but I've noticed since
about 10.3.4/10.3.5 a lot of mouse and key events are ignored the first
time. For example, shift-clicking in the Finder (to select a group of
files) *always* fails the first time - it ignores the shift and just
selects whatever individual item I click on. Extremely annoying.
Similarly, it occasionally ignores other key modifiers, or ignores
clicks entirely - this is usually random, so far as I can tell.
I think it's an app-based issue, in my case; I have no such issues with
most apps (particularly games, where I really would notice if things
didn't work), just apps like the Finder, Safari and Mail. Possibly
iTunes, as well, although much more rarely. There's also major issues
with Safari where it completely ignores key input when under load - so
if I type Command-N and start typing in the address, it completely
loses it (opening new windows in Safari is particularly slow, for no
obvious reason, so this is an easily reproducible example). Again,
extremely annoying, because it's preventing exactly the most desirable
behaviour. It may be indicative of a mangled event-handling model
(which could tie in with the sort of problems you're seeing).
The issues you allude to with clicks not working on metal windows seems
to be a symptom of a major problem somewhere - if you think it's bad as
is, try rotating the window
(http://homepage.cs.latrobe.edu.au/wjtregaskis/Rotated Windows.sitx) -
however dragging by content is implemented, it appears it draws inputs
from at least two sources and these quite easily conflict. Obviously
when you play with the window server in order to rotate the window,
that's going to create problems of it's own, but even so, I'm sure
there's something bad happening anyway; probably some innocent
optimisation somewhere with mouse monitoring, that goes haywire under
some conditions.
My pet hate, however, has been around for as long as I can remember,
and is where clicking on a window sometimes, for no apparent reason,
brings that window to the front but doesn't actually activate it, so
you then have to click on another apps window to get out of it, and try
again. This happens at least once an hour for me, with no apparent
rhyme or reason.
And then there's when you launch an app, explicitly click back onto
whatever app you're working on (i.e. you want the new app to launch
into the background for the moment), but it persistently keeps throwing
it's windows up in front, and becoming active. This is most likely a
fundamental design flaw with the Cocoa startup sequence - it doesn't
appear to happen with Carbon apps.
Wade Tregaskis (AIM, Yahoo & Skype: wadetregaskis, ICQ: 40056898, MSN &
email: email@hidden, Jabber:
email@hidden)
-- Sed quis custodiet ipsos custodes?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden