Well it's true that the spinning colourwheel seems to have stopped
appearing, which is a distinct improvement. Is that because of that
change you guys made to the autowaitcursor?
It might be; honestly I'm not sure about that. But if it were needed,
there is a simple declare you can use to take care of that.
Where might I find that? I'm not particularly au-fait with the
toolbox...
BTW, when I say it seems to have crashed, I mean from the OS's point
of view, rather than the user's.
Ah, I see. I'm not sure the OS particularly cares, though.
Well it does if the app gets put in the background or you try to move
the window since it can't do anything with it. I guess that is a bit of
a transferred epithet - obviously the OS doesn't care, but the user
cares if the OS can't interoperate with an app because it thinks it's
frozen. Or something.
Less of an issue for fullscreen apps, granted, but they still do weird
shit if you command-tab to another application. I know that can be
switched off too with declares, but at that point I think the user
might really start to get pissed off, especially if your app gets stuck
in its infinite loop and you can't quit out except by restarting.
[Threads] don't suck if... oops, I can't talk about that yet. I
have to ask your patience on this one for a little while (perhaps a
few weeks) yet.
You enjoy doing that just a little too much... :-) I take it we're
expecting some thread improvement in either 5.2.3a1 or 6.0a1 then?
I really don't enjoy it; but you know how it is, if we say something
publicly and then it doesn't work out we get people screaming that we
aren't delivering on our promises.
Yeah, people suck. I've posted on this subject before. For what it's
worth I think you guys are doing a great job.
So, how about we postpone this discussion for a week or two, then
anyone who's on the betas list can take it up again. I have a neat
benchmarking app (inspired by a similar one by John Balestrieri) that
allows you to select from a a variety of different frame-driving
approaches, and see both your total frame rate as well as the
smoothness (using a little graph on bottom that shows you the time
between each pair of frames). That will form a good framework for
this discussion -- but because this is something we've been working on
just in the last few weeks, I'm not sure the discussion is worth
having until you can see what's up our sleeve.
Sounds cool, I'll await with baited breath... (and then bitch about it
in two weeks when nothing has happened :-)
Nick
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|