Well, it's easy. I just created an animation queue, thus if one
transition is called while another one is still running (busy), it is
put into an array and executed when the running animation has
finished. It works pretty awesome!
— Tobias.
On May 18, 2010, at 2:42 AM, Jack Carbaugh wrote:
Hey guys, it's funny, I just found a way of handling the animation
without blocking the UI. I thought it's impossible to be in control of
everything then but that's obviously not true. :-)
Thanks to everyone!
Best regards,
Tobias Jordan.
On May 17, 2010, at 7:02 PM, Kyle Sluder wrote:
On
On Mon, May 17, 2010 at 9:21 AM, Uli Kusterer
wrote:
> Can't you just not not ask for mouseDown events in your event mask while
> running your event loop? My guess would be that that would keep any menus
> from opening.
Gah! That would be a bad idea. The HIG says menus should always be
openabl
Bear in mind most of the animations in the OS predate Core Animation, so tend
to behave a little differently.
Even so, take something like the Genie effect. It's possible to kill the
animation midway and have a distorted, but usable window.
On 17 May 2010, at 17:28, Tobias Jordan wrote:
> You
You are right Uli, I'd definitely like to let the user decide what to
do but when taking a look at Apple's OS X animations I have to say
it's always completely blocking the UI so I thought that's a default
behavior. I don't know yet whether I'll need to disable the MainMenu
or not, it depen
On May 17, 2010, at 6:08 PM, Tobias Jordan wrote:
> Thanks for your nice ideas guys, both solutions, subclassing NSApplication
> (overwriting -sendEvent:) and calling
> -nextEventMatchingMask:untilDate:inMode:dequeue: in a loop work. Now the only
> thing that's missing is disabling the applicati
Thanks for your nice ideas guys, both solutions, subclassing
NSApplication (overwriting -sendEvent:) and calling -
nextEventMatchingMask:untilDate:inMode:dequeue: in a loop work. Now
the only thing that's missing is disabling the application's menu
since it's still clickable during animation
On May 17, 2010, at 1:21 PM, Paul Sanders wrote:
> The approach I use is to subclass NSApplication and throw awat mouse,
> keyboard and gesture events in -[MySubclassedNSApplication sendEvent:]
> instead of calling super. For added style, beep.
For the OP's case, you don't even need to subclas
On May 16, 2010, at 3:37 PM, Tobias Jordan wrote:
> Hey guys,
>
> I have a CA transition running which obviously doesn't support any blocking
> modes (CABasicAnimation). I must block the UI during the transition so the
> user can't click somewhere and something unexpected happens. I think all
On May 16, 2010, at 3:37 PM, Tobias Jordan wrote:
> Hey guys,
>
> I have a CA transition running which obviously doesn't support any blocking
> modes (CABasicAnimation). I must block the UI during the transition so the
> user can't click somewhere and something unexpected happens. I think all
10 matches
Mail list logo
