For the mouse pointer that changes to a wait cursor, that's normal. As far as I know, RB uses the processor intensively when a sprite surface is running (I mean, your application is in a loop, like a do/ loop, but with events being called).
Also, that's "normal" your code is slow. In general, I try to use s.x=s.x +2 or a bigger number. I don't know if it's normal, system- widely speaking (maybe it has something to do with how RB handles the sprite surface (not a standard control, in my opinion)). Your 5.5.2 version is not too old (I usually use RB 5.5.5, which you may look for because you should be able to use your serial number for both versions, and, therefore, upgrade to 5.5.5 freely. Finding RB 5.5.5 is just the difficult part (I wonder if someone has the right to send a copy to someone (without the serial, obviously). If I'm allowed, I may send it to you if you want)). Hope this helps. Le 5 mars 07 à 22:55 Soir, Víctor Fernández Fernández a écrit: > i have a window, a button, a sprite surface... > > in my little test... > > when the user push the button... a little sprite cross the sprite > surface.... > > the problem is that when i push the button, the sprite surface going > slooooowwwwwwwwww, and sometimes hang the system. The mouse pointer > changes to wait mode. > > my code is simple... > > pusnbutton action event: > > s= new sprite > s.image=myhero > s.x=10 > s.y=10 > spritesurfacec.attach s > spritesurface.clicktostop=FALSE > spritesurface.framespeed=1 > spritesurface.run > > in the spritesurface nextframe event: > > if s.x<=200 then > s.x=s.x +1 > end if > > is my code the guilty or my rb version (5.5.2) is older for ? my > system: iMac G5 2.1 1GB RAM, Mac OS X 10.4.8 _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
