Re: Can't turn off screen savers in System Preferences
Re: Can't turn off screen savers in System Preferences
- Subject: Re: Can't turn off screen savers in System Preferences
- From: Philip Aker <email@hidden>
- Date: Sat, 07 Oct 2006 15:53:27 -0700
On 2006-10-07, at 14:39:47, deivy petrescu wrote:
On Oct 6, 2006, at 7:50, Bill Cheeseman wrote:
Finally, using UI Browser's Attributes drawer to set the value to
any legal value also fails to stick when you quit System
Preferences and restart it.
Here I take issues with you. I believe it does not stick period!
If you change the dial manually it sticks immediately, you can read
it from the defaults value. Changing it via UI does not affect the
value. So it is "moved" but never "changed". And this is
independent of quitting and restarting SP.
Here's what I think (from previous post):
The problem as I see it now is that when manually altering the value
of the slider there are only two possible actions:
1. Drag the indicator.
2. Click at a point on the slider exclusive to the rectangle of the
indicator.
IOW, all of the previous attempts at a solution, except for the dss
method have been targeting the wrong area.
Of the two actions, System Events currently can't handle a drag but
it's supposed to be able to handle a mouse click at an arbitrary
location. I can for instance click a window's close button like so:
tell application "System Events" to tell application process "Finder"
set wpos to position of window 1
set x to (item 1 of wpos) + 12
set y to (item 2 of wpos) + 12
click at {x, y}
end tell
Therefore, we should be able to click at a location within the
slider's bounds and have the indictor jump to that and have the value
stick. However, I'm having a problem getting the slider to recognize
the click at what I think is a valid point…
So if anyone knows how to click that sucker (oops, I mean slider),
speak up. Actually I do, but it's in Carbon and that's not what we
need for an AppleScript only solution.
And, at the risk of sounding redundant: <https://bugreport.apple.com/>
Since GUI Scripting and UI Browser use essentially the same
accessibility API code under the hood, this establishes that the
bug lies in the implementation of accessibility support in this
slider. I would guess that the complexities of this dead zone
implementation of the snap effect led the programmer who made this
slider accessible to an error which causes the
Philip Aker
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden