0 Members and 1 Guest are viewing this topic.
It will be slower than multiple threads, yes.
HoMM: [==--------] Project 'resumed': I'm suffering overwhelming new ideas being popped up in my dreams :PtiDE: [----------] Explored and understood the main part of the code: just started writing a Tokenizer.
It will be slower than multiple threads, yes. However, threads can set an option - FreezeOnIdle. This option means that if the thread does not have focus, it is frozen and no longer executed until it is no longer idle. This is useful for a notepad type of thing. The notepad process would freeze when switched out, and resume when switched in. Programs like Mosaic would be set to remain active on idle while compiling, for example.
Well, games would probably want FreezeOnIdle. This would stop them from running when you opened up the math stuff.
Quote from: SirCmpwn on November 07, 2010, 10:56:50 pmIt will be slower than multiple threads, yes. However, threads can set an option - FreezeOnIdle. This option means that if the thread does not have focus, it is frozen and no longer executed until it is no longer idle. This is useful for a notepad type of thing. The notepad process would freeze when switched out, and resume when switched in. Programs like Mosaic would be set to remain active on idle while compiling, for example.Yeah sounds like a cool idea. It would suck if you opened a game then quickly switched to a math program with teacher key or something, but the math stuff ran several times slower