#6936 closed bug (invalid)
ActivityMonitor duplicate graph
| Reported by: | Karvjorm | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/ActivityMonitor | Version: | R1/alpha2 |
| Keywords: | Duplicate graph | Cc: | Karvjorm |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
I tested ActivityMonitor in a VMware virtual machine with a single processor laptop. When I added graph from the menu, application showed two identical CPU graphs.
Also, it is impossible to remove any added graph.
Attachments (1)
Change History (7)
by , 14 years ago
| Attachment: | ActivityMonitor1.png added |
|---|
comment:1 by , 14 years ago
You know that you have to right-click on the graphs to change/remove them?
See the Haiku User Guide.
comment:2 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Unless you have any further input, I'm closing this as user error.
comment:3 by , 14 years ago
Yes, I did not know, that graph can be closed using right-click mouse button.
But my first point was that application can create a duplicate graph. In this case, it doesn't check that there is already a CPU graph. And that is a bug, I think. Another minor problem is that when you select "Add graph" from the menu, you will not know what graph application is creating. If the only graph the application can create is a duplicate one, then "Add graph" menu item should be disabled.
follow-up: 5 comment:4 by , 14 years ago
Maybe "Add graph" should just create an empty graph to avoid any confusion.
comment:5 by , 14 years ago
Replying to humdinger:
Maybe "Add graph" should just create an empty graph to avoid any confusion.
Do you mean empty graph when it can only create a duplicate graph? User has to know what to do with an empty graph. Showing a text "close this graph using mouse right-button" ?? Why not disable menu item in this case?
comment:6 by , 14 years ago
Since it's entirely your choice what graphs you enable, I don't see any added value in disabling those that are already shown (you may want to keep cache usage and swap usage in separate graphs, and have both compared to the amount of free memory, for example).
However, since ActivityMonitor cannot really know what the user would like to see, and having any default will just probably add more work for the user, I would actually go with humdinger's suggestion and and have only empty new graphs -- those could then have a nice help text on what to do.
Duplicate CPU graph in ActivityMonitor