![]() |
2009-10-27
, 10:58
|
Posts: 329 |
Thanked: 142 times |
Joined on Oct 2009
|
#22
|
The Following User Says Thank You to MrGrim For This Useful Post: | ||
![]() |
2009-10-27
, 11:06
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#23
|
3) If the app hogs all resources, terminate automatically in one minute
![]() |
2009-10-27
, 11:32
|
|
Posts: 71 |
Thanked: 54 times |
Joined on Oct 2009
|
#24
|
You know, i don't like my idea so much that i have to keep pushing it, it just kind of annoys me i can't seem to make it well understood. So here it is again, for the last time (i promise!): when cpu usage goes above, say, 90%, the screen becomes black and white. There is no light fading (maybe even making it 5% brighter to compensate for lack of colors). There is no overlay and nothing to keep you from trying to interact with it, it just carries on as usual, but looks a bit different to let you know it's busy
Some apps are right to use lots of resources. When i decompress a .zip, i prefer a 10 second inactivity period and then back to idle rather than 2 minutes using 10% CPU. Apps should not be killed just because of resource use, and deciding which ones are not responding and which simply have high demands is hard
![]() |
2009-10-27
, 12:17
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#25
|
![]() |
2009-10-30
, 07:14
|
|
Posts: 270 |
Thanked: 195 times |
Joined on Aug 2009
@ Finland
|
#26
|
![]() |
2009-10-30
, 07:24
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#27
|
![]() |
2009-10-30
, 07:26
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#28
|
This is dangerous if not done right. It's a mobile computer, right, so I might try to run my hypothetical number crunching tool on it - at 100% CPU.
N800/OS2007
-- Metalayer-crawler delenda est.
![]() |
2010-02-16
, 01:49
|
Posts: 393 |
Thanked: 67 times |
Joined on Feb 2010
|
#29
|
![]() |
2010-02-16
, 02:40
|
|
Posts: 1,090 |
Thanked: 476 times |
Joined on Jan 2010
@ Ingolstadt, Germany
|
#30
|
I suggest the following:
1) Minimize unresponsive app to the dashboard with a throbber
2) If the app will not respond within, say 30 secs, bring up above suggested "kill this?" dialogue.
3) If the app hogs all resources, terminate automatically in one minute
4) Add notification area to the desktop, which tells you what happened. Windowsy "Your app just crashed, click OK" popups are just silly and should never be used.
EDIT: I guess the tray would do that better