On Apr 30, 2016, at 17:27 , Richard Charles wrote:
>
> NSNumber *yes = [NSNumber numberWithBool:YES];
> [self performSelector:@selector(setNeedsDisplay:) withObject:yes
> afterDelay:0.0];
No, that’s the opposite of the solution to that particular issue. :)
The problem is that you’re passing an
> On Apr 30, 2016, at 5:39 PM, Quincey Morris
> wrote:
>
> Do you have any proof that ‘mouseMoved’ is called at all?
Yes adding logging shows that both methods mouseMoved: and mouseInactive are
being called.
> Note that there are two different ‘mouseMoved’s. One is a continuous stream
> of
On Apr 30, 2016, at 12:49 , Jean-Daniel Dupas wrote:
>
> Maybe registering the changes is not executed immediately but deferred until
> the end of the current event loop cycle
There’s no “maybe” about it. By default, the undo manager groups all undo
actions registered between iterations of the
On Apr 30, 2016, at 16:08 , Richard Charles wrote:
>
> - (void)mouseInactive
> {
>// This does not work.
>[self setNeedsDisplay:YES];
>
>// This does not work. I think this did work at one time but stopped
>// working on OS X 10.10 Yosemite.
>[self performSelector:@selector(s
I have a view that needs to be refreshed after a period of mouse inactivity.
- (void)mouseInactive
{
// This does not work.
[self setNeedsDisplay:YES];
// This does not work. I think this did work at one time but stopped
// working on OS X 10.10 Yosemite.
[self performSele
Just my 2 cents.
Maybe registering the changes is not executed immediately but deferred until
the end of the current event loop cycle, so the undo manager can group them
into a single operation.
In such case, it would mean that what you think is the undo registration is
just a call to schedul
Hi
My app deals with an object tree that can have millions of leaves. It is
possible to run an operation on all of them. Each will register its own change
with the undo manager. The hole operation might tale a few second (the last
line in the trace below). But after my operation is finished, th
I asked this question early yesterday on the accessibility-dev list and
received no answers, so I thought I would try here.
Using my UI Browser application , I am seeing a new
"AXSections" accessibility attribute in all windows of all applications in OS X
10.11 El Capitan, but I can find no ref
