Opened 17 years ago
Closed 16 years ago
#1987 closed bug (fixed)
BeTask Manager - four problems
Reported by: | kvdman | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I'm trying out BeTask Manager:
http://www.haikuware.com/view-details/utilities/system/be-taskmanager
It works, but there's four problems:
1) under the teams tab, you can't select individual teams to kill 2) xkill will only allow you to select tracker to kill with the crosshairs eventhough you select another window. 3) when you have task manager live in the deskbar and right-click it to 'show task manager' deskbar crashes. 4) quitting the program won't actually quit, and spikes your cpu.
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Hi,
most of the problems are fixed already, the only remaining part is nr. 2. This seems not so easy to fix, i had a look into the implementation of TaskManager and it turns out to be a problem of our app_server implementation. Asking for window_info seems somehow depend on a window order in R5, whereas we have a kind of unordered list which will in this case return the Tracker Desktop window first. So the check performed in TaskManager will always succeed for the first window.
Part 3 should be fixed with hrev26406, but i can't tell about the others.
I'm going to close this task and reopen a new one with more specific info about the xkill - app_server relationship.
Regards, Karsten
One more thing, under the teams tab, you can't order items (i.e by most memory usage)