On 5/28/03 7:22 PM, "Mark Talluto" <[EMAIL PROTECTED]> wrote:
> > On Wednesday, May 28, 2003, at 05:47 PM, Dave McKee wrote: > >> So the saga continues. I re installed version 1.1.1 and opened the >> stack >> with version 1.1.1 and my stack is well behaved as is revolution 1.1.1. >> Going back to version 2.0r2, just opening the stack was enough to peg >> the >> cpu usage at 100%. Using cmd period to stop this behaviour works and >> then >> just opening the main stack's script is enough to peg cpu usage at 100% >> again. > > > If you have a default button active on the screen, that will eat up a > lot of cpu power. It is not Revs fault, but Apples. > > > > Best regards, > Mark Talluto > http://www.canelasoftware.com > > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution I don't think thatıs the problem. I have emptied my stack of all its scripts and now when I try opening the stack script, the cpu usage shoots to 100% and sits there until I depress cmd period. Then when I close the script window, Rev asks whether to change the scripts ( but nothing was added or changed or even clicked in ) and back it goes to 100 %, Cmd period again and the script window closes. And this same stack with all of its scripts works fine in Rev 1.1.1. In fact, the same stack worked ok in the last release of Rev 2.0 ( 2.0rc2 ). Something nasty has happened, not sure if its my stack ( unlikely because it functions ok in rev 1.1.1 ) or Rev 2.0 Its getting frustrating trying to track down what this problem is, so why do I get the feeling that I will have to recreate the stack from scratch before it will run in Rev 2.0 ( did not expect this sort of problem ) _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution